I'm using phonegap build service for our iOS application, (the app is built on HTML5), and the delivered ipa file from phonegap works fine using a development provisioning profile on our devices. However, when attempting to load the app to the app store (using a release provisioning profile for itunes), we get this from the application loader
ERROR ITMS-9000: "Unsupported Architectures. Your executable contains
unsupported architectures '[12-11]'." at SoftwareAssets/SoftwareAsset
(MZItmspSoftwareAssetPackage)
This happens for versions 2.8 and 2.9 of Application loader. We're using Phonegap build service 2.7, 2.9 and 3.0. How can we determine what the "unsupported architectures" are from PhonegapBuild ? is there a method for identifying what features we are using that may be contributing to this error ?
I have managed to successfully upload the app. The issues was that I was running OSX 10.7.5 and running Application Loader 2.8 (AL), which seems to be compatible with Moutain Lion (10.8). Once upgrading to Mountain Lion you can do another update to 10.8.5 which will install Application Loader 2.9. (You can upgrade to 10.8 via the Apple=>"App Store" option on your Mac. It is a paid upgrade.)
If you downloaded the latest AL from the itunes connect portal and install it, it doesn't tell you that it's incompatible with older verions of Mac OSX before 10.8. All you'll get is an obscure message that your ipa is an "unsupported architecture" which in "Appleonean" means "You need to upgrade your version of OSX". Extremely misleading as it's nothing to do with your IPA, it's your OS. Even reading the PDF from Apple about AL there is no indication for minimum system requirements..
same here - this app previously uploaded fine but when I try a support update I get this error along with a warning about a missing icon of 120px, 76px, and 152px
Related
Problem summary : I would like to submit an app to the Apple App store (TestFlight). I am using Transporter v1.1 to submit the app. I am getting the following error in Transporter during the submission process. Please note that I am not using Xcode in this process.
Actual result:
ERROR ITMS-90596: "Invalid Bundle. The asset catalog at 'Payload/ExpoKitApp.app/GoogleMaps.bundle/GMSCoreResources.bundle/Assets.car' can't be processed. Rebuild your app, and all included extensions and frameworks, with the latest GM version of Xcode and resubmit."
Expected result : successful submission to the app store.
Development environment : Expo 36.0.0 / macOS High Sierra v 10.13.6 / Processor 2,3 GHz Intel Core i5 / Transporter v 1.1
What have I tried ? :
Deleting all node modules and installing them again (npm install).
Deleting any old Xcode folders on my mac. Please note that I am not using Xcode.
Checked the version of xcode in package-lock.json. It is 2.0.0 but it is being used as dependancy and not as a direct tool in the submission process.
Generate a new build thrice and submitting it once more in Transporter.
Can anyone please help me in this process ? I know this question has been asked before but the case is not applicable to me because I am not using xcode or application loader to submit the app.
This could help someone in a similar situation. Here is how I solved my problem with the advice of a senior developer.
Using expo diagnostics I found out the version of Xcode that my expo toolkit was using. The answer was undefined because I wasn't using Xcode at all.
Being on macOS High Sierra 10.13.6, I needed Xcode 10.1 for compatibility.
I downloaded Xcode 10.1 and also the compatible command line tools.
I transferred the installed Xcode from the downloads folder to applications folder.
Again ran expo diagnostics and noted that expo has taken into account the associated Xcode version.
Ran expo build:ios
Downloaded the .ipa file generated by expo on their server.
Submitted the .ipa file using Transporter to the Apple app store (TestFlight).
Successful submission.
I'll try to be as concise as possible but feel free to ask for further details.
First of all, on both machines code signing passes and there are no errors at any point in Xcode. When archiving app and exporting ipa on my MacBookPro the app successfully installs and runs on a device. When doing the same on our CI server (manually via Aqua session, not through a script) the app installs but crashes as soon as the app references any library with the following error: kernel(AppleMobileFileIntegrity)[0] <Error>: Library Validation failed: Rejecting '' (Team ID: , platform: ) for process '(<decode failure invalid size>)' (Team ID: <private>, platform: <missing data>), reason: <missing data>.
The only difference between server and my Mac configuration is that server runs on El Capitan and I've updated to Sierra.
Configuration:
Cocoapods v. 1.1.1
XCode v. 8.1 (8B62)
Provisioning profile permission: Enterprise distribution
OS versions are in discrepancy (read above)
I've searched a couple of days for the solution and didn't find anyone having the same problem, let alone solution for it. I've probably tried all that you are going to suggest, but I'm still hoping someone has a solution to propose without updating server to Sierra.
I installed the latest osx security update (https://support.apple.com/en-ca/HT207130) and tried to archive an update for my ios app. The archive was successful. However, after uploading the build to itunes connect with the Application loader, I received the following email :
When trying to submit my app for review I got this other error message :
I am clearly not running any beta build of macos or xcode. Here is my setup : OSX El Capitan 10.11.6, Xcode 7.3 (7D175)
Any one having the same issue? How did you get around this?
Since there have been many errors at iTunes Connect which Apple still can't solve on macOS Sierra (10.12) when uploading archives(build) of our applications,
You must use Xcode 8 no matter what on macOS Sierra
These are common errors that is happening when we upload our archive from Xcode 7.3.1 on macOS Sierra (10.12)
ERROR ITMS - 90163 (No.App bundle found)
Now your problem
Changing the build version or Xcode version from info.plist doesn't seen to worked. Believe me, I have tried many alternative hacking ways. Finally I gave up. Instead install Xcode 8 and Xcode 7.3.1 parallel on my mac because I am not ready for migration.
Archive your build from Xcode 7.3.1 and export it's ipa from App Store Release. Then, use Application Loader of Xcode 8 to upload your build to App Store.
Hope this help.
From this thread, try this:
I was able to submit without warnings or errors by digging into the
.xcarchive and modifying the info.plist of the app.
Change the key
<key>BuildMachineOSBuild</key>
<string>15G1004</string>
to the value for the original 10.11.6
<key>BuildMachineOSBuild</key>
<string>15G31</string>
Then export the IPA or submit to the app store as usual.
I didn't test so it could not fix your problem.
From this same thread, this seems to be a recurrent issue when Security Updates are released.
If #marco-santarossa's method does not work, you can wait for Apple to update iTunes Connect so that they accept the new OS build version, or contact support hoping they can speed this up.
I did and after a few hours the same build I had uploaded was submitted for review.
I have just updated my OSX to Yosemite, then I ran into an error when submitting a new build to TestFlight with the TestFlight desktop app.
error: /usr/bin/codesign --force
--preserve-metadata=identifier,entitlements,resource-rules --sign 2c30db522ceda29332f9f85951addff0276e0de1
--resource-rules=/tmp/sesLW20J9I/Payload/MyApp.app/ResourceRules.plist /tmp/sesLW20J9I/Payload/MyApp.app failed with error 1. Output:
Warning: usage of --preserve-metadata with option "resource-rules"
(deprecated in Mac OS X >= 10.10)! Warning: --resource-rules has been
deprecated in Mac OS X >= 10.10!
/tmp/sesLW20J9I/Payload/MyApp.app/ResourceRules.plist: cannot read
resources
Anyone has got an idea?
OK, finally I find a solution to this issue. It seems that the resource rules file is not generated by default in XCode 6.1.
To generate the resource rules file as before, go to project setting, search for
Code Signing Resource Rules Path, and set its value as
$(SDKROOT)/ResourceRules.plist
After this change, rebuild your target, TestFlight desktop app will work as before.
The app has not been updated to work on Yosemite (and I doubt it ever will because it was developed before Apple acquired TestFlight iirc and Apple has integrated the uploading process into Xcode.
I am trying to test my app on a device but am unable to do it as says that
"The version of iOS on “iPhone” does not match any of the versions of iOS supported for development with this installation of the iOS SDK. Please restore the device to a version of the OS listed below, or update to the latest version of the iOS SDK; which is available here.
OS Installed on iPhone
5.1 (9B179)
Xcode Supported iOS Versions
Latest
5.0 (9A334)
4.3
4.2"
Now I know that i have the latest iOS deployed in the iPhone. But my installed Xcode's version is "4.2.1" whereas in App Store the latest version is "4.3.2". Also, in App Store it shows up as "Installed" which means that I need to run the "Install Xcode" app from my applications.
Now, when I run "Install Xcode", it fails saying that there was an error encountered. In install.log file, the message logged is as below
"Failed install preflight: Error Domain=PKInstallErrorDomain Code=102
"The package “DeveloperTools.pkg” is untrusted."
UserInfo=0x7fc3c9e602a0 {NSLocalizedDescription=The package
“DeveloperTools.pkg” is untrusted.,
NSURL=../Packages/DeveloperTools.pkg --
file://localhost/Applications/Install%20Xcode.app/Contents/Resources/Xcode.mpkg/,
PKInstallPackageIdentifier=com.apple.pkg.DeveloperToolsLeo,
NSUnderlyingError=0x7fc3cbdc42d0 "The operation couldn’t be completed.
CSSMERR_TP_CERT_EXPIRED"}"
Now, how to fix it. I have ensured that there is no other software update pending in the system which may have potentially caused any issues in Xcode installation.
PS - I am using Lion, current Xcode version is Version 4.2.1 and the issue occurs on all iOS devices.
There was a problem with updating from 4.2 in the app store as noted here: https://developer.apple.com/xcode/ - which is why the app store is not letting you update eventhough you do not have the latest version.
It sounds from your question as if you are trying to reinstall using the installer you already have. If you have not done so already you should log into the apple dev center and download the installer from there (from full tools download list - main screen just links to app store). once on 4.3 updating from app store for future updates should work fine.