Yesterday i updated to the latest version of Xcode, since the update i experience a very strange glitch:
When i try to run the app on a device the Xcode start with the process and say "finish run the app on iPhone" and then the Xcode crashes.
what could cause this problem?
before the update everything worked perfect.
I was seeing this same issue and even trying to view the device from Window -> Devices would cause Xcode to crash. I updated the device to the latest version of iOS (8.0.2) and that seems to have fixed the problem (for this afternoon at least).
Related
I create a flutter app and now I'm trying to run it through XCode on my real iPhone, but after the installation finishes, I face the following problem:
Also with I trying to run the application on my real phone, after clicking on the application icon, I face a white screen appears, and then the application closes directly.
Catalina 10.15.3
IOS 14.2
XCODE 11.7
Also I was make a trust to app in phone
Does anyone know the reason for this problem?
This problem maybe because of two reasons:
First: Xcode 11.7 doesn't have support files for iOS 14 you can download it from here https://github.com/filsv/iPhoneOSDeviceSupport
Second: I have this problem now and I couldn't fix it.. but I have iPhone with iOS 14.2 and iPad with iOS 14 so the problem was just on the iPhone but after I updated the iPad with iOS 14.2 it happened with it.. so the problem maybe because of the iOS 14.2 so we have to wait for the update or because of the Xcode 11 version and we have to download the Xcode 12 version..
I hope we can find a solution quickly...
make sure to have the latest system update on your target device and the latest Xcode version as well. The error should disappear.
Best,
Ralf
I have fixed the problem by using the above solution but it has happened again. So, I have followed these instructions and fixed again:
https://stackoverflow.com/a/61665031/6586109
A good first place to look is Window > Devices & Simulators in xCode, then find the details for your device. There may be error information here that helps you find the fault.
Restarting devices and installing updates seem to fix this problem for a lot of people.
For me, there was a red notice in the device window about connection to the device and it turned out to be the cable that was at fault.
This was an official Apple cable, just a few months old, and still works fine for charging and data transfer; and I've been using it with xCode without problems for a couple of months. It seems to be possible for Apple cables to develop some tiny physical fault that seemingly only xCode is sensitive to.
Using a different cable worked first time for me.
There seem to be a few variations on the exact error message with the same root causes varying depending on exactly what xCode was trying to do at the exact moment it failed: I'm on xCode 12 and for me it was:
Failed to start remote service on device
Failed to start remote service com.apple.installation_proxy on device
I know similar questions have been asked many times.
My xcode projects ran fine on the simulator. Ive started a new project today and the first time I tried running it I get the black screen and 'unable to boot simulator error'.. and I have to force quit xcode. Now all my projects are getting the same error??? They were working fine before.. I have not updated anything either? Whats the problem?
Thank you
After many failed attempts at fixing the problem I ended up updating the OS from El Capitan to Sierra and I completely uninstalled Xcode and reinstalled a fresh version (from 7.3 to 8). The problem is now gone. I am assuming there was some kind corruption in Xcode as I cant figure how else this specific issue would occur.
When I run tests on my project in XCode, it builds, and then says Testing... which never ends.
When I use the stop button, the process stops with this text in the console:
*** If you believe this error represents a bug, please attach the log file at /Users/MY.NAME/Library/Developer/Xcode/DerivedData/APPNAME-gcsubmsjksdbljcswbefkgugjray/Logs/Test/C53D8988-3564-4C2B-A535-075D26D1E4A7/Session-APPNAMETests-2016-07-13_140704-t3DFd5.log
However, I am unable to run the tests again, and have to relaunch xcode to run them.
Is this an issue on XCode that may be known to the Apple developers?
EDIT
So, I figured, the simulator is not launching in time, and that fails the xcode to run the tests. It might be an installation bug with the simulator.
As I anticipated in my edit to the question the first time, XCode installation did not install the simulator correctly.
I trashed the old installed version and reinstalled XCode. And now everything works fine.
Thanks for all the help.
I found that the tests never ran if I was running anything other than iOS10 on the simulator, so use iOS 10. I guess backwards compatibility doesn't really matter.
Just installed XCode 6 Beta to test my app. The iOS 8 Simulator runs and my app successfully installs but the simulator can't access the internet. I try using safari or maps and there is no network connection. If I run the iOS 7 simulator from XCode 6, it connects to the internet perfectly.
I've tried using the steps in this thread but it didn't change anything. (The steps were more if your app doesn't install but I tried anyway.)
I don't have a firewall or little snitch blocking the simulator.
Any other pointers?
I had the same problem. Try to quit the iOS simulator, and then re-build and launch your application. It should work.
I saw a lot of posts about re-starting the simulator, resetting the simulator settings, etc. I ended up re-installing X-Code, updating to X-Code 6.1, etc, etc. Still didn't have a connection to the network!
What ended up being the solution is I turned off my antivirus (TrendMicro). I had checked all the anti-virus settings before and didn't see any "block process connection". When I turned the whole thing off it solved the problem though.
I had same error with xCode 6.1 and iOS 8 simulator. What worked for me is I went to settings>developer> and switch on "Allow HTTP Services" option.
Same problem for avast security on mac, turning of webshield under avast preferences solved it.
Xcode version 7.3.1, ios simulator 8.4
Turning off AVAST resolve all errors.
I've had the exact same issue. It's bizare but plugging my Macbook in via an ethernet cable seemed to resolve this. I know it's not perfect but it works.
I also use XCode 6.1 GM and git the same issue. My scenario was that during development I connected my MacBook to another WLAN. My Macbook was connected to the internet, but the iOS Simulator not. My solution was to just close the iOS simulator and redeploy the app from xcode.
Just simply reset the simulator. Quit and Re-run your app your problem will be gone. It works for me.
I had a similar scenario with Mac OS X 10.9.5, Xcode 6.2, Cordova 4.3, iOS 8.3 - Everything worked fine on all platforms except ajax/network access was limited on the IOS simulator.
As suggested by by others, going into the Settings on the IOS emulator and changing "Allow HTTP Services" in the developer submenu opened up all network access and ajax queries/processes came to life.
So try that first!
The source control I used is Git. So upon resetting all my local changes and getting the latest solved my problem.
So First thing I would do is Stash all your local changes if you need them.
Then reset all your local changes and get the latest
Now run the tests.
This worked for me. Hopefully works for you as well.
Hi I just upgraded to Mountain Lion. I created an empty Single View Application and run it. The first time it runs fine but the next runs will give me the "There was an internal API error" pop-up warning TWICE. It's the same with my other projects. They run okay once but gets this error the next runs. There was no warning or any specific warning message of any kind.
Any idea how to solve this?
Would really appreciate your help.
I have it working on iOS6 Beta 4!! This is what I did but other variations may also work:-
Install XCode 4.5 Developer Preview 4
Delete your app from the device
Run your app from Dev Preview 4
Delete your app again (not sure if you have to do this)
Return to XCode 4.4.1
Run your app, stop running, run again!!!
Of course you could continue developing in 4.5, but I prefer to wait.
Installing 4.5 Beta 4 installs updated device support. Once this is done once (possibly on any device) it should work fine. If you use the same device on a different machine you will have to again run it once from 4.5 Beta 4 before using your preferred version of Xcode (You do not need to delete the app from your device this time).
Edit: I am pretty sure that if you make a change to your core data you will need to run from 4.5 for the first time also.
Don't know if this helps, but I've deleted all files in ${HOME}/Library/Developer/Xcode/iOS DeviceSupport and it worked as a charm (Xcode 4.4.1, OSX 10.7)
I had this problem when I upgraded my device to Preview4 but had my MBP still running Xcode Preview3. Updating to Xcode Preview4 made the problem go away for me, no restarts necessary.
Deleting the app manually from the device/simulator will allow you to build and run successfully. A long term solution is to not use a Beta Xcode :)
Sounds crazy but you can also not use the Beta version of XCode 4.
However, you must keep it in your left hand to authorize your iPhone to compile with the non Beta version (don't ask me why, it works).
If you run your app with XCode 4.5 preview & IOS6 Beta 4, the second time you run your app on the device, you'll get the internal API error.
In theory, you cannot use XCode 4.4 to compile on your iOS6 Beta 4 iPhone.
But...
It seems that, if you launch XCode 4.5 Preview, connect your iPhone (so it is recognized), run the application on it (even if you get the error), quit XCode 4.5, launch XCode 4.4 and .. tadaaaa... your iPhone is now recognized as an authorized device to compile on...
And of course, XCode 4.4 doesn't generate the api error...
I have Xcode 5.0.2 and iPhone with iOS 7.0.6.
Every time when I launched my project on iPhone, I saw "There was an internal API error". And it was launched on simulator without any problems.
I did all the stuff that usually helps (like remove an app, clean, restart Xcode, restart a mac, etc.).
This problem went away only after I restored the iPhone. Sad but true.
I don't know so far, why it appeared.