Expo构建的React Native应用APK登录报错问题求助

Hey Adam, let's figure out why your app crashes on login after building the APK—since it works perfectly in development and on your device during dev mode, the issue is almost certainly tied to production build differences. Here are the top fixes to test:

1. Fix Environment Variable Configuration #

• When developing, you might have used a .env file for API keys or endpoints, but these don't automatically get embedded into the production APK unless configured properly.
• Make sure you're using expo-constants to read variables, and that you've set up the extra field in app.config.js or passed the correct env file during the build command:

  eas build --platform android --profile production --env-file .env.production
  

• Double-check that your production environment variables point to the correct live API endpoints (not your local dev server).

2. Verify Android Network Permissions #

• Expo handles permissions automatically in dev mode, but production APKs need explicit declarations. Open your app.json and confirm the android.permissions array includes:

  "android": {
    "permissions": ["INTERNET", "ACCESS_NETWORK_STATE"]
  }
  

• The INTERNET permission is mandatory for login requests, and ACCESS_NETWORK_STATE helps your app handle offline scenarios gracefully.

3. Check Your API Base URL #

• It's super common to hardcode a local IP (like http://192.168.x.x:3000) for dev testing and forget to update it for production. If your login request is trying to hit a local server that doesn't exist on the device's network, it'll throw an uncaught error and crash.
• Use environment variables to switch between dev and production URLs, so you don't have to manually update code for builds.

4. Disable or Fix ProGuard/R8 Obfuscation #

• If you're using code obfuscation (enabled by default in EAS production builds), some libraries (like Retrofit, OkHttp, or your own utility classes) might get mangled, causing runtime crashes.
• Test by temporarily disabling obfuscation in your eas.json production profile:

  "production": {
    "android": {
      "enableProguard": false
    }
  }
  

• If that fixes the crash, add custom rules to android/app/proguard-rules.pro to exclude critical classes from being obfuscated.

5. Get Detailed Crash Logs #

• The generic "app has stopped" message isn't enough to pinpoint the issue. Use these methods to get the full error stack:
  • Connect your device to Android Studio and use Logcat to filter your app's package name—look for FATAL EXCEPTION entries when you tap login.
  • Integrate an error reporting tool like Sentry into your Expo app; configure it for production builds, and it'll send detailed crash logs to your dashboard when the app fails.

Start with checking environment variables and the API base URL—those are the most frequent causes of this kind of dev-to-prod crash. Let me know if you need help digging deeper into any of these steps!

内容的提问来源于stack exchange，提问作者Adam Katz