I got the following error after adding a third party framework to my projectdyld: Library not loaded: @rpath/NMAKit.framework/NMAKitReason: image not foundI tried to resolve this by adding that framework under Embedded Binaries Tab, then I can run the project but couldn't upload binary to iTunesConnect, got following set of errors,ERROR ITMS-90086: Missing 64-bit support. iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK or later. We recommend using the default Standard Architectures build setting for Architectures in Xcode, to build a single binary with both 32-bit and 64-bit support.ERROR ITMS-90086: Missing 64-bit support. iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK or later. We recommend using the default Standard Architectures build setting for Architectures in Xcode, to build a single binary with both 32-bit and 64-bit support. ERROR ITMS-90087: Unsupported Architectures. The exec
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hey All,I'm starting the journey to incorporating Core-Data-iCloud syncing into my App for the first itme. I'm following the guide located here:https://developer.apple.com/library/ios/documentation/DataManagement/Conceptual/UsingCoreDataWithiCloudPG/UsingSQLiteStoragewithiCloud/UsingSQLiteStoragewithiCloud.htmlSure enough, on the first checkpoint I'm already having issues. My app reports: -[PFUbiquitySetupAssistant finishSetupWithRetry:](830): CoreData: Ubiquity: <PFUbiquitySetupAssistant: 0x1257a62f0>: Retrying after delay: 1Error Domain=NSCocoaErrorDomain Code=134080 An error occurred while opening the persistent store. UserInfo={Reason=Didn't get a container URL back from URLForUbiquityContainerIdentifier:, giving up now. Please ensure the application is signed with the proper entitlements to read from the container., NSPersistentStoreUbiquitousContainerIdentifierKey=null}I checked the entitlements and they look okay... They appear correctly setup by Xcode.I have:com.apple.developer.icloud-c
This appears to be a new issue/bug introduced in ITC in the last 10 days. We submitted a beta app 10 days ago and all was fine, then today we get the error.ERROR ITMS-90682: “Invalid Bundle. The asset catalog at “Payload/MYAPP.app/Watch/MYAPPWatchApp2.app/Assets.car’ can’t contain 16-bit or P3 assets if the app supports iOS 8 or earlier.The assets that the error is complaining about are in our watchOS app. These assets have been shipping in our app since watchOS 1 without issue. Since they're in watchOS, it doesn't make any sense that restricting to iOS 9 or later would help.BTW, my colleague found this tool for inspecting .car archives.https://github.com/steventroughtonsmith/cartoolTime to submit a bug. Steve
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
I tried to submit my archive and the error message I received was ERROR ITMS-90639: Invalid Binary. The value of LSApplicationLaunchProhibited in Info.plist can't change after your app has been released..Can anyone from Apple comment? I want to convert my app to an iMessage app. I don't want to have to bundle all my media assets twice in an iOS app and an iMessage extension.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I submitted a tvOS build to iTunes Connect today and processing failed a few minutes later with several ITMS-90522 errors for various layered images.ERROR ITMS-90522: Invalid Image Asset. The image stack 'image-name' in 'Payload/MyApp.app/Assets.car' has an invalid layer.All of the images called out by these errors display correctly in Xcode and in app. None of the background images have an alpha channel. Everything looks fine, but iTunes Connect rejects the app. Worst of all, these images haven't changed in many months and I've been submitting builds successfully to iTunes Connect for TestFlight several times per month without these errors. I did see these errors a few weeks ago, but I simply resubmitted the exact same binary a few minutes later and it processed successfully. I have tried resubmitting this build three times and haven't gotten past this error.This seems to me like a bug in iTunes Connect, but I thought I'd post here to see if anyone had encountered this or had any thoughts.
Submitting my app for iOS 10 I get the following error:ERROR ITMS-90362: Invalid Info.plist value. The value for the key 'PHSupportedMediaTypes' in bundle {info}.appex is invalid. The value 'LivePhoto' is not supported.What is the correct value?
could you detail how did you achieve that?I'm still trying to build my app with iMessage extension support, and I always get this errorERROR ITMS-90682: Invalid Bundle. The asset catalog at 'Payload/cutecatsmatch4.app/PlugIns/sticker.appex/Assets.car' can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
plus itunes connect wants me to add a plist key:ERROR ITMS-90513: Missing Info.plist Key. Your app's Info.plist in 'Payload/AccuWeatherTV.app' must contain the 'TVTopShelfImage.TVTopShelfPrimaryImageWide' key.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
How to resolve ERROR ITMS-90682: Invalid Bundle - The asset catalog at 'Payload/XXXXX/Assets.car' can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier.With Xcode 8 GM, this error will occur if you include 16-bit or P3 assets in an app submission targeting iOS releases earlier then iOS 9.3. If your app requires wide color functionality you must change your Deployment Target to iOS 9.3 or later. If your app does not require wide color functionality and you wish to deploy it to older iOS versions then you should replace all 16-bit or P3 assets with 8-bit sRGB assets.You can find 16-bit or P3 assets by running “assetutil” on the asset catalog named in the error message from iTunes Connect. The following steps outline the process:1. Create an Inspectable .ipa file. In the Xcode Organizer (Xcode->Window->Organizer), select an archive to inspect, click “Export..., and choose Export for Enterprise or Ad-Hoc Deployment. This will create a local copy of the .ipa file for your app.2. Loc
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
I have just upgraded to the GA version of macOS Sierra and am no longer able to submit apps to iTunes Connect with XCode 7.3. Any idea if there is a fix for this ?
Hello,I followed all the steps and the Assets.json file doesn't contain any reference to P3 or ARGB-16 but I still get the ERROR ITMS-90682 error.All entries basically look like this:{ Compression : lzvn, BitsPerSample : 8, LayoutDirection : 0 - Horizontal, AssetType : Image, ColorModel : RGB, Name : w_m_d_Shop_03, PixelWidth : 960, Graphics : GLES2,0, Subtype : 0, PixelHeight : 960, SizeClass Horizontal : universal, EdgeInsets : top:0 left:0 bottom:0 right:0, Scale : 3, Memory : 512MB, Opaque : false, DisplayGamut : sRGB, Idiom : universal, Encoding : ARGB, Image Type : kCoreThemeOnePartScale, SizeClass Vertical : universal }Any more ideas what I should look for?
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Hi All,I have been trying to submit my sticker pack since Apple released the GM version of xcode 8, but everytime I try to upload to app store from the archive, I get this error,ERROR ITMS-90039: Type Mismatch. The value for the Info.plist key LSApplicationLaunchProhibited is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009248-SW1ERROR ITMS-90039: Type Mismatch. The value for the Info.plist key LSApplicationLaunchProhibited is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009248-SW1Can anybody possibly explain this? It is driving me round the bend, I have spent hours trying to get over this. I have hunted everyw
Hello, I have tested iOS10 beta and GM Seed, and found a problem that In-house app cannot be installed on iOS10 device if you use itms-service scheme.It happens only when you block app install (hide the App Store icon) on your device by installing profile or set on Settings > General > Restrictions > Installing Apps.Does anyone have the same problem? Is the regulation changed or is there any way to fix this? Thank you.
I have embedded a simple Safari extensionfor MacOS in one of my apps esentially building on the XCode template (XCode 8A218a). Everything works nicely, but when trying to submit to the App Store, Application loader reports the following error:ERROR ITMS-90656: Invalid Safari Extension. The value '$allowedDomains' for key 'Allowed Domains' in extension 'MYEXTENSION' is incorrect.where MYEXTENSION is the name of my extension. The relevant segment of my Info.plist is<key>NSExtension</key> <dict> <key>SFSafariWebsiteAccess</key> <dict> <key>Level</key> <string>All</string> </dict>which is essentially the template with the access level set to All. If I use a different string (for example 'Any'), Application loader reports a more sensible message (along the lines that the key 'Any' is not valid, instead of $allowedDomains).Has anybody managed to successfully submit a Safari Extension with full website acces to the app store?CheersMorten
I am developing a stand alone iMessage app (App that works only within iMessage) the structure of it is similar to IceCream Builder sample code. When I try to submit the archive to itunes, I am getting the following error :ERROR ITMS-90632: Invalid iMessage App. Your iMessage app contains a sticker pack and developer code, but iMessage apps can’t contain both. Remove the sticker pack or developer code and resubmit your app.I am not sure how to go about resolving the above issue. I started my project by choosing XCode -> Project -> iMessage ApplicationAny quick help is HIGHLY appreciated since I am close to a launch.Thank You in advance.