ElmonyDocs

Integrations

Expo / EAS

Elmony uses Expo and EAS for native mobile preview, cloud builds, credentials, and store submission. This integration appears in the Publish panel for mobile projects.

Connect Expo

  1. Open a mobile project in Builder and select Publish.
  2. In Expo / EAS, open the Expo access-token page.
  3. Create an Expo access token, paste it into Elmony, and connect the account.
  4. Confirm the Expo owner, then select Configure EAS.

The Expo token is account-level. The configured project ID, owner, and slug are saved for the selected app.

Test before release

  • Use Expo Go and the Device preview QR code for fast development checks.
  • Run Expo preflight and fix blocking diagnostics before starting an EAS build.
  • Create preview builds for testing native behavior that Expo Go cannot reproduce.
  • Create production builds only after identifiers, icons, splash assets, and credentials are final.

Credentials and store records

Android and iOS have separate signing credentials. The Publish panel can prepare or import Android credentials and open the interactive credentials setup when a platform needs manual work. Store submission additionally requires a linked Google Play or App Store Connect app record.

Keep package names and bundle identifiers stable after store records are created. Changing an identifier creates a different native app identity and can break Firebase or store links.

Submit a build

  1. Create and wait for a production EAS build to finish.
  2. Complete the Store submission prerequisites in Publish.
  3. Confirm Store & billing readiness for at least one platform.
  4. Submit the finished Android or iOS production build.
  5. Follow review and rollout status in Play Console or App Store Connect.

Google Play may require the first app upload to be completed manually before automated EAS submissions work. Follow the warning shown in Publish if this applies.

Troubleshooting

  • Refresh build status if an EAS job finished outside the Elmony window.
  • Use the build diagnostics action to copy details, attach them to chat, or ask AI to fix the app.
  • For Google sign-in, sync the Android signing SHA-1 with the connected Firebase project.
  • Reconnect Expo if the saved token was revoked or belongs to the wrong account.

Continue with the complete mobile troubleshooting checklist .