Following this unity tutorial: https://docs.unity3d.com/Manual/AppThinning.html
We are trying to use on demand resources for an app to fit the 200mb limit for the apple store.
assets are tagged for the asset bundle
asset bundle is built
on demand resources are enabled
xcode on demand resources are enabled
appleconnect lists an asset pack
testflight app works on our test phone (multiple build have been tested on this phone)
ODR does not work on apple’s end for submission review ERROR: On Demand Resource request failed: The requested application data doesn’t exist
Current iOS that we have testing is 12.3. Xcode version 11.4. Unity version 2019.2.17
Could it be possible that the test iphone has the bundle cached and therefore does not encounter this error. Before every test, the previous build is deleted.
From the error it seems that the bundle is not being hosted. The test phone will be updated to 13.4 in the meantime, but it seems an important step is missing.
We have scoured the internet for a few weeks with no results, so if anyone has information, it would highly appreciated.
Hey I'm experiencing something similar with my app. To give some context. I've embedded the Unity Engine (2018.4.9f) within a native iOS app (targeting iOS >11). Seeing as your experiencing this with a unity build I'm now not sure if it's an issue with Unity, Xcode, or Apple's backend (my money is on apple's backend. See: recent ODR issue). My ODR works totally fine when tested locally and through testflight but gets rejected during app review because of a NSBundleOnDemandResourceInvalidTagError, meaning the tags my app is trying to access aren't in the tag manifest. It's been a serious headache because I can't replicate the issue at all. In the past I've eventually gotten builds approved after clearing the derived data and cleaning the build folder and continuing to submit until it works for them. I just submitted a build after completely uninstalling Xcode and reinstalling it to see if that might fix things. I'll keep you posted.
Related
I have just release an app to the App Store.
I have tested the build using TestFlight and everything worked.
After installing it from App Store it crashes upon opening.
Switching back to the same build but installed through TestFlight makes it work once again.
Does anyone know of any difference between a TestFlight version and an App Store version (of the same build), or have experienced anything similar?
The issue appears to be network related (I think, but I have very little information, and can’t setup a test env as it only happened after releasing to the App Store) and the issue is reproducible on multiple devices.
The app is a React Native (Expo build with EAS) and the source in its entirety can be found at https://github.com/pictoroma/app/
Edit: added source url
Resubmitted another build using the same source, and now everything works. Maybe something inside Apple’s pipeline corrupted the binary between TestFlight and App Store 🤷
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I am trying to submit an app update for an iOS app to support devices running iOS 9, and in the process of uploading to the App Store via XCode, I'm getting the following error:
No version found for 'adamId - platform' (936823648-Mac OS X App). If this problem persists for more than 24 hours, please contact your Apple representative.
This is an iOS app, not an OS X App, so I don't know why I am getting this error. I have already submitted several versions of the app to the App Store previously.
Anyone know how to resolve this issue?
I solved the problem by submitting the app using Application Loader instead of uploading via XCode. Seems like it might be an issue with XCode 7?
https://itunesconnect.apple.com/apploader/ApplicationLoader_3.0.dmg
As #scientiffic says in his answer. You should use Application Loader to upload your app. I thought using ANY version of Application Loader would solve this problem but no.
You need Application Loader 3.0 version. It doesn't work if you use Application Loader 3.2.
I realize this is an old question, but I have had this problem for about a year with no resolution from Apple. I had been using an old version of Application Loader as a solution to this problem, like many others, until I ran into a complication (I have one Apple ID that is attached to multiple iTunes Connect accounts and older versions of Application Loader do not support this). Essentially, I had to find a solution that allows me to use newer versions of Application Loader/Xcode to submit binaries or I was dead in the water.
It turns out I had a key in my Info.plist that was Mac OS X specific. LSMinimumSystemVersion or “Minimum system version”. Removing that key from the Info.plist solved the adamid - platform error.
Just for the record - this error message also comes if you are trying to upload an app for a wrong platform - e.g. uploading an iOS app with a bundle id that is registered as a tvOS app on iTunes Connect.
You can use tvOS/iOS with identical app ids (for e.g. universal in-app purchases), but both platforms must be enabled manually on iTunes Connect, or you will get this cryptic error (at least true in XCode 8).
Saw this when the tvOS version did not exist on the App Store.
I fix that by adding a 1.0 version to tvOS APP as the screenshot.
Same problem with Application Loader 3.5.
Downloaded 3.0 as mentioned and it worked.
You might get this error if you haven't set up iTunes Correctly to accept an app upload. I.e. its possible you haven't created an app with the matching bundle id within iTunes Connect.
I am beta testing my app, and a few users are getting the error "Unable to Download Application. "Okasio" could not be downloaded at this time". So far 30 users have downloaded the beta of the app, and only 2 are getting the error, so it seems user- rather than app-specific. Does anyone have a suggestion?
The message is identical to the one from this post, but with current iOS 8 formatting:
TestFlight fails to install app and cannot delete partially installed app
The most likely reason is that their iOS OS version is below the app's minimum OS version.
As strange as it might sound the official Apple TestFlight/iTunes Connect beta system does not test the OS version at all at the moment. We faced this issue while we were working on our integration with the new TestFlight system (Bitrise.io, iOS CI/CD service - CTO here).
For example one of our test apps was built with iOS 8.2 as the minimum OS version. It's even listed on the app's card in TestFlight (Compatibility: Requires iOS 8.2 or later) but you can still click on the install button and it starts to download&install it. Then of course you get the helpful error message with Unable to Download App.
Note: Tested on two different iPads, both with iOS 8.1.3.
Another, less likely issue might be the lack of storage on the device but as far as I remember that presents a different error message.
I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.