Console:
dyld: Symbol not found: ___chkstk_darwin
Referenced from: /private/var/containers/Bundle/Application/6A606806-B567-4237-9B63-561126BF5E96/Appname.app/Frameworks/libswift_Concurrency.dylib (which was built for iOS 13.0)
Expected in: /usr/lib/libSystem.B.dylib
in /private/var/containers/Bundle/Application/6A606806-B567-4237-9B63-561126BF5E96/Appname.app/Frameworks/libswift_Concurrency.dylib
the app is running smoothly in the simulator with iOS 12.4
I tried making libswift_Concurrency.dbt optional. It did not stop the app from crashing.
I encountered the same issue today, the issue was weird because everything just worked well before today. After some checks, I found that my system automatically updated Xcode from 13.1 to 13.2 last night. The Xcode 13.2 Release Notes shows that Xcode 13.2 has a compiler issue about libswift_Concurrency.dylib library, and it provides a Workaround method to resolve, but I found out the method doesn't work for me after I tried it.
I still don't know the reason which causes this issue, but I did make my project run on my iphone6 again by rollback Xcode to the version of 13.1 .
If your issue also caused by the update of Xcode, you can try this method. Download here: Xcode13.1
For iOS 12-12.5: use Xcode 13.1 and update your Pods (i.e. last versions for Realm) (bitcode is enabled by default). Xcode 13.2.1 still crashes on device with iOS 12 but runs fine on simulator.
You probably installed Xcode 13.2 from the App Store. Don't. There are bugs in that version. Go to developer.Apple.com and download Xcode directly from there.
Xcode 13.2.1 claims it resolves this issue (see the release notes) - in fact the issue presists.
Douglas Gregor confirmed that Xcode 13.3 beta 1 fixes the issue.
Personally, I'll use Xcode 13.1 and then use Xcode 13.3 when the final release comes out.
Related
How can i upgrade my ios deployment target version from 5.1 to 5.1.1. I have install 5.1.1 on my iPad but in xcode deployment target I can not get the newest version from the drop down list in both of(Project->info->Deployment Target->ios Development target and Target->Summary->ios Application Target->Deployment Target). But in this drop down I am not getting the latest ios version.
Thanks in advance.
I ran into this today, when I tried to symbolicate crash reports from phones that were on 5.1.1. The addresses would not symbolicate because symbolicatecrash.pl could not find the symbols for 5.1.1. The solution from Apple is here: basically plug in a phone with 5.1.1 and Xcode will load the symbols.
https://discussions.apple.com/docs/DOC-3461/diff?secondVersionNumber=8
Okay I am late but here is what was issue with me. My xCode was debugging fine for iOS 5.1.1 (9B206) however, my other iPhone was running iOS 5.1.1 (9B208) and thus the above problem as you face.
The solution was to copy the debug symbols from the working version to the non-working one. Here is how
Enable Showing Hidden files
Navigate to ~/Library/Developer/Xcode/iOS DeviceSupport/5.1.1 (9B206)/Symbols/System/Library/Caches/com.apple.dyld
Copy the available three files
Navigate to ~/Library/Developer/Xcode/iOS DeviceSupport/5.1.1 (9B208)/Symbols/System/Library/Caches/com.apple.dyld
Paste the files.
Detach the device and attach again.
Worked perfectly for me .. =)
Yesterday after about a whole nights tinkering i manage to compile for 5.1.1
That was after i downgraded from iOS 5.1.1 (9B208) to iOS 5.1.1 (9B206) as a last desperate attempt.
But today afte a restart im back to square one.
When i go to the organizer and select devices from the top menu i get the following text as before:
The version of iOS on “xs iPhone” does not match any of the versions
of iOS supported for development with this installation of the iOS
SDK. Please restore the device to a version of the OS listed below, or
update to the latest version of the iOS SDK; which is available here.
OS Installed on xs iPhone
5.1.1 (9B206)
Xcode Supported iOS Versions Latest
5.0 (9A334)
4.3
4.2
I feel completely dumbfounded that it has to be so vastly complicated getting xcode and iOS go together.
But lets say i clean out xcode and reinstall my iphone.
Is there a safe way to compile for the latest IOS "currently 5.1.1"?
As others have pointed out, you need to install the latest version of Xcode, which is 4.3.2.
We recently had this problem after the latest iOS update and upgrading Xcode solved it just fine.
I had similar problems until I upgraded my Xcode to the latest version. Upgrading should fix your issue.
I had a similar problem and I can not upgrade to Xcode 4.3.x because I am still running Snow Leopard and 4.2 still is the latest Xcode version. I solved the issue after following the steps in this answer
https://stackoverflow.com/a/9621226/467813
Just installed xcode 3.2.2 (on Lion) so I can test my app for the iOS 3.0 and 3.2
Created a simple test app based on View application template.
Just trying to build it gives me the following error.
I doubt you can use XCode 3 with Lion, even I was using XCode 4 and had to update to 4.1 to run on Lion.
However if using XCode 3 is mandatory for you I found some post explaining how to do so but it seemed tricky. In his original post he clearly mentions the same problem as you're having.
You can (must? should?) use the latest version Xcode and still target the older iOS. I see that you're trying to do this presumably to use the simulator, but I'd strongly recommend testing on the actual devices with the older versions of iOS.
I have new changed the Snow leopard with Lion OS x and Xcode 4.0.1 with 4.1. The iPhone code was working fine on Xcode 4.0.1. Now in Xcode 4.1 it giving errors mostly related to LLVM GCC 4.2. I have tried with changing the compiler's different options available. Can body know the issue and help me out of this.
I think you want to change the compiler version on the target and double click it then you have to change it from there.Try it,i may solve your problem.
http://useyourloaf.com/blog/2011/3/21/compiler-options-in-xcode-gcc-or-llvm.html
check this url
I know that when I upgraded to Lion and Xcode 4.1, the update via App Store removed iOS SDK 4.0, 4.1 and 4.2, leaving only 4.3.
This gave me compile errors because my base SDK was 4.0, it required the 4.0 SDK files to compile, I was lucky enough to have everything backed up and I copied my SDKs back over to Lion into
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs
This was the only issue I had with the upgrade, hope this helps.
About 3 months ago I set up my iPhone for development; installed the provisioning profile, updated the device to the latest version of iOS, namely 4.3.3 (8J2) and testing applications on my iPhone worked 100%.
Today I went back to working on one of my iPhone applications after not having worked in XCode for about a month, and now I do not seem to be able to deploy applications to my iPhone. When I try deploy and run on my iPhone, I get the message "No provisioning iOS device connected", even though my iPhone is connected.
If I look in the organizer window of XCode, I see my iPhone listed there under DEVICES, but I see the following message when I select my iPhone entry:
The version of iOS on “Bruce Hill’s iPhone” does not match any of the versions of iOS
supported for development with this installation of the iOS SDK. Please restore the
device to a version of the OS listed below, or update to the latest version of the iOS
SDK; which is available here.
OS Installed on Bruce Hill’s iPhone
4.3.3 (8J2)
Xcode Supported iOS Versions
4.3.3 (8J2)
4.2 (8C134)
4.1
4.0
4.0.2
4.0.1
3.2
3.2.2
3.2.1
3.1
3.1.3
3.1.2
Does anyone have an idea what is going wrong here and why XCode seems to think that my iPhone has an unsupported version of iOS installed, when in fact the latest version is installed?
UPDATE:
I have tried restarting my Macbook Pro, doing a hard reboot of my iPhone and removing my iphone entry in the organizer. None of these actions helped. My iPhone keeps getting listed in the organizer with an orange circle and if I hover over my iPhone entry I get a tooltip message that says "This device is busy or otherwise unusable by Xcode."
I did notice that in my developer information in System Profiler it only shows sdk 4.2 (8C134) installed, not 4.3.3 (8J2), even though Xcode lists it as being present and supported in the message I quoted above. Here is my developer information:
Version: 3.2 (10M2423)
Location: /Developer
Applications:
Xcode: 3.2.5 (1760)
Interface Builder: 3.2.5 (823)
Instruments: 2.7 (3017)
Dashcode: 3.0.2 (333)
SDKs:
Mac OS X:
10.4: (8S2167)
10.5: (9L31a)
10.6: (10M2423)
iPhone OS:
4.2: (8C134)
iPhone Simulator:
3.2: (7W367a)
4.0: (8A400)
4.1: (8B117)
4.2: (8C134)
I think what happened here is that I installed Xcode and then later did an update of my iPhone to iOS 4.3.3. This problem then occurred because my Macbook Pro actually didn't have the SDK for 4.3 installed, even though Xcode seemed to think that it was installed.
So, I got this working by downloading an installing Xcode 4.0.2 and iOS SDK 4.3. I downloaded Xcode from here: http://developer.apple.com/xcode/
Once Xcode 4.0.2 was installed and running, I connected my iPhone, it showed the orange dot again briefly (for about 10 seconds or so) and then this turned to a green dot and I was able to deploy my application to my device again... FINALLY!! :) In my developer settings in System Profiler, I also see iPhone OS: 4.3:(8H7) listed there now. I think that this issue would also have been resolved by installing Xcode 3.2.6 with iOS SDK 4.3, as this would, I think, also have resolved the missing or corrupt SDK 4.3 on my Macbook, but I chose to download and install the latest version.
So, bottom line: Xcode working again! I am happy! :)
I had a similar problem with my 3GS and i solve it by resetting iPhone's developer configuration. Try to hard reset your device (here' the link - don't worry, your dta will survive). Then remove your device from Xcode organizer and add it again.
Also try 'Cleaning' your Xcode project and just turning off your phone and back on again. Restart your computer while you're at it. After it's back up, open Xcode, then plug in the device. It should do its thing then start working again. I had the same issue a few times when I updated and hadn't disconnected/reconnected everything.