I keep got this error message on iPhone8:
"The developer needs to upload a build that supports your device's architecture (armv6)."
And the same version is ok to install on other devices (iphone7,6,ipad...).
So far I had tried
update mac to 10.12.6 and reboot
keep clean whole Xcode project
update crashlytics/fabric version
try Xcode 8.3 and 9GM
And nothing work for me.
This is a known issue that the team is working to fix. I'll post an update to this answer once we have it working. It's top priority for us and we're looking to have a solution out ASAP.
UPDATE:
This is fixed now. Beta installs work on iPhone 8.
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 have upgraded macOS Sierra Developer Preview, but my Xcode 7.3.1 gives below error while try to run my project on simulator. In addition Generic to archieve gives another error like:
In addition for archive: a cryptographic verification failure has occured.
How can I fix this?
I have tried before Xcode 8.0 Beta, uninstall it deleting derivedData and reset content simulator but still occurs this error.
Update:
I want to share an information who want to use Sierra now. If you decide to do below changes you need to know "Uploading App Store with beta software" not allowed by Apple. Continue with El Capitan and Xcode 7.3.1 for production.
If you want the slow solution, you can reinstall Xcode 7.3.1 by downloading it from https://developer.apple.com/download/more/.
It worked for me and now my Simulator is able to start again without getting the error.
The issue is discussed in depth here:
How to fix Xcode "DTAssetProviderService could not start.." error?
This seems to be a major bug. Until Apple fixes it, you can work around it:
Build app
The app will still install on the simulator, even with the error
Launch the app manually on the simulator
Go to Xcode
Click Debug > Attach to Process > Your App Name
That will enable Xcode debugging features and allow your app to run in simulator. Definitely not ideal, but hopefully you can use this until a real solution comes out.
This is a regression in macOS Sierra that multiple developers have reported in the forums and in the lab sessions at WWDC. Xcode 7.3 is not supported on Sierra. If you want to use macOS Sierra, please use Xcode 8.0 beta or later.
If you must use Xcode 7.3 on Sierra, you can partially workaround this bug by using Xcode.app to install the app through Build & Run, launch the app suspended from the command line (xcrun simctl launch -w booted <app identifier>) and then attach with the debugger and resume the suspended process.
Note that this issue only impact Xcode 7.3.1 downloaded from the Mac App Store. You will not hit this issue if you use Xcode downloaded from http://developer.apple.com (ie, the "drag & drop installer"). Note that you might hit another issue with the same symptoms when using the drag & drop installer. That is discussed in DTAssetProviderService could not start DTXConnection with Simulator
You can still run the debugger, but you have to attach it manually.
You can run your app tapping the icon in the simulator, than switch back to Xcode and select Debug, Attach to Process and pick your app process.
The following steps fixed the issue for me:
Remove both Xcode 7.3.1 and 8 Beta
Remove /Library/Developer and ~/Library/Developer (before removing check the contents and back up whatever you need)
Download the Xcode 7.3.1 DMG file and the Xcode 8 Beta xip file (unless you already have them)
Install 7.3.1 and test the Simulator (should work fine now)
Install 8 Beta and test the Simulator in 7.3.1 again (should work as before)
Restore what you backed up on step 2
I keep getting the error:
“Xcode cannot find the software image to install this version” on deployment?
I upgaded my iPhone to version 6.1.3 and also recently updated xcode to the lastest as well. Before doing this, I could deploy my apps to my phone, but now my apps won't deploy to my device.
Do I have to go and make another provisioning profile and all that stuff again? (I did it all a couple of months ago and got everything working when I was still on iOS 5).
Thx,
You need to upgrade the version of your Xcode to 4.6 in order to use your iOS 6.1.3 device for testing & deployment purposes.
The latest version of Xcode is 4.6.1. You can update it using Appstore App.
I had this issue. Eventually I found refreshing my provisioning profiles (in Organiser, select devices, in Library select Provisioning Profiles (top left) and click on refresh (bottom right). Then my devices accurately reflected my provisioning profiles and everything worked.
The message "xcode cannot find the software image to install this version" seen in the organiser window... This is just a notification rather than a problematic error.
Source: https://stackoverflow.com/a/8537034/736384
So, if it is a update problem, Rajan's answer should solve it, if not:
That message has nothing to do with the problem that you can not compile. When you want to compile, didn't Xcode show any message error?
Anyway you could try restarting Xcode (quit iTunes first if it's running).