-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing iOS app to App Store fails with Asset Validation Errors #18991
Comments
Does your app have these required assets? A new project from a template isn't guaranteed to contain all the assets required to publish the app to the app store (in particular because those would just be placeholder assets anyway). |
Hi @RobSchoenaker. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
@rolfbjarne thx for the swift response. This is just a new empty 'Tabbed Page App' I made and changed the bundle identifier to an existing app I have (for which publishing fails). The new (empty) app contains place holder images - correct. I would expect these images to be sufficient. The info.plist and Assets.xcassets look normal. Info.plist:
What additional info do you need? |
That's not necessarily the case: Apple changes the publishing requirements every now and then, and we don't always keep track of them and update the templates. Can you try adding the required assets to the project and see if that helps? |
Hi @RobSchoenaker. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Thanks and I see. Have been struggling to get my app to be reviewed and finally managed to find the issue. You are correct in stating that "Apple changes the publishing requirements every now and then, and we don't always keep track of them and update the templates." It would be very useful for developers to know what they need to do to get their app approved. A single Knowledge Base article would suffice. When the requirements changes, the app and some files need to be changed too. The info.plist I sent in my last post 'clearly' states the missing pieces. I do not have access to the correct info.plist at the moment, but I will attach it here and outline the required bits in a day or two. |
Agreed, but the problem is that only Apple knows that. If we try to document it, it will inevitably be out of date, and then we'll have people complaining that our documentation is out of date :/
OK. |
Hi @RobSchoenaker. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
I have really been pulling my hair out over the course of several weeks in order to get the app reviewed. Especially since iOS 17 is released today, I consider myself lucky to be able to publish an iOS17 compatible app. First, the info.plist needs to be completed:
Specifically, I had to add the Next,. I removed all icons from the Assets.xcassets and added a single AppIcon of 1024x1024 pixels. Square, PNG without transparency. The settings for the icon in Xcode 14.3 are:
With these settings, I archived the app setting the 'iOS Build Only Device' to Generic Device (This is the last option in the list and marked by an Xcode icon) After archiving, I was able to send the app through Transporter without any issues. And after Thasporter, I could link the app to a new release and submit it for review. In case anyone has similar issues, I hope this is useful. |
Thanks Rob, this worked for me, you have to archive with Generic Device setting |
This error is preventing me from sending an updated version of my iOS App to Apple for validation. To mitigate the issue, I tried creating a new sample app to test and this gives the same results.
Steps to Reproduce
Asset validation failed (90704)
Missing App Icon. An app icon measuring 1024 by 1024 pixels in PNG format must be included in the Asset Catalog of apps built for iOS, iPadOS, or watchOS. Without this icon, apps cannot be submitted for review. For details, see https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/app-icon/. (ID: 7841a3bc-7991-41bf-a31a-2e1a5ee699ba)
Asset validation failed (90023)
Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface (ID: 737951a9-54fb-46ab-8fef-e24878fa1b35)
Asset validation failed (90023)
Missing required icon file. The bundle does not contain an app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface (ID: e0c1d9a5-9b80-47c5-b031-bb248b127564)
Expected Behavior
The assets should be included in the app so that Transporter can successfully send the App to Apple
Actual Behavior
Cannot pass asset validation after the App is uploaded
Environment
Version information
Build Logs
Example Project (If Possible)
The text was updated successfully, but these errors were encountered: