In an attempt to solve another problem, I upgraded my XCode from 6.1.1 to 6.2.
Now I can no longer run any application from Delphi XE7 upd1 in the simulator - not even an empty app. Always get an error in Delphi when run from Delphi: Unable to create process or some times Debugger Assertion Failure rproxy.cpp line 663.
The app is deployed, but when I try to start it directly in the simulator with a click on the icon, it only shows the splashscreen shortly and then closes/crashes.
Problem is the same no matter if I choose to target Simulator7.1 or Simulator8.2 (always runs in Simulator 7.1 on the Mac anyway). Also the same both for Debug and Release mode. Choosing Device as target works fine with an iOS8.2 iPad!
How to solve this problem with the simulator?
(did anyone make it work with XCode 6.2?)
PS. I have also asked this question on the Embarcadero forum, but since it is down 80% of the time, there is no chance anyone can answer it.
Related
I was able to run automation scripts on simulators and physical devices (with varying success but at least they were working).
Now what seems to happen, on the iPhone 5 for example, it connects and the page appium.io opens, then nothing else happens.
The only error I can see in Appium is "Page 27752/0 not found. Already sent close_frame"
Nothing else has been updated except for Xcode, and I think before this I was on Xcode 9.2
This same script works fine with when automating Safari.
Version details below
MacOS 10.14.5
Appium 1.12.1
Xcode11
iPhone 5 OS 11.2.6
Apologies for any errors, I'm still new to this.
I actually don't know what to do to fix this. I've had so many problems getting automation to work with iOS that I'm reluctant to update anything at the moment. The automation works fine on Safari, just not iOS
I can't see where to attach the appium output log.
I ran into the same issue after updating to Xcode 11, seem like there is an issue with the Command Line Tools, you can roll it back to Xcode 10.2 like this:
This fixed the issue for me.
I've recently started working on an existing objc project and wanted to check the memory graph debugging tool. As I started a debugger with the app I realised it doesn't show in the debugging tools.
I tried it with another project (created a new swift project) and the icon suddenly did show again. But only for this project.
So my question now is if there're any settings in a particular project that can prevent the memory graph debugging tool from showing?
Any hints are appreciated.
I tried a lot of different simulators (iOS 9/10/11). I event tried rebooting my macbook because I read somewhere this could help ;-)
I'm using an objc only project with Xcode 9.1 or Xcode 9.2 beta 2.
This is my diagnostics selection in the scheme if that's related:
Step 1: shut down and restart your iPhone.
Step 2: quit and reopen Xcode.
This should make the button reappear.
For some reason, the button is not there when I test on the device, but it's there when I test on the simulator.
Hi I was having the same issue. It's actually hidden here:
It appears that the memory debugger will only work for newer devices. It definitely does appear on the iPhone 8 running iOS 11. On some of my older devices it does not appear. I'm not sure at this time what the cutoff is.
I'm trying to debug an iOS project in XCode 6.4. Recently, none of the breakpoints are working (they did before), while I'm running the iOS Simulator. The debugging area only starts if I manually attach it to the process. I've looked through the project build scheme and settings, and there's nothing to suggest that I've turned off or changed the debugger in any way.
The problem only occurs with this specific project in XCode. I even reinstalled XCode to no avail, so I assume the problem must be specific to this project/workspace.
Any ideas why the debugging is not automatically attaching to the process? Or a workaround?
Thanks!
I have that problem where I updated Xamarin and Xcode to their latest stable version.
My app will run on the Simulator, but won't run on the Device. It will install, then it will crash just after the Launch Screen, and it doesn't give any Error in the IDE.
I tried on another computer where Xamarin is on the same version, but Xcode is still on the 4.X ... and it launch with success and run as it should on the device.
So, is it just a problem with Xamarin and Xcode 5 compatibility ? Can I do something to fix that problem, any tips to solve this problem will be grateful.
What might be happening (that is happening to me) is that the resulting exe is too big.
I have an app that uses servicestack. Before xcode 4.6 it worked, after xcode 5 it does not work.
With Xamarin support and some research I realized that the "estimated size" for the "archive" in organizer was bigger than 62mb. Whenever that happens my app is killed before starting.
I am in the process of slimming down servicestack, but preliminarily it is working.
Bottom line: check the size of your exe. See limitation: Max size of an iOS application
Having a strange issue with XCode 4.5 on OSX 10.8.2.
When I run an application on the mac, it doesn't launch and I get the following error in console consistently.
10/01/2013 17:26:26.478 Xcode[7884]: ERROR: Failed to create an alert for ID "enabled" based on defaults: 1
When I run an iPad/iPhone app, the simulator launches, but the app just shows a blank screen. I thought there was an issue with my apps (although very unlikely) so attempted to create a vanilla mac app and iOS app. Both experience the same issues. Running/Debugging any iPad project directly on the iPad through Xcode works however.
I've attempted to:
Delete everything in ~/Library/Developer/Xcode/DerivedData/
Delete the Xcode app and download it again from the AppStore
Delete all of my Xcode preferences
Xcode Build and stop buttons also become unresponsive so I have to force quit xcode to try again.
Nothing seems to be working, Xcode works fine however on my mac pro at work and all projects build just fine! Any help would be much appreciated!
Never mind, setting the debugger to GDB instead of LLDB seems to have fixed this. It would however be good to get an answer as to why LLDB doesn't work as the default debugger and what's changed in xcode to make it no longer work as expected.