Expo Android Release Guidance

I’m getting ready to publish an Expo React Native app to Google Play and need crystal-clear, step-by-step instructions that take me from an empty repo to a successfully reviewed production release. Nothing is in place yet, so every piece of the workflow must be covered from scratch. My priority areas are:

• Correctly setting the Android package name / applicationId
• Configuring EAS Build for production AABs
• Generating, managing and matching keystores & signing certificates

Beyond those, I want full confidence in the entire release pipeline. The guidance you deliver should walk me through each of the following checkpoints and leave me with repeatable notes I can follow for future apps:

1. Initial Expo / React Native project setup and configuration
2. EAS-managed credentials and the difference between the Google Play App Signing Key and Upload Key
3. Producing a signed AAB, understanding SHA-1 / SHA-256 fingerprints, and resolving “App Bundle is signed with the wrong key” errors
4. Google Play Console tasks: App Integrity, closed testing track, tester setup, declarations, store listing assets (screenshots, feature graphic, privacy policy, etc.)
5. Submitting the build, tracking review, and best practices to iterate on updates

Deliverables
• A clearly documented, ordered checklist (markdown or Google Doc) that I can reuse
• Any sample command snippets, JSON or YAML files (app.json, eas.json) referenced in the steps
• A brief Q&A session after I complete the first run-through to verify everything works as intended

If screensharing is needed for clarification, I’m open to it, but the core value I’m after is a written playbook I can rely on independently going forward.