I just upgraded XCODE to 13.3.1 and my app crashes on startup when installing from TestFilght. When I build it directly on the phone there is no issue with the app.
There are no crash logs and can't see the logs on the device itself. I don't know what will happen if I'll publish it to the store and I don't want to try. The app should work on TestFlight
I searched the internet and it's an Apple bug. So let me summarize all the solutions here-
Disabling bitcode (setting to NO)- is the only working solution- but I don't want to disable it.
If any of you have another solution please let me know!
Other solutions that didn't work-
Updating XCODE to 13.4 - didn't help
Adding "-Wl,-weak-lswift_Concurrency -Wl,-rpath,/usr/lib/swift"- didn't help
Adding libswift_Concurrency.tbd in the "Link Binary with Libraries" - didn't help
Related
Every time I try to run this application it builds OK and installs, but as soon as it runs, the application breaks and prints this error message:
dyld: Library not loaded: #rpath/StandardCyborgFusion.framework/StandardCyborgFusion
Referenced from: /private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/StandardCyborgExample
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion: code signature invalid for '/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion'
I saw many similar posts here and on the App Developer forums about this problem but no one has an explanation or a valid fix.
I tried:
Cleaning and building
Restarting XCode
Restarting the Mac
Completely resetting Keychain
Verifying all Keychain certs Trust settings are on "Use System Defaults"
Factory resetting my Mac
It appears to be an issue with my iOS device. The application can start on a simulator, but the simulator is not good for my development purposes so I need to make this work on my device. I recently updated my iPhone XR to iOS 13.3.1.
"Running new app on actual iOS (13.3.1) device crashes on startup: code signature invalid for "path/to/Flutter.framework/Flutter" #49504" seems to be the same issue.
I'm using XCode 11 and iOS 13.
This is an issue with iOS 13.3.1. All dynamic frameworks being compiled to the newest release of iOS 13.3.1 are experiencing this issue when run on a personal provisioning profile/developer account. The solution, copied from jmagman from Github, is below.
You can:
Use a non-Personal Team provisioning profile (paid developer account).
Run on the 13.3.1 simulator.
Test on a real iOS device running 13.3 or lower.
Install the beta profile on your test device and install iOS 13.4 beta 3. (Fixed)
Wait for iOS 13.4 to be released.
Hopefully this issue will be fixed soon.
I'm using CocoaPods, and for me this fixes the error (Wasa22's Answer on github issue):
Open the podfile
Comment out use_frameworks!
Add use_modular_headers!
In Terminal, do a pod update -> pod install
In Xcode, Clean (Command-Shift-K) -> Build and Run.
Source:
https://github.com/Alamofire/Alamofire/issues/3051
This appears to be fixed on iOS 13.4 beta 3. You can install the beta profile or wait for the release of iOS 13.4.
I see 2 way to fix it.
Downgrade to iOS 13.3. iOS 13.3.1 breaks third parties signature unless you have a paid developer account. If possible (get a cheap iphone dedicated to development)
Update Mac OS, Xcode, and iOS to latest Beta version (Update anyone of them alone will not work, because iOS beta requires latest Xcode beta, and Xcode requires latest Mac OS Catalina)
I had the same issue using a local framework. After hours of debugging, all I had to do what change the default "Do Not Embed" to "Embed & Sign" and the error went away. Worth a try! :)
If you run from Xcode you will see an error like:
/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-A146-
A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter: code signature
invalid for '/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-
A146-A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter'
solution provided by jmagman on Github
jmagman has escalated to Apple (FB7562472) and will let everyone know if they hear anything. more details on github
I encountered this issue when trying to build to my actual iOS device (but it worked fine in the simulator). I spent at least 10 hours trying to fix this bug. Tried everything in all the forums, nothing worked. But this is what finally worked for me!
Upgrading from iOS 13.3.1 to iOS 13.4.1
I couldn't have imagined this, but its true that iOS 13.3.1 breaks the third parties signature unless you have a paid developer account!
I had the same error message with GoogleUtilities.framework. My problem occurred when trying to run on the simulator. On the device, it ran fine. The problem is that CylancePROTECT antivirus software on my MacBook is quarantining the file and this causes the app to crash. Check if your device is running CylancePROTECT or some other antivirus software that is blocking the framework you need.
This is an Apple's problem. I solved this issue by upgrade my device to iOS 13.4.1
Also, if you don't want upgrade ios system,and you also use Podfile, you can do flow ways:
Comment out use_frameworks! in Podfile.
Add use_modular_headers!
pod deintegrate + pod install.
Clean (Command-Shift-K) -> Build and Run.
Every time I try to run this application it builds OK and installs, but as soon as it runs, the application breaks and prints this error message:
dyld: Library not loaded: #rpath/StandardCyborgFusion.framework/StandardCyborgFusion
Referenced from: /private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/StandardCyborgExample
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion: code signature invalid for '/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion'
I saw many similar posts here and on the App Developer forums about this problem but no one has an explanation or a valid fix.
I tried:
Cleaning and building
Restarting XCode
Restarting the Mac
Completely resetting Keychain
Verifying all Keychain certs Trust settings are on "Use System Defaults"
Factory resetting my Mac
It appears to be an issue with my iOS device. The application can start on a simulator, but the simulator is not good for my development purposes so I need to make this work on my device. I recently updated my iPhone XR to iOS 13.3.1.
"Running new app on actual iOS (13.3.1) device crashes on startup: code signature invalid for "path/to/Flutter.framework/Flutter" #49504" seems to be the same issue.
I'm using XCode 11 and iOS 13.
This is an issue with iOS 13.3.1. All dynamic frameworks being compiled to the newest release of iOS 13.3.1 are experiencing this issue when run on a personal provisioning profile/developer account. The solution, copied from jmagman from Github, is below.
You can:
Use a non-Personal Team provisioning profile (paid developer account).
Run on the 13.3.1 simulator.
Test on a real iOS device running 13.3 or lower.
Install the beta profile on your test device and install iOS 13.4 beta 3. (Fixed)
Wait for iOS 13.4 to be released.
Hopefully this issue will be fixed soon.
I'm using CocoaPods, and for me this fixes the error (Wasa22's Answer on github issue):
Open the podfile
Comment out use_frameworks!
Add use_modular_headers!
In Terminal, do a pod update -> pod install
In Xcode, Clean (Command-Shift-K) -> Build and Run.
Source:
https://github.com/Alamofire/Alamofire/issues/3051
This appears to be fixed on iOS 13.4 beta 3. You can install the beta profile or wait for the release of iOS 13.4.
I see 2 way to fix it.
Downgrade to iOS 13.3. iOS 13.3.1 breaks third parties signature unless you have a paid developer account. If possible (get a cheap iphone dedicated to development)
Update Mac OS, Xcode, and iOS to latest Beta version (Update anyone of them alone will not work, because iOS beta requires latest Xcode beta, and Xcode requires latest Mac OS Catalina)
I had the same issue using a local framework. After hours of debugging, all I had to do what change the default "Do Not Embed" to "Embed & Sign" and the error went away. Worth a try! :)
If you run from Xcode you will see an error like:
/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-A146-
A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter: code signature
invalid for '/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-
A146-A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter'
solution provided by jmagman on Github
jmagman has escalated to Apple (FB7562472) and will let everyone know if they hear anything. more details on github
I encountered this issue when trying to build to my actual iOS device (but it worked fine in the simulator). I spent at least 10 hours trying to fix this bug. Tried everything in all the forums, nothing worked. But this is what finally worked for me!
Upgrading from iOS 13.3.1 to iOS 13.4.1
I couldn't have imagined this, but its true that iOS 13.3.1 breaks the third parties signature unless you have a paid developer account!
I had the same error message with GoogleUtilities.framework. My problem occurred when trying to run on the simulator. On the device, it ran fine. The problem is that CylancePROTECT antivirus software on my MacBook is quarantining the file and this causes the app to crash. Check if your device is running CylancePROTECT or some other antivirus software that is blocking the framework you need.
This is an Apple's problem. I solved this issue by upgrade my device to iOS 13.4.1
Also, if you don't want upgrade ios system,and you also use Podfile, you can do flow ways:
Comment out use_frameworks! in Podfile.
Add use_modular_headers!
pod deintegrate + pod install.
Clean (Command-Shift-K) -> Build and Run.
Every time I try to run this application it builds OK and installs, but as soon as it runs, the application breaks and prints this error message:
dyld: Library not loaded: #rpath/StandardCyborgFusion.framework/StandardCyborgFusion
Referenced from: /private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/StandardCyborgExample
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion: code signature invalid for '/private/var/containers/Bundle/Application/2292CCF2-800F-4E28-AF10-A1B98081DD0A/StandardCyborgExample.app/Frameworks/StandardCyborgFusion.framework/StandardCyborgFusion'
I saw many similar posts here and on the App Developer forums about this problem but no one has an explanation or a valid fix.
I tried:
Cleaning and building
Restarting XCode
Restarting the Mac
Completely resetting Keychain
Verifying all Keychain certs Trust settings are on "Use System Defaults"
Factory resetting my Mac
It appears to be an issue with my iOS device. The application can start on a simulator, but the simulator is not good for my development purposes so I need to make this work on my device. I recently updated my iPhone XR to iOS 13.3.1.
"Running new app on actual iOS (13.3.1) device crashes on startup: code signature invalid for "path/to/Flutter.framework/Flutter" #49504" seems to be the same issue.
I'm using XCode 11 and iOS 13.
This is an issue with iOS 13.3.1. All dynamic frameworks being compiled to the newest release of iOS 13.3.1 are experiencing this issue when run on a personal provisioning profile/developer account. The solution, copied from jmagman from Github, is below.
You can:
Use a non-Personal Team provisioning profile (paid developer account).
Run on the 13.3.1 simulator.
Test on a real iOS device running 13.3 or lower.
Install the beta profile on your test device and install iOS 13.4 beta 3. (Fixed)
Wait for iOS 13.4 to be released.
Hopefully this issue will be fixed soon.
I'm using CocoaPods, and for me this fixes the error (Wasa22's Answer on github issue):
Open the podfile
Comment out use_frameworks!
Add use_modular_headers!
In Terminal, do a pod update -> pod install
In Xcode, Clean (Command-Shift-K) -> Build and Run.
Source:
https://github.com/Alamofire/Alamofire/issues/3051
This appears to be fixed on iOS 13.4 beta 3. You can install the beta profile or wait for the release of iOS 13.4.
I see 2 way to fix it.
Downgrade to iOS 13.3. iOS 13.3.1 breaks third parties signature unless you have a paid developer account. If possible (get a cheap iphone dedicated to development)
Update Mac OS, Xcode, and iOS to latest Beta version (Update anyone of them alone will not work, because iOS beta requires latest Xcode beta, and Xcode requires latest Mac OS Catalina)
I had the same issue using a local framework. After hours of debugging, all I had to do what change the default "Do Not Embed" to "Embed & Sign" and the error went away. Worth a try! :)
If you run from Xcode you will see an error like:
/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-A146-
A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter: code signature
invalid for '/private/var/containers/Bundle/Application/D0BD5694-A7D6-4820-
A146-A49DF0C0F0B1/Runner.app/Frameworks/Flutter.framework/Flutter'
solution provided by jmagman on Github
jmagman has escalated to Apple (FB7562472) and will let everyone know if they hear anything. more details on github
I encountered this issue when trying to build to my actual iOS device (but it worked fine in the simulator). I spent at least 10 hours trying to fix this bug. Tried everything in all the forums, nothing worked. But this is what finally worked for me!
Upgrading from iOS 13.3.1 to iOS 13.4.1
I couldn't have imagined this, but its true that iOS 13.3.1 breaks the third parties signature unless you have a paid developer account!
I had the same error message with GoogleUtilities.framework. My problem occurred when trying to run on the simulator. On the device, it ran fine. The problem is that CylancePROTECT antivirus software on my MacBook is quarantining the file and this causes the app to crash. Check if your device is running CylancePROTECT or some other antivirus software that is blocking the framework you need.
This is an Apple's problem. I solved this issue by upgrade my device to iOS 13.4.1
Also, if you don't want upgrade ios system,and you also use Podfile, you can do flow ways:
Comment out use_frameworks! in Podfile.
Add use_modular_headers!
pod deintegrate + pod install.
Clean (Command-Shift-K) -> Build and Run.
I just installed Crashlytics in my app yesterday and I'm having trouble trying to track down the missing dSYMs that it warns me about in their Dashboard. Currently running Xcode v7.2.1 and building for iOS 9.2
I'm pretty sure I've followed each current Stackoverflow answer to this problem to no avail. I've tried:
This answer
And this answer
And I have already tried to go into the Xcode Organizer and downloading the dSYMs from there but it says there are none to download.
Is there another way to find these or am I just unable to use Crashlytics in my app?
After looking around some more I have found a solution (or just a workaround). By disabling bitcode in my project Build Settings, Fabric is able to automatically collect my dSYMs on build. Also, I have additional frameworks included as .xcodeproj files in my app, so these must also have bitcode disabled.
I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.