Question 130265 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode 14 Asset validation failed – missing app icon

after long nights of programming, I have finally finished my app and would now like to upload it to the AppStore Connect for testing purposes, but I always get the same 2 error messages because of certain sizes of the app icon are missing (screenshot attached). I have tried pretty much everything from Stackoverflow, but nothing helped or a lot of things are already out of date, because in Xcode 14 you can only specify one size for the app icon (1.024px x 1.024px).

Does anyone here have a solution for this problem?

The "AppIcon" is in the Assets.xcassets folder & I added some attributes in the info.plist file to eliminate some other error messages. (Do I have to add my App as a target in the info.plist file, because I get some errors when I do?)

AppIcon in Assets folder
AppIcon in Assets folder

Info.plist file
Info.plist File

Error messages
Error messages

Sorry I’m new to stackoverflow so I can’t post images directly.

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    After long and hair-raising moments I figured it out now. My Assets.xcassets folder was inside another folder in my project. I dragged the Assets folder to the root were also the info.plist file is and my upload worked.

    I also used this website to create my icons and dragged that Assets.xcassets folder into my project: https://appicon.com


  2. 0

    From Xcode 14 Release notes:

    Apps using a single-size app icon can fail App Store validation if the deployment target is older than iOS 12 or watchOS 4. (98471456)

    So, I would guess this is a bug caused by old deployment target.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search