Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Can't upload watchOS 2.1 apps to iTunes Connect
I'm trying to upload an iOS 9.2 app with a watchOS 2.1 watch app to iTunes Connect. I get this error:ERROR ITMS-90455: Invalid WatchKit App Bundle. The value '2.1' for the MinimumOsVersion key in Info.plist in bundle [redacted] is not supported.I found some posts on stackoverflow that suggested setting the Base SDK to watchOS 2.0 in the Build Settings, but that option is not available in the drop-down menu for me (I'm using Xcode 7.2), presumably because I only have the watchOS 2.1 SDK installed.So - how can I upload a watchOS 2.1 app? Or, failing that, how can I install the watchOS 2.0 SDK for Xcode 7.2?
0
0
289
Jan ’16
App with embedded framework rejected due to ITMS 90205 (contains invalid nested bundles)
Hi. We're attempting to submit an app to the app store but is being rejected due to ERROR ITMS-90205: Invalid Bundle. The bundle at [...] contains disallowed nested bundles. There is indeed an app and a framework bundled together. I'm not sure if I've set it up incorrectly or if there's some sort of trick you need to do to get it accepted if you have an app that depends on a custom framework.Both app and framework are written purely in Objective-C.The app compiles without warnings and installs and runs correctly on devices in both Debug and Release configurations. The Archive is also created without issue. It's only when we submit to the App Store that it complains about nested bundles. The workspace setup is as follows:ourApp Target -> General -> Embedded Binaries -> ourFramework.framework -> Linked Frameworks and Libraries -> ourFramework.framework, Status = Required -> Build Phases -> Link Binary with Libraries -> ourFramework.framework, Status = Required -> Copy Files -
1
0
5.9k
Jan ’16
UIRequiredDeviceCapabilities, help
i have an app with arm64 everything is ok.But now i put in both system, arm64 and armv7, and when i try to upload an update of the app, this message does not allow me.ERROR ITMS-90502 Invalid Bundle. Apps that only contain the arme64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist.please how can i solve this?http://nfx.comuv.com/aaa.png
0
0
433
Jan ’16
Can no longer upload hosted content
So last night I added screenshots etc to my app as it's nearly ready for review. I did need to make an update to an item that is hosted with apple so I changed the item, and archived the package but in application loader when I try to upload the updated purchase content I get a line of errors:ERROR ITMS-3000: Line 106 column 97: value of attribute display_target is invalid; must be equal to Mac, iOS-3.5-in, iOS-4-in, iOS-4.7-in, iOS-5.5-in, iOS-Apple-Watch or iOS-iPad at XPath /package/software/software_metadata/versions/version/locales/locale/software_screenshots/software_screenshot[17]They all are more or less that with a different line number. I have no idea what to do to fix this.
5
0
1.3k
Feb ’16
ERROR ITMS-90190 First app upload
Im trying to upload my first app through Application Loader and Im getting this error:ERROR ITMS-90190: Invalid Info.plist Key. The key 'UISupportedDevices' in the Info.plist file is not valid.I have no idea what it means and I can't find info or support in Apple documentationMy app has also an Apple Watch application targetAlso I have searched through all my files in the project looking for UISupportedDevices and I don't have any key with this name. Hope anyone could help me!
0
0
908
Feb ’16
Invalid Code Signing
hello, sorry for my not good English , my name is Filippo and i write from Italy.Wen I load my app.ipa to xcode with application loader, this error appears.ERROR ITMS-90179: Invalid Code Signing. The executable 'Payload/Mistermind 2015.app/Mistermind 2015' must be signed with thecertificate that is contained in the provisioning profile.The ipa file is created with Flash and when i export the app , use the certificate for distribution (p12) ed mobilprofile.The file.ipa created with flash is ok.Why xcode ask me to re-sign the already signed files ??Thanks for the answersFilippo
0
0
922
Feb ’16
App transfered but using keychain
Hi,a few weeks ago we transfered our app from one account to another, ignoring that we would loose access to the keychain. Today we were going to upload the first update of the app using the new account and when we submitted the IPA we received a warning saying that we could have a Potential Loss of keychain access (WARNING ITMS-90076).... the problem is that we are currently using the keychain to store if a user did In App Purshases and we are afraid that now, when all our users update they will lose the information about the purshases that they've made, which would be an absolute disaster.After reading some technical documents from Apple it seems pretty obvious that it will be like this:https://developer.apple.com/library/ios/qa/qa1726/_index.htmlhttps://developer.apple.com/library/ios/technotes/tn2311/_index.html#//apple_ref/doc/uid/DTS40014135-CH1-A_ONE_TIME_LOSS_IN_KEYCHAIN_DATA_WILL_OCCUR_IF_YOU_SWITCH_YOUR_APP_ID_PREFIXI would like to know if someone else has faced this situation and what did
3
0
6.0k
Feb ’16
Using Web https to install app, the app is in waiting... state on the device
Hi,I started to put in place enterprise deployment using manifest.plist and ipa file on a https web server.So, I created my application identifier (explicit), my distribution provisioning profile, build my archive using the enterprise account, export my ipa file and manifest.I put these 2 files on my https web server.When I launch the link to the manifest (using the itms service option), I have the pop up asking me if I want to install the application.I click on install and the app appear on the springboard in grey with waiting.. wrote under it. And it stay in this state all the time.I don't know how to understand what happened.I am able to install manually the application with xcode.The issue is present on the 2 devices I have (an iPhone and an iPad).Thanks for your help if you have an idea.Best regards, Eric.
9
0
1.2k
Feb ’16
Runtime Updating Does Not Complete Install
We manage our enterprise app's runtime updates by means of...[[UIApplication sharedApplication] openURL:[NSURL URLWithString:@itms-services://?action=download-manifest&url=https://xxx.plist]];This has always worked well. When called, an alert is presented asking for permission to install, the app closes, and installs. Suddenly, this stoppped working for all our apps. Running on iOS 8 and 9 (not sure how that is possible). Now the user is prompted for the install, but the app never closes and never completes the install.Only if the app is manually closed (Home button) will the install complete, and even then the app's icon remains on Loading for about a minute (with a partial radar icon) and the install eventually completes. If the user never closes the app the install never completes. Is anyone else experiencing this sudden change?
0
0
366
Feb ’16
Two errors -- binary not optimized for iphone 5 (error 90096) and invalid code signing (error 90163) when submitting to iTunes
I have two issues when I upload to iTunes and I’m not sure if they are related to each other:ERROR ITMS- 90096: “Your binary is not optimized for iPhone 5 ……” This is weird because I have the correct splash screen included which is Default-568h@2x with the file size being 640 x 1136. Not sure why I’m getting this error. I've submitted several apps with this splash screen size and having had a problem in the past.ERROR ITMS- 90096: “Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning file. The bundle contains a key that is not included in the provi…… “beta-reports-active”. I know that this issue is being caused by the beta-reports-active tag. I’ve researched this issue but have not found anything that definitively solves this problem. For this building I’m using a production certificate and provisioning profile. I am attempting to upload the app for TestFlight App so I need to solve this problem.My devel
6
0
705
Feb ’16
Reply to Two errors -- binary not optimized for iphone 5 (error 90096) and invalid code signing (error 90163) when submitting to iTunes
The problem for the ERROR ITMS- 90163: “Invalid Code Signing Entitlements error was that a development AND production provisioning profile was using the same App ID. Once I created and paired a separate app ID for the development and production provisioning profile the problem was solved. PROBLEM SOLVED.
Feb ’16