Yesterday, I\'ve downloaded beta version of Xcode 11. After that, I\'ve opened my project and tried to run with new Xcode. Unfortunately error has occurred with message:
In my case it was running the simulator/coresimulator version for 11 beta vs the one for 10.1 -> Killing and letting Xcode reopen the simulator solved the problem.
Adding onto this, I noticed that if your CFBundleVersion does not spec out to:
This key is a machine-readable string composed of one to three period-separated integers, such as 10.14.1. The string can only contain numeric characters (0-9) and periods.
it will not build on simulator
link
If you get the following running error.
(* see the attached screenshots below)
This is how you can to solve this issue.
Done in few steps.
Step 1) Go to your project navigator in Xcode.
Step 2) In the info.plist.
Select the (Bundle Version) field.
Change it is value to a single digit, from (4.0) to (4) instead. by removing any decimal period.
Step 3) Add a * (Bundle versions string, short) below the (Bundle Version)
// Hint: Select the + sign to browse it if necessary .
Step 4) In the Value field (String), add the version, but with decimal period this time.
So if the (Bundle Version) is 4, make sure to add a period to it 4.0
Step 5) Build Succeed.
Happy Coding :-)
There is a lot of misinformation in the answers here, so I wanted to provide an authoritative response.
The issue here is that the new version of CoreSimulator.framework with Xcode 11 beta does validation on CFBundleVersion that previous versions did not do. These checks are valid, and it does represent an issue in your application, but there's also a bug in how the checks were performed in Xcode 11 Beta 1 which compounds the issue.
First, fix the CFBundleVersion in your Info.plist. It should consist of only numbers and up to two periods (ie ##.[.##[.##]], eg: 12.4.2).
Second, after fixing CFBundleVersion, you need to killall -9 CoreSimulatorBridge
because the old value is unfortunately cached in CoreSimulatorBridge, preventing it from recognizing the new value. This part was a bug, and it was addressed in Xcode 11 Beta 2.
I was confronting this problem yesterday. The situation is that I pull my code from git and tried to compile, after that, I may not able to run my app on the simulator (Or archive app to submit to the app store, the version number has not been put into archive info list, no version information as 1.3.4(123)). The error message is CFbundleVersion is not correctly setup. My Xcode version is 11.4 (11E146).
so I tried following the method:
Fix the CFBundleVersion in your Info.plist.(setup correct version format, numbers or X.X.XX)
change the Bundle identifier, for instance, add a prefix address com.example to com.example.test. Then try to compile and install the app on the simulator. Right now, you could see the app can install normally.
Then change Bundle identifier to your original one, such as com.example. Then try again, you will see you could install the app on the simulator or archive normally.
In my case, the "Build Version" field on my target was empty, I changed it to 1 and the app was able to install.