I installed Xcode 9 and trying to run my app on ios simulator 11.0. As soon as it launches the app its crashing giving this error. What does this error mean? If my app is not compatible with ios11.0, how can I check for the compatibily?
EDIT - Uploaded my valid Architectures
You need to make these changes in build setting ... it works for me
I had the same problem and found out that the architectures and valid architectures settings for my targets (and pods) were set wrong. iOS 11 doesn't support 32bit applications anymore, so I guess that took part in my problem..,
I've deleted my architectures + valid architectures settings (made it default) and now it compiles and runs fine in both simulator and iOS 11 device. hope it helps u as well ;).
Related
When trying to build and install an application on an iPod running iOS 4.2.1, I'm seeing the error
This application does not support this device's CPU type
I'm trying to build the application using xcode 4.3, as well as xcode 4.4, and still seeing this. What can cause this and how can I fix it?
I have encountered such a problem today on iOS 11.2.1 with iPhone 7 devices.
The reason is that the previous project set up a 32-bit architecture that is no longer supported.
And I solved the problem as follows：
Project -> Build Settings -> Architectures value should be set Standard architectures - $(ARCHS_STANDARD)
From the project build settings -> Architectures, make sure you have both armv6 and armv7 values.
Also, you can check your Info.plist file, under Required device capabilities. If there's armv7 there, remove it.
If you are getting this error building Unity 3D application, change scripting backend to IL2CPP, and select "Universal" architecture.
This post led me to my answer. Thanks #adig and #masam
I have an iOS 8.4 enterprise signed app that would only work on certain device types when I tried to install it from our internal app store, and it was inconsistent. I wasn't getting any helpful error messages, even from the device console, until I tried to deploy it using the XCode Devices to a 5th gen iPod. It said "This application does not support this device type" which led me to here. I was debugging on a 6th gen iPod/iPhone 6.
I was archiving from a different scheme than I usually release from and I was only building the current architecture which meant that it would only work on a certain type of device depending on what was plugged in when I archived.
So make sure that "build active architecture only" is NO when you are archiving an app to sign as an Enterprise app.
When trying to validate my new app using watchkit with xcode 6.2 I get a strange error:
iTunes Store operation failed.
Unsupported architectures. Your executable contains unsupported architectures '[armv7k]'.
What does armv7k even mean?
All my build settings (for the app and all extensions) look like the ones in the following screenshot:
Could the red color of my embedded binaries have something to do with the problem? Everything works great on my device and on the simulators.
Thanks in advance!
Update:
xCode 6.2 and iOS 8.2 was released. Problem is still there.
It's more than likely not passing validation as you can't actually submit watch apps yet.
Per https://developer.apple.com/watchkit/:
Please Note: Apps built with Xcode 6.2 and iOS 8.2 SDK may be submitted to the App Store. However, WatchKit extensions are not accepted at this time.
I think this is architecture of new Apple Watch. It is not architecture of your main app so you can't see it in build settings of your app. For sure it is impossible to submit app from Xcode beta.
I have the same issue but from Xcode 6.2 (not beta). May be itunesconnect does't support watchkit extensions yet.
I'm getting this error whenever I build in Xcode 6 GM Seed. It seems to be making my app insanely slow. What exactly does this mean and how do I fix it?
I had the following error:
Warning: Error creating LLDB target at path '.....'- using an empty
LLDB target which can cause slow memory reads from remote devices.
PS: im not able to run my app, its stuck on the splash screen
There is a thread in the Apple Developer Forum, https://devforums.apple.com/message/1010068#1010068 that describes how to diagnose this issue. I had his issue for Xcode 6 GM Seed, specifically - Version 6.0.1 (6A317). This isn't necessarily a solution, but it may help some people get a better diagnosis
Useful steps are as follows -
1) Create or modify your ~/.lldbinit and add log enable -f /tmp/lldb-api.txt lldb api to it.
2) Rerun your debugger session (no need to restart Xcode or anything)
3) Inspect the file at /tmp/lldb-api.txt. Look for a line beginning with SBDebugger::CreateTarget(...). Mine looked something like this
SBDebugger(0x7f83671fd600)::CreateTarget
(filename="/Users/xxxxxxx/Library/Developer/Xcode/DerivedData/Dino-gjuxikhuyokkqufeqmesmgjcxylu/Build/Products/Debug-iphonesimulator/Dino.app",
triple=x86_64, platform_name=(null), add_dependent_modules=1,
error=the specified architecture 'x86_64' is not compatible with
'i386-apple-ios' in
'/Users/xxxxxxx/Library/Developer/Xcode/DerivedData/Dino-gjuxikhuyokkqufeqmesmgjcxylu/Build/Products/Debug-iphonesimulator/Dino.app/Dino')
=> SBTarget(0x0)
4) Inspect the target file from the above log output, in my case -
file
"/Users/xxxxxxx/Library/Developer/Xcode/DerivedData/Dino-gjuxikhuyokkqufeqmesmgjcxylu/Build/Products/Debug-iphonesimulator/Dino.app/Dino"
/Users/apanagar/Library/Developer/Xcode/DerivedData/Dino-gjuxikhuyokkqufeqmesmgjcxylu/Build/Products/Debug-iphonesimulator/Dino.app/Dino:
Mach-O executable i386
5) So, In my case my problem was the architectures I was building for. The target architecture for your project should match the one on the SBDebugger::CreateTarget() line in the log output.
Xcode doc's point out the following. I had to go through my nested frameworks and change some outdated architecture targets -
NOTE ABOUT 64-BIT ARCHITECTURE
An app extension target must include the arm64 architecture in its
Architectures build settings or it will be rejected by the App Store.
Xcode includes this architecture with its “Standard architectures”
setting when you create a new app extension target.
If your containing app target links to an embedded framework, the app
must also include the arm64 architecture or it will be rejected by the
App Store.
For more information about 64-bit development, see 64-Bit Transition
Guide for Cocoa Touch or 64-Bit Transition Guide for Cocoa, depending
on your target platform.
https://developer.apple.com/library/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionCreation.html#//apple_ref/doc/uid/TP40014214-CH5-SW1
I am not sure if this will help in your case. But I tried this solution and it worked pretty neatly for me.
Pull up the terminal and type - rm -rf ~/Library/Developer/Xcode/DerivedData
This is supposed to remove the huge stack of DerivedData folder and make the app execute faster.
Did you use Architectures=$(ARCHS_STANDARD_32_BIT) and run your app on a 64 bit device? (iPhone 5S or iPhone 5S simulator)
Apple seems to be stricter with apps which don't support 64bit. So if there is no specific reason, I think it's better to include arm64 in your build architecture
NOTE ABOUT 64-BIT ARCHITECTURE
An app extension target must include the arm64 architecture in its
Architectures build settings or it will be rejected by the App Store.
Xcode includes this architecture with its “Standard architectures”
setting when you create a new app extension target.
If your containing app target links to an embedded framework, the app
must also include the arm64 architecture or it will be rejected by the
App Store.
For more information about 64-bit development, see 64-Bit Transition
Guide for Cocoa Touch or 64-Bit Transition Guide for Cocoa, depending
on your target platform.
Source:
https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionCreation.html#//apple_ref/doc/uid/TP40014214-CH5-SW1
This warning is solved by changing Build Settings :
Select Project -> Build Settings
Change 'Architectures' to 'Standard architectures (armv7, arm64) - $(ARCHS_STANDARD)'
This will prompt an alert stating iOS 5.1.1 and above are supported. Click 'Change Deployment Target to 5.1.1'
Repeat steps for Target (if not changed automatically)
Also, this is preferred build setting since Apple is forcing developers to build apps on 64 but architecture. Apple document Link
Since update to XCode 4.5 I am unable to open my apps in the simulator.
It says "Finished Running on iPhone 5.0 Simulator".
Sometimes, after retrying twice or thrice, the Simulator finally launches but the App never starts in it.
I am getting mad with this new version of XCode.
I have started a brand new project with a simple "Hello World" view. Even a clean brand new project cannot solve the problem.
Am I really missing something hidden in the config ?
Thanks
Lionel
Edit 9/21
When I try to run on my iPad 2 with iOS 5.1, I have the following error that may be linked to what I described above :
"Choose a destination with a supported architecture in order to run on this device."
My Project deployment target is 5.0
My Project build settings : Valid architectures = armv7 armv7s
My Target deployment target is 5.0
My Target base SDK is 6.0
My Target valid architectures are : armv7 armv7s
On my iPhone 4 updated to iOS 6 : same error.
Again, I started from scratch, deleting all information from the app and putting back each file carefully, and everything works seamlessly.
It's pretty unlikely it's any of your settings. Xcode just gets into a weird state like that sometimes. Usual fixes are force quit Xcode, force quit simulator, reboot.
I have to update an application for iOS, which is running from iOS 3.1.3 to the latest 5.1.
When I build the code on the new Xcode 4.3.1 and try to test this app on an old device with iOS 3.1.3 I get an error "Bad CPU type on executable".
iOS Deployment Target = 3.1.3
Architectures = armv6 $(ARCHS_STANDARD_32_BIT) - armv6 $
Valid Architectures = armv6 armv7
If I add armv5 to the list of valid architectures, the code is installed on the device, but the application starts with a black screen and nothing happens.
Then I can stop the program and start it on the device. It seems to be working then.
Is it allowed to add armv5 to the list of valid architectures? Is this the solution to get rid of the error?
I saw the same problem today with iOS 4.1 and Xcode 4.3.3. The fix - just re-open Xcode and re-connect the phone.
I resolve this magic problem after "Reset network settings" in device (on iPad2 and iPhone3GS). It's pure magic!