I am running Xcode 13.0 with the Swift 5.5 toolchain.
When I load the pod 'Firebase/Firestore' and try to build, I get the following error:
Missing '#include <stdlib.h>'; 'abort' must be declared before it is
used
A screenshot of the code that is being highlighted below:
Note, that I have stripped this back so that I have zero code in my project - only the default that is provided with a new project.
Note, that I have stripped this back so that I have zero code in my project - only the default that is provided with a new project.
Update to a recent version of Firebase. The issue was fixed in March in https://github.com/firebase/firebase-ios-sdk/issues/7552
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:
Failed to install the requested application
Domain: NSPOSIXErrorDomain
Code: 22
Failure Reason: The application's CFBundleVersion is invalid.
Recovery Suggestion: Ensure your bundle contains a CFBundleVersion with a valid semantic version number.
--
I've closed beta version and tried to run again with latest stable version of Xcode (10.2.1), but the same error has occurred. I need to mention that before attempting to run a project with Xocde 11, it worked without any problems on Xcode 10. Nothing has been changed before and after running with beta Xcode.
What I've already tried:
I've removed Xcode 11 beta
I've cleaned my project and pulled it from latest branch
I've completely removed Xcode 10 from:
~/Library/Caches/com.apple.dt.Xcode
~/Library/Developer
~/Library/MobileDevice
~/Library/Preferences/com.apple.dt.Xcode.plist
/Library/Preferences/com.apple.dt.Xcode.plist
/System/Library/Receipts/com.apple.pkg.XcodeExtensionSupport.bom
/System/Library/Receipts/com.apple.pkg.XcodeExtensionSupport.plist
/System/Library/Receipts/com.apple.pkg.XcodeSystemResources.bom
/System/Library/Receipts/com.apple.pkg.XcodeSystemResources.plist
And then installed fresh stable version 10.2.1
I can run other projects which was not tested with Xcode 11 without any problems.
My last idea is to just reinstall macOS, but I would like to don't do it.
Edit: I’ve forgot to mention that application is working on physical iPhone XS.
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.
Happened to me too, wasted almost an entire day scouting for possible causes.
The steps that finally fixed the problem and allowed me to install on simulator:
Quit Xcode and iOS Simulator
Remove /Library/Developer (the one from root), or rename it if you want to keep a backup
Relaunch Xcode, agree with the installation of command line tools
Continue work where you left over :)
Besides the steps mentioned in the question (fully uninstall Xcode 11, fully uninstall Xcode 10 and reinstall it afterwards), I also tried cloning the project in another location, circulating through all possible locations for derived data, installing other simulator runtimes and trying on those. None of them worked, luckily the console log app shown the path for the process that rejected the app bundle, it was one of the binaries installed by Xcode in /Library/Developer/PrivateFrameworks/CoreSimulator.framework.
Seems that Xcode 11 installed a newer version of the frameworks, and Xcode 10 was not overwriting them. Removing the whole /Library/Developer folder triggered the command line tools installation, which finally brought back the simulator runtime that properly worked in Xcode 10.
You gotta love the betas :)
I went to targets and found "Version" field is empty, just fill a number, for example 1.0
I had the same problem.
I find the Xcode 11 Beta Release Notes had explain it.
Bundles without a CFBundleVersion are invalid and can’t be properly installed on
devices or simulators. CoreSimulator now checks and rejects such bundles earlier in
the process with a clearer error message. (49892531)
And this link is the format of CFBundleVersion.
When I resolved this problem, I found out if having the CFBundleVersion problem when running App for the first time. Then it always has problem no matter whether the format is correct or not. So I restart the Xcode and the Simulator, and change the CFBundleVersion to a correct format, the App running correctly.
Combining Sgeven.Zheng and Cristik's answers.
CAUSE
Installing Xcode11 Beta installs a new version of CoreSimulator.framework with the following update:
https://developer.apple.com/documentation/xcode_release_notes/xcode_11_beta_release_notes
"Bundles without a CFBundleVersion are invalid and can't be properly
installed on devices or simulators. CoreSimulator now checks and
rejects such bundles earlier in the process with a clearer error
message. (49892531)"
The following won't fix the issue:
Uninstalling Xcode11 Beta
Uninstalling and reinstalling Xcode 10
This is because CoreSimulator.framework is installed in /Library/Developer/PrivateFrameworks/CoreSimulator.framework, which is outside the Xcode.app bundle.
When re-installed, xcode10 detects that the currently installed version of CoreSimulator.framework is newer than what xcode10 would have installed, so it leaves it as-is.
SHORT-TERM FIX
Uninstall xcode11
Install Xcode 10 (No need to re-install if it's already installed)
Remove /Library/Developer/PrivateFrameworks/CoreSimulator.framework
Launch Xcode 10 and agree to install command line tools
LONG-TERM FIX
Since this is not a "real" bug but is instead the intended behavior of Xcode11, steps will eventually need to be taken to ensure that apps are always built with a valid CFBundleVersion.
In my case, the "Build Version" field on my target was empty, I changed it to 1 and the app was able to install.
Hi I've resolved just now with this:
I had in my info.plist only this key:
<key>CFBundleShortVersionString</key>
<string>2.1</string>
... and so now all works adding this:
<key>CFBundleVersion</key>
<string>2.1</string>
with the simulator that works again....
NOTE: without CFBundleVersion my app had worked perfectly on physical device!!!
It's a new feature in Xcode11.
In release note it said:
Bundles without a CFBundleVersion are invalid and can’t be properly installed on devices or simulators. CoreSimulator now checks and rejects such bundles earlier in the process with a clearer error message. (49892531)
You can:
Edit your CFBundleVersion by the style of this LINK
Reset your Xcode and simulator
Run again, you will see it works again
When you run app in simulator success, you can change back your CFBundleVersion again, you will found it still can work XD
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.
find the info.plist then select it
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
See this picture for guidance.
Step 5) Build Succeed.
Happy Coding :-)
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
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.
In my case, the Build Version field was empty. I added the value there but still it didn't work. I tried killall -9 CoreSimulatorBridge command and that also didn't help.
Finally when I checked the xml of the info.plist (Open as -> Source code), the CFBundleVersion key was not present and the version was displayed in the info.plist through CFBundleShortVersionString.
I just added the CFBundleVersion key as given below in the info.plist and it worked.
<key>CFBundleVersion</key>
<string>$(MARKETING_VERSION)</string>
I hope it helps someone else too.
I ran into this same issue as well.
I didn't get so far as to trying some of the other options provided here, but I was able to get back to building for simulator by simply deleting the /DerivedData directory.
If you're unsure as to where to find it, simply do this:
Xcode -> Preferences -> Locations
and select the arrow next to the path for Derived Data
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 Xcode Version 12.0 beta 3 I was having continuous problem launching the Simulator. I tried all the above mentioned techniques. Nothing worked.
I solved by adding this property to the Info.plist:
Bundle version string (short) and
setting its value to 1.0
See Image Here
I faced a similar issue for hours, this is what actually worked for me.
Navigate to the Resources folder
Find Info.plist
Add a key-value pair: CFBundleShortVersionString:
Clean Build Folder
Clear Device Cache
Run and Build
After upgrade from Xcode 13.2.x to 13.4.x my app archive started to show in organizer in section "Other items" not in "iOS apps". Also in organizer app has empty version. Build to iPhone was working, build on simulator failed due to error, that I do not have CFBundleVersion in Info.plist - but I had it there. I had fixed number (not variable) and it is root of problem. I had to change static values to variables....
File Info.plist
// OLD incorrect
<key>CFBundleVersion</key>
<string>345</string>
<key>CFBundleShortVersionString</key>
<string>1.2.3</string>
// NEW correct
<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>
<key>CFBundleShortVersionString</key>
<string>$(MARKETING_VERSION)</string>
File project.pbxproj
...
CURRENT_PROJECT_VERSION = 345;
MARKETING_VERSION = 1.2.3;
...
And additionally I had to add variables to file project.pbxproj to Release and Debug sections because I did not have it there. So with older Xcode it was working this way and versions was taken from Info.plist. Now it seems that source of true are variables from project.pbxproj but Apple have incorrect error messages because it is fail to say in error that CFBundleVersion is missing in Info.plist when it is there. Finally Xcode automatically deleted CFBundleVersion and CFBundleShortVersionString from Info.plist.
I have spent many many hours of finding out what is problem. I hate upgrading Xcode - nightmare, many hours always lost.
For some reason today I am no longer able to deploy my Xamarin.Forms app to any android emulators. The emulators were working previously. The error I am seeing in the deployment pad is
"Mono.AndroidTools.SdkNotSupportedException: The device does not support the minimum SDK level specified in the manifest".
It seems the answer to this is usually that the manifest is just not matching the SDK version of the emulator, however I've checked and I have it set to a minimum of 26 and target of 28. The emulators are on version 27. I tried setting both min/target to 27 as well, but same result.
I have a few theories as to what change may have happened.
I recently began preparing the app for google play and I added a package name, where I didn't have one before.
I changed the version number to 2 from 1. Also the version name is 2.
Updating visual studio (mac)
Any ideas what else I should check?
In case anyone else hits this issue, it was caused by a blank inside my Debug|Android configuration block in my csproj. It was created that way using the previous VS Mac IDE.
There is another AndroidManifest element inside my main PropertyGroup, so deleting the blank one (or adding the path to AndroidManifest.xml here) makes the initial error go away.
For additional details, refer to this solution
I'm getting a lot of unused variable errors after updating to the new version of and Xcode 5.1.
Compiler is saying unused variables are errors, and checked the compiler settings that i didn't modify treating warning as errors.
This only happened after I updated to Xcode 5.1
There seems to be indeed an issue with Facebook iOS SDK and compiling on Xcode 5.1 even if compiling it by itself.
I opened a bug in the Facebook support system:
https://developers.facebook.com/x/bugs/1449419898627543/
As a temporary workaround - you can fix it by turning off treating warnings as errors ( a very good practice by itself btw I use for our SDK) by:
1. Open the Facebook proj file (or the project inside an existing project
2. Go to build settings of the entire project
3. Change the "Treat Warnings as Errors" field from YES to NO.
This will let you compile it even with these warnings - but do be alert for an updated sdk in the coming days.
The problem was that we were unintentionally compiling for 64bit in the internal compiler settings somewhere inside our scripts. Please be aware.
I have to proceed with an existing phoengap application using phonegap 1.5 .
But when i am installing phonegap in my xcode 4.5.2 , I am not getting any option for "Phonegap based project" .
I am sure i have ios SDK and everything else required , but dont know what is wrong here .
Stucked in the same issue for weeks and no output.
In th latest versions of PhoneGap, there wont be any template in XCode available. You need to use command line to create a new project. This link tells how to do it : http://docs.phonegap.com/en/2.5.0/guide_getting-started_ios_index.md.html#Getting%20Started%20with%20iOS
Check the Project Creation section.