I've been using essentially the same set of schemes for my app for several years with no problem. When selecting a scheme to build, for each simulator device there would be a choice of iOS reflecting what simulators were installed.
Trying to solve a problem, I deleted Derived Data per some suggestions here. Today, when I select a scheme to build, I get this:
This is not helpful! I cannot figure out how to get back to the Target/Scheme combinations I had before. Any and all help will be appreciated!
yes i got this when I installed Xcode 7 beta.
Went away when I downloaded XCode 7 from the mac app store.
But I had to run Xcode 6.4 to test swift 1.2 code and was fine for a while till i rang two simulators at once.
Then in Xcode 7 they all appeared again
I had also downloaded the 8.4 simulator in Xcode 7 today so this may also have caused it.
I believe both simulators were sharing this folder so they got merged:
/Users/gbxc/Library/Developer/CoreSimulator/Devices
/Users/gbxc/Library/Developer/CoreSimulator/Devices/device_set.plist
raised q:
https://stackoverflow.com/questions/32742962/xcode-devices-list-showing-50-devices
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
Just showing the Documentation Window crashes XCode 12 (cmd-shit-0) - anytime I do it.
Does anybody have the same problem, an explanation or a work around ?
Update: There's now a new version (12.0.1) in the App Store that fixes this issue.
I'm experiencing the same when using the version from the App Store. People in this Apple Forums thread are reporting that it doesn't occur with the GM download from Apple's developer resources, despite the build identifiers being exactly the same.
Anecdotally, I can confirm that I was able to use documentation in the GM version before I deleted it in favor of the App Store version. So this may in fact be a viable workaround until the App Store version is fixed.
The Xcode on the app store is some sort of unknown version, (Since there it release even before the GM version available). So get rid of it and Download The Xcode From The developer.apple.com or click the proper version below. Then it. will work like a charm.
This needs you. to login to your account
Don't forget to remove the appstore version downloaded Xcode
Direct Download
Xcode 12
Xcode 12.2 Beta
I use xcode 12 beta 5 works well can open document window, when I upgrade to GM seed, it can not open document window any more. When I fallback to xcode 12 beta ,open document it crash every time. All these happened on mbp13 pro, but my another mbp 15 with the same macos version works very well.
I guess it have something with macOS system, not xcode version.
Now I upgrade xcode by AppStore ,crash all the same.
I have an UI issue in my Swift 1 (Xcode 6, iOS 7.1) app on devices running iOS9. I've tried to convert my app to Xcode 7 and Swift 2.0 but I'm running in a lot of issues here.
To give my customers a quick fix until I've figured out whats wrong I was wondering if I can download and install Xcode 6 (the version I build and uploaded the app last time) correct the UI issue (I know what to do) and upload the app again.
In a nutshell: Will Apple deny an app update with an old Xcode/Swift version?
The “Submit Your Apps” page currently (as of 2015-09-23) says
If your app still depends on Xcode 6, you'll need to keep a partition or external hard drive with OS X Yosemite installed in order to submit from Xcode 6.
This clearly implies that you can still submit apps with Xcode 6 (and therefore with the iOS 8 SDK).
Trying to get iOS 8 simulators in XCode 7. Prior to beta 3, that wasn't possible but in beta 3 release notes:
"Xcode 7.0 beta now supports downloadable legacy simulators."
Xcode 7 beta 3 Release Notes
They also show up in the "Downloads" section:
I'm running into the same problem as reported in this question about XCode 6. I have Xcode 6 still installed, but am trying to install the simulator to Xcode 7 beta 3 where iOS 8 is no longer the base OS.
Error msg:
Could not download and install iOS 8.3 simulator. Authorization is required to install the package
I found another workaround on the Apple forums for this issue that does not require downloading/having other versions of Xcode. If you run Xcode using sudo the simulator downloads and installs work just fine:
sudo /Applications/Xcode.app/Contents/MacOS/Xcode
Note: Once the downloads and installs are complete you should quit Xcode and start it normally.
Update: XCool points out an important safety tip in the comments that I wanted to highlight here:
Make sure that you close any projects before opening Xcode using sudo, otherwise there'll be a lot of permission issues with any files that are currently open when the installation occurs.
sorry for the post, I don't have 50 reputation to comment. i am having this same issue. Any further progress? If I happen to come across a solution I will let you know. What have you tried?
--------- UPDATE -------
So I have found a work around.... if you are trying to get it to deploy to an iPhone.
If you still have the previous xCode file... you can navigate to Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
copy the simulators and SDKS you want over to the same location in Xcode-beta.app and paste... granted those downloads still won't download, but this will allow for the simulator to run on your iPhone.
I got this from Using the device simulator for iOS 8 with Xcode 7
and verified it works.
XCode 7 and above does not support simulators 8.4 and earlier.
Please check my answer on the post here.
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.