# Android / Play Console Release Guide

## Package identity

This mobile project retains the Android application ID:

```text
com.colorjetbd.managementsuite
```

Before a production update, confirm this is exactly the existing Play Console package. Do not change it after the first published release.

## Environment

Create `mobile-engineer/.env` locally:

```env
EXPO_PUBLIC_API_BASE_URL=https://erp.yourdomain.com/api
```

Never put backend passwords, JWT secrets, database URLs or signing password in this file.

## Build

```bash
cd mobile-engineer
npm install
npx expo-doctor
npx eas login
npx eas build --platform android --profile production
```

## Signing key

Use the exact Android upload signing key already registered for this Play Console app. A new unrelated key will cause update rejection. The SHA-256 value is public certificate identity only; never upload or send the `.jks`/`.keystore`, alias password or private signing password.

## Release checks

1. Sign in using an actual engineer account.
2. Verify only assigned tickets are visible.
3. Start ticket with location permission.
4. Capture photo, complete ticket and check Web ERP result.
5. Turn Internet off, create an offline queued action, turn Internet on and verify sync.
6. Verify no demo username/password is visible in app or release notes.
7. Upload the generated AAB to Play Console internal testing before production.