Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/desarrolladorandres2026-gif/Native-tailwind/llms.txt

Use this file to discover all available pages before exploring further.

The Debuta mobile app is a React Native application built with Expo. Production builds are compiled in the cloud through Expo Application Services (EAS) — you do not need Xcode or Android Studio on your local machine to produce a store-ready binary. This guide walks through the complete process from configuring your environment to submitting to both stores.
WebRTC video calls use native device APIs that are not available in Expo Go. All testing that involves video or voice calls must be done on a development build (eas build --profile development), not in the Expo Go client.
1
Install EAS CLI and Log In
2
Install the EAS command-line tool globally and authenticate with your Expo account:
3
npm install -g eas-cli
eas login
4
Verify the CLI is connected to the correct Expo account:
5
eas whoami
6
The project’s EAS configuration links to project ID 1f521860-0fcd-4604-92da-3bf95ef017bc. Make sure the logged-in account has access to this project in the Expo dashboard.
7
Review eas.json
8
The eas.json at the root of the mobile/debuta directory defines three build profiles:
9
{
  "cli": {
    "version": ">= 18.12.1",
    "appVersionSource": "remote"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal",
      "android": {
        "buildType": "apk"
      }
    },
    "production": {
      "autoIncrement": true
    }
  },
  "submit": {
    "production": {}
  }
}
10
ProfilePurposedevelopmentDevelopment client build distributed internally — required for WebRTC and other native modulespreviewInternal APK build for Android testing without Play Store submissionproductionStore-ready build with automatic version code/number increment
11
appVersionSource: "remote" means EAS manages the version number remotely; autoIncrement: true in the production profile bumps the build number automatically on each production build.
12
Set the API URL
13
Before triggering a production build, create or update the .env file in mobile/debuta/ so the app points to your live backend:
14
EXPO_PUBLIC_API_URL=https://your-backend.com
15
This variable is read at build time and embedded in the JavaScript bundle. Rebuild the app any time the backend URL changes — changing the variable after a build has no effect on already-compiled binaries.
16
Do not set EXPO_PUBLIC_API_URL to http://localhost:3000 for production builds. The variable is public (prefixed with EXPO_PUBLIC_) and will be visible in the compiled bundle.
17
Build for Android
18
cd mobile/debuta
eas build --platform android --profile production
19
EAS will upload your project source, compile the Android AAB in the cloud, and provide a download link when the build finishes. The bundle format is an Android App Bundle (.aab) by default, which is required for Play Store submission.
20
To build a standalone APK for direct installation (for testing, not store submission), use the preview profile instead:
21
eas build --platform android --profile preview
22
Build for iOS
23
eas build --platform ios --profile production
24
An active Apple Developer account (paid membership) is required. EAS will prompt you to log in to Apple and will automatically create or reuse the required provisioning profile and distribution certificate.
25
The output is an .ipa file ready for App Store submission.
26
To build both platforms in parallel in a single command: eas build --platform all --profile production
27
Submit to the Stores
28
Google Play Store:
29
eas submit --platform android
30
You will need a Google Play service account JSON key. Follow the EAS Submit documentation to generate one from the Google Play Console and configure it in your EAS project settings.
31
Apple App Store:
32
eas submit --platform ios
33
EAS Submit uses App Store Connect API keys for authentication. Generate a key in App Store Connect → Users and Access → Keys, then provide the key ID, issuer ID, and .p8 file when prompted or via EAS secrets.

​
App Configuration Reference

The app.json in mobile/debuta/ defines the core application metadata:
PropertyValue
expo.namedebuta
expo.slugdebuta
expo.schemedebuta
expo.android.packagecom.andressofia.debuta
expo.extra.eas.projectId1f521860-0fcd-4604-92da-3bf95ef017bc
expo.version1.0.0
The iOS build declares NSCameraUsageDescription and NSMicrophoneUsageDescription in infoPlist for camera and microphone access required by video calls. The Android build declares the corresponding CAMERA, RECORD_AUDIO, and MODIFY_AUDIO_SETTINGS permissions in app.json.

Build docs developers (and LLMs) love

Get started for freeTalk to us