I use the Xcode7 release and tried so submit my app for review. After submitting the app for review I got a mail from Apple with the following error:
Invalid Bundle - Failed to verify bitcode in
testapp_main.framework/testapp_main: error: Bundle only contains
bitcode-marker Testapp.app/Frameworks/testapp_main.framework/testapp_main (armv7) ...
I also disabled bitcode in my Build Settings:
How do I solve this issue?
I'm having the same issue. Bitcode is enabled in both the framework that I've created myself and the incorporating project. Architectures are arm64, armv7, armv7s. Deployment target is iOS 8.0. SDK is iOS 9 (Xcode 7.0.1).
These are the errors that I get when it fails:
"Solution"
When trying to validate or submit to iTunes Connect, unchecking either "Include app symbols..." or "Include bitcode" allows validation to succeed. It's just when both of them are checked that it fails. I wouldn't really consider this a solution though.. You either have to give up receiving crash logs or utilizing app thinking, both of which would be preferably enabled. This is just a temporary workaround until someone else can figure out what is really causing the issue.
Encountered this issue when trying to Archive a flutter project.
The solution I found is to to uncheck Rebuild from Bitcode, and click Next before the error shows up.
Related
I am attempting to upload a watchOS3 app to the apple store, however I received a rejection (from apple) thats similar the below
Invalid Executable - The executable 'someWatch Extension' does not contain bitcode.
Once these issues have been corrected, you can then redeliver the corrected binary.
How can I resolve this? It seems like bitcode is mandatory as there is no longer a build setting in Xcode for my watch application to simply "Enable Bitcode=No".
I have also tried looking into running swiftc -embed-bitcode *.swift from my Watch Extensions directory, but I receive the below
MyController.swift:9:8: error: no such module 'WatchKit'
import WatchKit
I really have no clue what to do from here and it UBER frustrating with the lack of documentation out there for watchOS3 to get around this. PLEASE HELP
For me the problem was that ENABLE_BITCODE=NO was set on the project level, and even though Watch did not have it set and should have resolved to YES which is the default for WatchOS, it was still resolved to NO - because of the inherited value from the project.
To resolve it, I removed the ENABLE_BITCODE value at the project level.
(to do this, select it in the Project Build Settings and press delete button on your keyboard so that text loses its boldness).
I was having some trouble uploading my Ionic Ios App to the App Store through Xcode(v 7.2).
I was constantly faced with the error: "upload failed: You are not authorized to use this service for provider XXXXXX"
After some careful problem solving I was able to resolve that I needed to have "Enable Bitcode: Yes" under my project's Target. This allowed me to upload the app through Application Loader by exporting the app with bitcode attached.
My question is in terms of my wanting to better understand what is going on under the hood here.
What difference did the enabling of bitcode make to allow the app to upload vs not having it? I tested this out to confirm and this one change was the difference in the success and failure of uploading.
Thanks.
What difference did the enabling of bitcode make to allow the app to upload vs not having it? I tested this out to confirm and this one change was the difference in the success and failure of uploading.
->You don't need to Set Yes to bitcode for iOS apps. Enabling bitcode might have simply recompiled your libraries ( above error looks like an profile error). To prove this theory, disable bitcode (Set Value to No) recompile and upload on iTunes.
Refer to this link
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AppThinning/AppThinning.html
For iOS apps, bitcode is the default, but optional. For watchOS and tvOS apps, bitcode is required. If you provide bitcode, all apps and frameworks in the app bundle (all targets in the project) need to include bitcode.
I am trying to archive my app and submit it to iTunes store. But I can't pass the validation.
Xcode always reported "Symbols tool failed."
I tried to archive and validate it by using Xcode 6.0 on 10.9 and Xcode 6.1 beta on 10.10 beta. Both are not working.
I will be appreciated for any help.
And IDEDistribution.stardard.log reported error like below:
2014-09-21 01:53:14 +0000 [MT] Validation failed for archive Europa with issues:
(
"<IDEDistributionIssue: severity(error), error(Error Domain=ITunesSoftwareServiceErrorDomain Code=-21013 \"The archive is invalid. /var/folders/dm/gps585zj4kvg0_9hlty6y8b00000gn/T/XCodeDistPipeline.FfM/Europa.ipa does not exist.\" UserInfo=0x7ff35a93a810 {NSLocalizedDescription=The archive is invalid. /var/folders/dm/gps585zj4kvg0_9hlty6y8b00000gn/T/XCodeDistPipeline.FfM/Europa.ipa does not exist., NSLocalizedFailureReason=Unable to validate your application.})>"
)
2014-09-21 01:53:14 +0000 [MT] Canceled distribution assistant
UPDATE: I find out that it can pass the validation when I uncheck "Include app symbols for your application to receive symbolicated crash logs from Apple" options. Does swift framework not support this feature?
I was able to resolve it by the following operations in Xcode.
I want to select a target on TARGETS.
I select the Build Phases.
I want to expand the Copy Bundle Resources.
To remove unnecessary files and libraries of the plug-in if it has been registered.
I was having a similar problem - assumed it was a profile/sign issue with XCode 6.0.1 - however, your note to uncheck the 'Include app symbols' fixed the problem for me.
uncheck "Include app symbols for your application to receive symbolicated crash logs from Apple". Organizer -> Submit...
In my case I accidentally had a static library in "Build Settings" -> "Embed Framework". Removing the static library from there helped.
There is also a similar question: Client.ipa does not contain a file
If the cleanup of "Copy Bundle Resources" didn't work for you, check if Link time Optimisation is switched on for your release build. Set it to NO.
Hi I just tried to upload my app to the app store but it failed with error.
**
No architectures in the binary. Lipo failed to detect any
architectures in the bundle executable.
**
That can also happen when the Cocoapods cache is not in sync, then just
pod install
solves the issue.
Hi I'm glad i found the Answer. The problem was actually with my 'Productname' in info.plist . It was different in my first version.
Same thing. Had this issue. I just changed
Project -> Build Settings -> Produc Name (wrote: "Wundmanager")
then
Project -> General -> Identity -> Bundle Identifier (wrote "imeksbank.Wundmanager")
my nick is imeksbank
and then
iTunes Connect and the same to Bundle-ID (chnaged "imeksbank.Wundmanager")
After that it worked for me. I am also new and today is my first day i can Upload my first App.
xcode 5.1.1
ios 7.1
Can also be caused by embedding a static framework (mistaking it for a dynamic one) in your app. Easily done if you build in different phases and/or allow xcode to "build implicit dependencies".
After a long struggle with an error message like this, I finally understood that mistakenly an iOS framework had been copied into the IPA. This was added automatically following the usual steps to add a framework to an iOS project.
So the solution would be to remove "Embed Frameworks" phase from "Build Phases".
I was able to get past this error by restarting Xcode.
Sometimes cleaning your project quitting and re archiving will solve the issue. In my case it worked. I don't have any issues with the bundle name, identifier or plist.
When trying to archive an app for an Ad Hoc release, I am getting the following warning:
iPhone/iPod Touch: application executable contains unsupported architecture(s): armv7s (-19031)
I am really not sure why this is happening for two reasons:
The only non-foundation framework I am using is the Facebook SDK, which is the latest version
I successfully archived the app last week and the only things that have changed since then are purely coding changes.
Also, I have tried archiving with and without an iPhone 5 plugged in, and I receive the error both ways.
Does anybody know how to fix this?
Quick fix is
Remove armv7s from
Project -> Build Settings -> Architecures
Updated ::
Now change Build Active Architecture in Build Settings to No to Yes.
But even this is not a pure solution to this problem.
I could archive and validate my projects by changing status of 'Build Settings -> Build Active Architecture Only' from 'No' to 'Yes'.
Same problem here today when submit my app (update) to appstore.
I clearly remember that its last version was submitted with both armv7 and armv7s set and succeeded, but now Organizer told me :
"iPhone/iPod Touch : application executable contains unsupported architecture(s): armv7s"
to remove armv7s is simple, but my app is Universal, will the armv7s-removed app run on all iOS devices (iPhone 5 for example)? when should i build with aremv7s?
Same issues here, app passed validation before, but after a quick code change, no go. Could this possibly have something to do with ipods? Seems to be a recent issue, as of yesterday.
Getting the same result as 21k. I submitted a binary with both armv7 and armv7s to the App Store last week, and it passed validation as well as the review. Now I tried submitting an update to the same app with the exact same project settings (other than the usual version number bump), and it fails validation.
In fact, I try validating the archived app from last week and now get the same error. So something must have changed on the App Store's side.
Go to Project ---> Build Settings and scroll down to the Architecture setting.
You will probably see the value $(ARCHS_STANDARD_32_BIT) listed under Architecture.
If so, double-click $(ARCHS_STANDARD_32_BIT), select it, and click the minus button to get rid of it. Then click the plus button and write armv7 and press Enter.
You have now removed armv7s, which was unsupported. Try it again and things should be good.
Removes armv7s architecture from menu Build settings > Architectures. At that point must appear valid architectural amrv7s and amrv7. Removes only finished in s. If the menu doesn't appears, notice that it is set to "All" and "Combined" in the search bar.