docs: add mobile bundle ID whitelisting requirement for production

[devin-ai-integration]

Description

This PR addresses WAL-6167: Improve visibility on mobile SDK setup for production by adding critical mobile bundle ID whitelisting information to production setup sections across mobile SDK documentation.

Problem: Customers like Starshot were experiencing silent request failures when moving from staging to production because their mobile app identifiers (bundle IDs/package names) weren't whitelisted on production API keys. The existing documentation step was easy to miss, and staging doesn't enforce this requirement the same way production does.

Solution: Enhanced production setup documentation in three locations to prominently highlight the mobile bundle ID whitelisting requirement:

1. crossbit-main: Added step 3 and warning box to React Native quickstart production section
2. wallets-expo-quickstart: Enhanced "Using in production" section with detailed mobile app identifier requirements
3. crossmint-sdk: Added new "Production Setup" section to React Native SDK README

All changes include:

• Explicit warning about staging vs production enforcement differences
• Clear examples of bundle ID formats (iOS: com.company.appname, Android: com.company.appname)
• References to existing detailed documentation at /introduction/platform/api-keys/client-side#mobile-app-identifiers

Test plan

Documentation rendering:

• Verify the <Warning> component renders correctly in the React Native quickstart (crossbit-main)
• Test that all documentation links work and point to the correct sections
• Confirm consistent messaging across all three repositories

Technical accuracy verification:

• Validate mobile bundle ID format examples are correct
• Confirm the staging vs production enforcement differences described are accurate
• Verify the referenced documentation section exists and contains the detailed setup instructions

Manual testing: Documentation changes only - no code functionality to test.

Package updates

No package updates required - documentation changes only.

---

Link to Devin run: https://app.devin.ai/sessions/6807ee0813584eddb002dd391c7bb1d4
Requested by: Agus ([email protected])

Human Review Checklist:

• Verify technical accuracy of bundle ID examples and staging/production differences
• Test all documentation links work correctly
• Confirm Warning component renders properly in MDX
• Check messaging consistency across the three repositories
• Validate that the changes address the root cause described in WAL-6167

[devin-ai-integration]

Original prompt from Agus

SYSTEM:
=== BEGIN THREAD HISTORY (in #help-wallets) ===
Pylon (U07V6DK170F): we should consider improving visibility around mobile client SDK setup: Starshot ran into confusion here:

* they were using the SDK in staging, everything worked fine
* once they moved to production, requests started failing silently, no clear auth errors
* root cause: their mobile bundle ID wasn't whitelisted on the production API key
* we do document this step here: <https://docs.crossmint.com/introduction/platform/api-keys/client-side#mobile-app-identifiers|https://docs.crossmint.com/introduction/platform/api-keys/client-side#mobile-app-identifiers>
* but it's easy to miss, especially since staging doesn't enforce it the same way

we could add this info in our quickstarts repos: <https://github.com/Crossmint/wallets-expo-quickstart/tree/main?tab=readme-ov-file#using-in-production|https://github.com/Crossmint/wallets-expo-quickstart/tree/main?tab=readme-ov-file#using-in-production>


Lars  |  Starshot #2236
<https://app.usepylon.com/issues?conversationID=bff80a54-9ab4-4df7-9da6-3f55a8ad5559|View in Pylon>  |  <https://crossmint.slack.com/archives/C0943MZM3T2/p1754503695393789?thread_ts=1754503695.393789&amp;cid=C0943MZM3T2|View in Slack>  |  :lock: Internal thread


Linear Asks (U064YQRSWJC): EmojiReactor created a new General Ask WAL-6167 Improve visibility on mobile SDK setup for production on behalf of Robin Curbelo

<@U08SHNFTXGE> created a new General Ask on behalf of *Robin Curbelo*

<https://linear.app/crossmint/issue/WAL-6167/improve-visibility-on-mobile-sdk-setup-for-production|WAL-6167 Improve visibility on mobile SDK setup for production>
we should consider improving visibility around mobile client SDK setup: Starshot ran into confusion here:
•  they were using the SDK in staging, everything worked fine
•  once they moved to production, requests started failing silently, no clear auth errors
•  root cause: their mobile bundle ID wasn't whitelisted on the production API key
•  ... (1017 chars truncated...)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 03dfa22

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
smart-wallet-auth-demo	Ignored			Aug 20, 2025 9:03pm