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!
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.
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 ;).
iOS simulator crash in iOS 8.2 and Xcode 6.2 with an error below
"Failed to lookup the process ID of xxx.xxx.xxx after successful launch. Perhaps it crashed after launch. No such process".
And I cannot try to simulate my app.
I uploaded the image of error.
http://imgur.com/2ayGys3
It works normally when i use iOS 8.1 as a simulator. Regardless of the types of devices and types of projects, it will crash in iOS 8.2 simulator.
The iOS simulator itself stands but has nothing on the screen.
A thing I care is that I changed my old macbook to new one and copy project files of Xcode from old to new.
Do you have any idea of this?..
I had the same problem and solved it by force quitting and restarting Xcode and iOS Simulator.
I had the same problem after I did a Mac update on xcode. I had the IOS simulator open during the install/update process. When I closed it, re-ran my compile, it re-opened the simulator and ran fine.
Simulator -> Reset Content and Settings did it for me.
In my case, all I needed to do was: Hardware -> Reboot on simulator.
I had the same problem, in my case the issue was :-
Have set "Build active architectures : NO". Just changed it to YES and it worked.
Even i had the same issue when i upgraded Xcode to 6.3.2. I just did re launch of Xcode and iPhone Simulator and worked for me.
I'm using xcode 7 beta 2 and am having the same problem.
My take is that this is a random error probably due to a race condition.
If I start xcode, then simply run my app over and over again, the error occurs randomly. Typically it will work 1 to 3 times in a row and then will fail 1 to 3 times in a row. The most consecutive failures I have seen so far is 3.
It might be the case that your app is not set up to build for the proper platform for simulator which are i.e. i386, x86_64.
It happened to me as I built for arm64 platform, and try to hook it up to simulator; built via xcodebuild command line. But I think you might want to try because basically Xcode use that tool to build things up for you.
So check the following in Build Setting of Xcode (along the line of text similar to this)
Only Build Active Arch => YES
Build architecture => i386 (or set to something else but not for mobile architecture)
I keep getting this error in AppCode, but usually it runs just fine with Xcode:
Error:xcodebuild: error: The run destination iPad Mini is not valid
for Running the scheme 'Appname'. Error:iPad Mini doesn't match any of
Appname.app's targeted device families. You can expand Appname.app's
targeted device families to support iPad Mini. Error:Build failed with
2 errors and 0 warnings in 7 sec Note:Building for 2 architectures.
Double click to set 'ONLY_ACTIVE_ARCH=YES' to speed up compilation.
Target sdk is 7.1 in AppCode 3.0.6 (Xcode 6.1)
TARGETED_DEVICE_FAMILY = 2 (iPad)
VALID_ARCHS = armv7 armv7s i386 arm64
Architectures = Standard architectures (armv7, arm64)
I have the problem with both an iPad Mini with iOS 8.1 and a iPad 4 with iOS 7.1.
Any idea why it will not work from AppCode?
According to JetBrains, it's a problem with the xcodebuild tool in Xcode 6 rather than being an issue with AppCode. Hopefully something Apple will fix soon!
https://youtrack.jetbrains.com/issue/OC-11204
I had that as well: Xcode builds fine, Appcode does not. There is no evident reason for that - the target etc looks fine. It seems to be a bug in AppCode 3.0.6 that seems to be fixed in the 3.1 EAP version. With 3.1 the project builds fine here.
Just had this problem as well in Appcode. If you set "Targeted Device Family" in Appcode's target to "1,2" (iPhone and iPad), it worked here.
Go To Build Settings ->
in search bar, search "targeted"
change in Universal
You need to check Development info like development target, Device and match with the simulator device.
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.