Setting Up Android Studio on Linux for React Native (Expo) Development

This comprehensive guide will walk you through installing and configuring Android Studio on Linux specifically for React Native and Expo development. By the end of this guide, you'll have a fully functional development environment optimized for mobile app development.

Prerequisites

Before starting, ensure you have:

Ubuntu/Debian-based Linux distribution
At least 8GB of RAM (16GB recommended)
10GB+ of free disk space
Terminal access with sudo privileges
Basic knowledge of command line operations

Installing Android Studio

Step 1: Update Your System

First, update your package manager and system packages:

bash

1sudo apt update && sudo apt upgrade -y

Step 2: Install Android Studio

We'll use the official PPA repository for the most up-to-date version:

bash

1# Add the repository for Android Studio
2sudo add-apt-repository ppa:maarten-fonville/android-studio -y
3
4# Update package list
5sudo apt update
6
7# Install Android Studio
8sudo apt install android-studio -y

Step 3: Verify Installation

Launch Android Studio to verify the installation:

bash

1android-studio

Initial Android Studio Configuration

Step 1: Complete the Setup Wizard

Welcome Screen: Click "Next" to start the setup wizard
Install Type: Choose "Standard" for typical development setup
UI Theme: Select your preferred theme (Darcula or Light)
SDK Components: The wizard will automatically download:

Android SDK
Android SDK Platform
Android Virtual Device (AVD)
Latest Android SDK build-tools

Step 2: Create a Test Project

To verify everything works correctly:

Create a new Kotlin project
Select "Empty Activity" template
Click "Finish" and wait for Gradle sync
Click the "Run" button (green play icon) to test compilation

React Native/Expo Specific Setup

Critical: Fix the Launch Script

This is essential for React Native/Expo projects to work properly with Android Studio.

Why this matters: The default launch script (studio.sh) doesn't load the Node.js environment properly, causing issues with Gradle configurations that use Node.js commands.

Method 1: Modify Desktop Entry

Edit the desktop application file:

bash

1sudo nano /usr/share/applications/android-studio.desktop

Change the Exec line from:

typescript

1Exec=/opt/android-studio-2025.1.1/android-studio/bin/studio.sh

To:

typescript

1Exec=/opt/android-studio-2025.1.1/android-studio/bin/studio

Method 2: Launch from Terminal

Alternatively, always launch Android Studio from the terminal:

bash

1/opt/android-studio-2025.1.1/android-studio/bin/studio

Understanding the Node.js Integration

React Native projects use Gradle configurations that execute Node.js commands:

plaintext

1def reactNativeAndroidDir = new File(
2  providers.exec {
3    workingDir(rootDir)
4    commandLine("node", "--print", "require.resolve('react-native/package.json')")
5  }.standardOutput.asText.get().trim(),
6  "../android"
7)

Without proper Node.js environment loading, these commands fail, causing build errors.

Environment Variables Configuration

Set Up JAVA_HOME and ANDROID_HOME

Add these environment variables to your ~/.bashrc or ~/.zshrc:

bash

1# Open your shell configuration file
2nano ~/.bashrc
3
4# Add these lines at the end:
5
6# Set JAVA_HOME to the JDK bundled with Android Studio
7export JAVA_HOME="/opt/android-studio-2025.1.1/android-studio/jbr"
8export PATH="$JAVA_HOME/bin:$PATH"
9
10# Android SDK paths
11export ANDROID_HOME="$HOME/Android/Sdk"
12export ANDROID_SDK_ROOT="$ANDROID_HOME"
13export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/tools:$ANDROID_HOME/tools/bin:$PATH"
14
15# React Native development
16export PATH="$PATH:$ANDROID_HOME/emulator"
17export PATH="$PATH:$ANDROID_HOME/platform-tools"

Apply the Changes

bash

1# Reload your shell configuration
2source ~/.bashrc
3
4# Verify the environment variables
5echo $JAVA_HOME
6echo $ANDROID_HOME

Verify SDK Installation

In Android Studio, go to:

File → Settings (or Android Studio → Preferences on some systems)
Appearance & Behavior → System Settings → Android SDK
Verify that the SDK path matches your ANDROID_HOME variable

Debugging and Development Tools

Android Studio's Built-in Tools

Android Studio provides excellent debugging tools for React Native/Expo development:

1. Logcat Tool Window

The Logcat window displays real-time logs from your device/emulator:

How to access:

View → Tool Windows → Logcat
Filter logs by app package name
Use different log levels (Verbose, Debug, Info, Warn, Error)

2. App Inspection Tool

For advanced debugging of background tasks, network requests, and databases:

How to access:

View → Tool Windows → App Inspection
Inspect network traffic
View database contents
Monitor background tasks

3. Device File Explorer

View and modify files on your device/emulator:

How to access:

View → Tool Windows → Device File Explorer
Navigate to /data/data/[your-app-package]/
Useful for debugging storage issues

Additional Development Tools

ADB (Android Debug Bridge):

bash

1   # List connected devices
2   adb devices
3   
4   # Install APK
5   adb install path/to/your/app.apk
6   
7   # View device logs
8   adb logcat
9

Emulator Management:

Tools → AVD Manager
Create multiple device configurations
Test different Android versions

Common Issues and Solutions

Issue 1: "Autolinking is not set up in settings.gradle"

This error occurs when Expo modules aren't properly configured in your Android project.

Solution:

First, try reopening Android Studio and reloading the project
Clean and reinstall dependencies:

bash

1   rm -rf node_modules
2   npm install
3   # or
4   yarn install
5

Verify your android/settings.gradle file:

plaintext

1pluginManagement {
2  def reactNativeGradlePlugin = new File(
3    providers.exec {
4      workingDir(rootDir)
5      commandLine("node", "--print", "require.resolve('@react-native/gradle-plugin/package.json', { paths: [require.resolve('react-native/package.json')] })")
6    }.standardOutput.asText.get().trim()
7  ).getParentFile().absolutePath
8  includeBuild(reactNativeGradlePlugin)
9  
10  def expoPluginsPath = new File(
11    providers.exec {
12      workingDir(rootDir)
13      commandLine("node", "--print", "require.resolve('expo-modules-autolinking/package.json', { paths: [require.resolve('expo/package.json')] })")
14    }.standardOutput.asText.get().trim(),
15    "../android/expo-gradle-plugin"
16  ).absolutePath
17  includeBuild(expoPluginsPath)
18}
19
20plugins {
21  id("com.facebook.react.settings")
22  id("expo-autolinking-settings")
23}
24
25extensions.configure(com.facebook.react.ReactSettingsExtension) { ex ->
26  if (System.getenv('EXPO_USE_COMMUNITY_AUTOLINKING') == '1') {
27    ex.autolinkLibrariesFromCommand()
28  } else {
29    ex.autolinkLibrariesFromCommand(expoAutolinking.rnConfigCommand)
30  }
31}
32expoAutolinking.useExpoModules()
33
34rootProject.name = 'your-app-name'
35
36expoAutolinking.useExpoVersionCatalog()
37
38include ':app'
39includeBuild(expoAutolinking.reactNativeGradlePlugin)

If the issue persists, regenerate native code:

bash

1   npx expo prebuild --clean
2

Issue 2: Gradle Sync Failures

Common causes and solutions:

Node.js not found: Ensure you're using the correct Android Studio launcher (not studio.sh)
JDK version mismatch: Use the bundled JDK in Android Studio
Network issues: Configure proxy settings if behind a corporate firewall

Issue 3: Emulator Performance Issues

Optimization tips:

Enable Hardware Acceleration:

bash

1   # Check if KVM is available
2   grep -E "(vmx|svm)" /proc/cpuinfo
3   
4   # Install KVM if not present
5   sudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils
6

AVD Configuration:

Allocate sufficient RAM (2GB minimum)
Enable "Use Host GPU" in AVD settings
Use x86_64 images for better performance

Best Practices

1. Project Structure

Never directly edit the android/ folder in Expo projects
Use Expo Config Plugins for native modifications
Keep custom native modules in separate directories

2. Autolinking Configuration

Only modify autolinking settings if you have specific requirements:

json

1{
2  "expo": {
3    "name": "your-app-name",
4    "autolinking": {
5      "searchPaths": ["../../packages"],
6      "nativeModulesDir": "../../packages"
7    }
8  }
9}

3. Development Workflow

Use Expo CLI for project creation and management
Test on real devices when possible
Use Android Studio for:

Native code debugging
Performance profiling
Advanced logging
Build analysis

4. Version Management

Keep Android Studio updated
Use specific Android SDK versions for consistency
Document your environment setup in project README

Troubleshooting Checklist

Before asking for help, verify:

[ ] Android Studio launches with the correct script
[ ] Environment variables are set correctly
[ ] Node.js is accessible from Android Studio
[ ] Gradle can execute Node.js commands
[ ] Expo CLI is up to date
[ ] Project dependencies are installed

Conclusion

With Android Studio properly configured on Linux, you now have a powerful development environment for React Native and Expo projects. The key points to remember:

Use the correct launcher to ensure Node.js integration
Set up environment variables properly
Leverage Android Studio's debugging tools for efficient development
Follow Expo best practices for native code modifications

This setup will provide you with professional-grade tools for mobile app development, from initial coding to debugging and performance optimization.

More posts

Building Android Widgets in Expo with Custom Native Modules

Tanstack DB in action

Reasons to Still Use Next.js from a TanStack Start Enjoyer

More posts

Building Android Widgets in Expo with Custom Native Modules

Tanstack DB in action

Reasons to Still Use Next.js from a TanStack Start Enjoyer

Prerequisites

Installing Android Studio

Step 1: Update Your System

Step 2: Install Android Studio

Step 3: Verify Installation

Initial Android Studio Configuration

Step 1: Complete the Setup Wizard

Step 2: Create a Test Project

React Native/Expo Specific Setup

Critical: Fix the Launch Script

Method 1: Modify Desktop Entry

Method 2: Launch from Terminal

Understanding the Node.js Integration

Environment Variables Configuration

Set Up JAVA_HOME and ANDROID_HOME

Apply the Changes

Verify SDK Installation

Debugging and Development Tools

Android Studio's Built-in Tools

1. Logcat Tool Window

2. App Inspection Tool

3. Device File Explorer

Additional Development Tools

Common Issues and Solutions

Issue 1: "Autolinking is not set up in settings.gradle"

Issue 2: Gradle Sync Failures

Issue 3: Emulator Performance Issues

Best Practices

1. Project Structure

2. Autolinking Configuration

3. Development Workflow

4. Version Management

Troubleshooting Checklist

Conclusion