Skip to content
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

[templates] Add comments to help developers #17591

Closed
6 tasks
rolfbjarne opened this issue Feb 22, 2023 · 1 comment · Fixed by #17830
Closed
6 tasks

[templates] Add comments to help developers #17591

rolfbjarne opened this issue Feb 22, 2023 · 1 comment · Fixed by #17830
Assignees
Labels
documentation The issue or pull request is about documentation enhancement The issue or pull request is an enhancement good first issue This is a good first issue for someone to start working with our code
Milestone

Comments

@rolfbjarne
Copy link
Member

rolfbjarne commented Feb 22, 2023

It can be difficult to get everything correctly aligned for publishing, so we might want to add comments to templates to show developers what they need to do depending on what they want to do.

A list of problems for Mac Catalyst are described here: dotnet/maui#12293

  • App rejected because: The product archive package's signature is invalid. Ensure that it is signed with your "3rd Party Mac Developer Installer" certificate. A commented section in csproj explaining what they need to do might help here.
  • App rejected because: The product archive is invalid. The Info.plist must contain a LSApplicationCategoryType key, whose value is the UTI for a valid category. For more details, see "Submitting your Mac apps to the App Store". A commented section in the Info.plist might be helpful.
  • App rejected because: Invalid bundle. The bundle supports arm64 but not Intel-based Mac computers. Your build must include the x86_64 architecture to support Intel-based Mac computers. A commented section in csproj explaining that if only x64 or arm64+x64 (but not just arm64) is valid for publishing would help.
  • App rejected because: `Invalid Bundle. The key UIDeviceFamily in the app's Info.plist file contains one or more unsupported values '1'. We should probably validate this at build time.
  • App rejected because: App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list [...]. A commented section in the Entitlements.plist might be helpful. Alternatively we could default to include this entitlement by default for release builds (but verify that we don't end up with builds that won't execute locally).
  • "I had to add ITSAppUsesNonExemptEncryption to Info.plist." A commented section in the Info.plist might be helpful.
@rolfbjarne rolfbjarne added enhancement The issue or pull request is an enhancement documentation The issue or pull request is about documentation labels Feb 22, 2023
@rolfbjarne rolfbjarne added this to the .NET 8 milestone Feb 22, 2023
@rolfbjarne rolfbjarne added the good first issue This is a good first issue for someone to start working with our code label Feb 22, 2023
@UrbanSowaLabs
Copy link

UrbanSowaLabs commented Feb 22, 2023

Another comment that would help developers when publishing MAUI Blazor: com.apple.security.network.client in Entitlements.plist

Details are here: dotnet/maui#13094

dustin-wojciechowski added a commit that referenced this issue Mar 24, 2023
…on App Store (#17830)

Added some information to the MacCatalyst templates based on comments from the community
on how to publish MacCatalyst apps on the App Store.

Fixes #17591
@ghost ghost locked as resolved and limited conversation to collaborators May 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation The issue or pull request is about documentation enhancement The issue or pull request is an enhancement good first issue This is a good first issue for someone to start working with our code
Projects
None yet
3 participants