Publishing to Apple, improve documentation about icons.

Open Beginner friendly
#8,333 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
ios, macos

Research direction

Start with the iOS publishing manual at https://defold.com/manuals/ios/ and compare its icon instructions with the reported Xcode 15 workflow. Document the Supported Destinations requirement and the needed icon sizes, including the two 1024px icons; the documentation should explain how to avoid the Transporter and moderation errors.

Written by the indexing model from the issue text.

Description

documentation ios task

When publishing to Apple, I encountered a number of problems that were not described in the official defold documentation. (https://defold.com/manuals/ios/)
I use:
Defold - 1.6.2
Xcode - 15
MacOS - Catalina.
According to the instructions on the official page, to create icons there is a checkbox for IPhone + iPad, and in the new version of XCode there is an option for iOS only without separation.
In the Xcode project, an IPhone has been added to Supported Destinations, and during assembly, if you assemble it in Single Size mode, Apple will generate errors even at the stage of sending the application via Transporter about missing images (120px and 152px), but if you fill in everything in All Sizes mode, it will be sent successfully, but at the stage of sending for moderation it will report an error of missing 1024px icon.
After analysis, the decision turned out that in Assets.car, in the correct case, there should be 2 icons of 1024px size (for iPhone and iPad)
And therefore, you need to add IPhone + IPad to Supported Destinations (even if the application is not intended for it), then the problem is solved.

Dominant language
C++
Stars
6.3k
Forks
455
Avg merge
1d 14h
Merged PRs (30d)
132

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defold/defold

All issues in defold/defold

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.