App Store Connect

What are the most overlooked App Store Connect APIs or capabilities developers should use?

• Automate build uploads, making builds available to testers, and processing feedback via APIs for end-to-end development automation.
• Combine TestFlight feedback APIs with webhooks to automatically generate tickets in the ticketing system.
• Utilize the Power and Performance API to download reports on app performance, including storage and CPU usage.

How should apps without audio signal accessibility for hearing-impaired users?

• Accurately answer accessibility questions based on the app's capabilities.
• If the app has no sound, do not claim it has captions.
• Use the app description and app previews to communicate accessibility features and value propositions.

What are the most common reasons subscription apps get rejected on their first review, and what are pro tips for new developers?

• Common Rejection Reasons:
  • Insufficient preparation and testing on devices.
  • Not addressing crashes or ensuring production-ready systems.
  • Failing to provide necessary login or demo credentials for subscription-based content.
• Pro Tips for Submission:
  • Thoroughly test the app on devices, exercising all functionality.
  • Ensure in-app purchases and subscription systems are production-ready.
  • Use the new enhanced IAP submission experience for clearer dialogue with App Review.
  • Use App Review Notes to guide reviewers, including login credentials for paywalled content.
  • Provide relevant information and notes that address potential reviewer questions.
• Pro Tips for Following Up After Rejection:
  • Take time to write a detailed response in App Store Connect, not just submit an update.
  • Use the response to have a dialogue, explain the app's functionality, and ask clarifying questions about the rejection.

Will App Store Connect analytics show impressions, retention metrics, and how often a user revisits the cancel flow for retention messages?

• Yes, App Store Connect will provide data on retention messaging performance.
• Developers can measure how many users saw the retention messaging page, clicked cancel, and continued to stay subscribed.
• This data allows developers to test different messages and offers to see what resonates most with users.

What are the most common security mistakes developers make when implementing App Store Connect API integrations?

• Key Security Practices:
  • Do not hardcode API keys into the repository or ship them in client applications.
  • Store API keys server-side or in the Keychain — never in client apps or source control.
  • Manage private keys responsibly and revoke them if compromised or when a service is no longer used.
  • Be especially careful when integrating with third parties; only grant necessary permissions and revoke keys when the integration ends.
  • Use the Users and Access API to monitor account access and compare it against internal systems.
• Private keys are for private use only and should not be shared.
• Create keys for specific use cases and revoke them afterward.

In App Store Analytics, is there a way to see how many people updated organically versus in the background (auto-update vs. manual)?

• Yes, this breakdown is available in the App Store Connect analytics reports.
• Developers can download the analytics reports and find a column that specifically breaks down auto-updates versus manual updates.

For large companies with many apps, is there a way to automate uploading only a few apps from CI without a team API key granting access to all apps?

• A general access team API key grants access to all apps on the account.
• Developers can create an API key per user of App Store Connect, which is tied to that user's level of access.
• This individual key will have the same permissions as the user in the App Store Connect UI, allowing for more granular control.

Can universal purchase apps use different names or subtitles per platform?

• The name and subtitle are shared across all platforms for a universal purchase app.
• Description, however, can differ per platform. Use the description to tailor content, such as omitting NFC mentions for a tvOS target while including them for iOS.
• App previews are also a good way to showcase platform-specific functionality.

Does the new retention workflow support localization, and should retention messages be localized to match app localizations?

• Yes, localization is supported for retention messages.
• It is highly recommended to localize retention messages to ensure consistency with the app's localizations and provide a cohesive user experience.

What are the best practices for App Store app descriptions, especially when many popular apps use dense copy?

• Focus on what users might be interested in and what the app offers.
• Tailor the message for the specific audience.
• Utilize features like Custom Product Pages to drive different audiences to different copies.
• Consider using Product Page Optimization to test different description variations.
• Leverage custom images and videos for product page headers and search results to convey information visually.

What are the best practices for using TestFlight for internal team testing, and how about external testing?

• Internal Testing:
  • Use internal TestFlight for initial testing within the team, especially for QA teams distributing builds regularly.
  • Create different internal groups for specific teams (e.g., QA, localization) and distribute tailored builds to them.
  • Be selective about builds provided to leadership or for early feedback.
• External Testing:
  • Submit to the beta app review process to ensure trustworthiness and safety.
  • Developers can have up to 10,000 testers.
  • Share a link to invite testers; they must download the TestFlight app for security and privacy.
  • Find testers through forums relevant to the app's niche, focusing on seeking feedback rather than selling.

What are best practices for App Store Connect API keys in tooling and automation?

• API keys should be kept on the server only; do not embed them in client applications.
• Keys have no expiration date, so manage them carefully.
• For team keys, consider the role and assign lower-level permissions for read-only access if possible.
• Use individual keys for testing and experimentation before moving to a team-wide key for production automation.
• Adhere to the principle of least privilege.

Is there a way to use the same product name on the App Store for a Mac app and iOS/Apple Vision Pro apps combo if they have different bundle IDs?

• No, this has not changed. You cannot use the same product name for apps with different bundle IDs.
• The recommendation is to use universal purchase, which would consolidate these apps under one bundle ID and accomplish the goal.
• This approach offers benefits and aligns with the ecosystem's evolution towards unified development.

What should first-time App Review submissions get right for auth and API keys?

• Thoroughly test the app, including third-party functionality and APIs.
• Ensure the services are ready to receive production traffic and scale.
• If managing user API keys, uphold privacy by managing them in a privacy-friendly way.
• Provide demo account information and credentials in App Review Notes so reviewers can access and test all app functionality.

How can purchase restoration be validated when transitioning a paid app to freemium?

• Use the StoreKit 2 appTransaction API to see the original app version a customer purchased.
• TestFlight detects app version changes but does not test actual purchases — use sandbox accounts in App Store Connect for purchase testing.
• Developers can also create sandbox accounts in App Store Connect for more complex sandbox management and testing scenarios.
• Consider having one account download the App Store version and then upgrade to the freemium version being tested in TestFlight.

How do developers publish their first iOS app?

• Explore the Apple Developer website for tutorials, videos, documentation, and WWDC sessions.
• Consult the App Store Connect Help Guide for step-by-step instructions on navigating the UI.
• Follow the Apple Developer Pathway, a guided process for getting the app on the store.
• Refer to detailed guides for each page and action available in App Store Connect.
• Watch the "Getting Started with TestFlight" tech talk for guidance on building, testing, and submitting.

Once an app is approved, how can I increase its visibility?

• Provide compelling creative assets, including more screenshots and previews.
• Create In-App Events to highlight timely content or activities.
• Utilize Custom Product Pages and tie them to specific keywords for increased relevance.
• Submit the app for a feature nomination to the editorial team for potential placement on the Today tab.
• Share "Shareable Moments" for featured apps or new version releases to promote them.

Do I need a different binary for every platform (watchOS, iOS, etc.) for a universal app?

• It depends on which platforms to distribute to and if the app is eligible for Apple Silicon.
• You will need distinct metadata for each platform.
• Developers can start with an iOS binary and then make it available on macOS or visionOS.
• Developers can create platform-specific binaries (e.g., visionOS, macOS) later to leverage native features, and users will update to those.

For review notes, if an app is localized to multiple languages, should the notes still be in English, or can they be in the developer's native language?

• While English is often preferred, App Review reviewers have a wide range of language skills and can often review apps in the developer's primary language.
• It is not an absolute requirement for review notes to be in English.

What new App Store Connect workflows introduced this year should developers revisit, even if they already have mature automation in place?

• Explore new visualizations and over 100 new metrics in the App Store Connect web UI for subscription and in-app purchase analytics.
• Investigate the submission of Game Center entities (leaderboards, etc.).
• Review updates to In-App Purchase APIs and the introduction of Offer Code APIs for consumables and non-consumables.
• Consider the Build Delivery API for automating build submission and updates.

What are the most common reasons for rejection on the App Store?

• Bugs and Crashes: Insufficient testing on devices (not just simulators).
• Incomplete Information: Missing demo credentials or functionality details in App Review Notes.
• Inadequate Testing: Not thoroughly testing via internal and external TestFlight, and not incorporating feedback.
• Submission Completeness: Submissions that are not detailed or complete.
• Guideline Violations: Not adhering to specific sections of the App Review Guidelines, especially for categories like Kids Apps or apps with crypto content.
• Insufficient Testing: Relying solely on Xcode Simulator and not testing on multiple physical devices or with external testers.

Which validations only run after TestFlight or App Store Connect upload?

• Validations occur throughout the pipeline, and efforts are ongoing to provide feedback as early as possible.
• Xcode offers validation before delivery, and warnings are provided to guide developers.
• Uploading frequently (continuous delivery) is a good way to identify issues early.
• The goal is to move validation checks earlier in the development workflow.

Is there a way to organize TestFlight builds into streams or groups, for example, keeping a major new feature separate from regular builds?

• Yes, developers can organize testers and builds into groups for both internal and external TestFlight.
• Create groups based on use cases (e.g., development team, QA team, localization team, power users).
• Developers can create a group for a specific upcoming feature (e.g., version 2.0) and another for bug fixes (e.g., 1.1).
• This allows for parallel development and testing of different app versions simultaneously.
• Xcode Cloud can automate this process by distributing builds to specific groups based on branches.

Is there a technical or policy reason for the few-day delay on price changes for in-app purchases or subscriptions, including when lowering the price?

• The delay is to ensure that price changes go live everywhere at the same time, accounting for global time zones and propagation across systems.

How should country-specific app listings be merged when features differ?

• Choose one app listing to be the "flagship" and update the other listings to direct users to download the new primary app.
• Notify users about the change and provide a transition period.
• Consider a final release that informs users the app is going away and directs them to the new app.
• Keep the old code for a period to potentially address security updates or bug fixes for users who haven't migrated.
• Use analytics to track user migration between app versions.

What features are provided by the new App Store dashboard with analytics, and how can developers maximize value?

• The biggest update to App Analytics in over 10 years, adding over 100 new metrics, primarily for in-app purchases and subscriptions.
• Data can be tied back to subscriptions, showing the full customer journey from download to renewal.
• Visualizations help identify conversion rates, retention, and "soft spots" in the business.
• New benchmarks allow developers to compare their performance against industry standards.
• Utilize the new guide and videos for detailed information and resources.

Any tips for creating a successful featuring nomination submission?

• The app should be interesting, potentially novel, or do something new.
• Apps with great art and compelling visuals have a better chance of standing out.
• New assets for product pages can also be used in featuring placements.
• Consider the story behind the app and its history.
• Feature nominations are not just for initial launches; updates and roadmaps can also be nominated.
• Developers can try multiple times if the initial nomination is not successful.

What is the least-privileged App Store Connect API role for third-party tools?

• The "Sales" role generally has the lowest level of functions and is recommended for read-only access.
• The "Developer" role allows uploading builds and using internal TestFlight.
• The "Marketing" role allows changes to metadata, product pages, and in-app events, but not app releases.
• These lower-permission roles are the most recommended for API keys used by third-party tools.

Any advice on fetching live or last 24 hours of App Store Connect data via the API, given the UI shows this but the API only updates daily or provides aggregates?

• Currently, the UI is the place to view the last 24 hours of sales data.
• The API updates on a daily basis.
• While the data is the same, the cadence of acquisition differs between the UI and the API for sales and trends data.

How can organic search custom product page impact be measured without keyword-level data?

• In App Analytics, developers can see how well a custom product page is performing overall.
• Filter by "Source Type" and select "App Store Search" to see performance from organic search.
• When developers are not running Apple Ads, this will represent the organic search traffic.
• If running ads, consider creating separate custom product pages for ads and organic search to differentiate the traffic.

Is there a way to see the rollout progress of the current release while a new release is being prepared and submitted to review?

• Yes, in App Store Connect, navigate to the version page and click into "Phased Release Rollout" to see the current day and progress.
• Developers can have up to two versions in App Store Connect per platform: the one ready for distribution and the one being prepared.

What options are open to developers building geospatial augmented reality games in terms of passing app review, especially if a full working demo is difficult to create?

• If the review requires being in a specific location, include a recording of the app in action with the submission.
• Ensure the app provides functionality for users outside the specific geographic location (e.g., outside the UK).
• Utilize TestFlight for internal and external testing to get feedback and ensure the geo-experiences are acceptable to App Review.