Android模拟器无法访问本地Django服务器，应用崩溃原因排查

Hey there! Let's break down why your Android app might be crashing when connecting to your Django server, and walk through fixes based on your code:

1. Missing Network Permissions or Cleartext Restrictions #

Android is pretty strict with network access, and this is one of the most common culprits:

• First, make sure you've added the internet permission to your AndroidManifest.xml:

  <uses-permission android:name="android.permission.INTERNET" />
  

• For Android 9 (API 28) and above, plain HTTP requests are blocked by default. If you're using HTTP (not HTTPS) for your Django server, add this line to your application tag in AndroidManifest.xml to allow cleartext traffic:

  android:usesCleartextTraffic="true"
  

  Without this, the system will block your Volley request entirely, which can lead to crashes or silent failures.

2. NullPointerException on the TextView #

Looking at your code: final TextView t = findViewById(R.id.textView3);
If this TextView doesn't exist in your layout file, or you call findViewById before setContentView(R.layout.your_activity_layout);, t will be null. Then when you try to call t.setText() later, the app will crash with a NullPointerException.

• Fix: Always call findViewById after setting your activity's layout, and double-check that your layout XML has a TextView with the exact id textView3.

3. Django Server Configuration Issues #

Even if your code is right, your Django server might not be set up to accept requests from the emulator:

• By default, python manage.py runserver only binds to 127.0.0.1, which won't be accessible to the emulator even though you're using 10.0.2.2 (the emulator's alias for your host machine's localhost). Start your server like this instead to listen on all network interfaces:

  python manage.py runserver 0.0.0.0:8000
  

• Also, update your Django settings.py to add the emulator's alias to ALLOWED_HOSTS:

  ALLOWED_HOSTS = ['10.0.2.2', 'localhost', '127.0.0.1']
  

  Without this, Django will reject the request with a 400 error, and while this might not crash your app directly, it can trigger unexpected behavior in your error listener if not handled properly.

4. Incorrect Context for Volley #

When initializing the Volley request queue with Volley.newRequestQueue(this);, make sure this refers to a valid Activity context. If you're running this code in a fragment or a non-activity class, use the application context instead:

RequestQueue queue = Volley.newRequestQueue(getApplicationContext());

Using an invalid context can lead to memory leaks or crashes.

5. Forgetting to Add the Request to the Queue #

Wait a second—does your code end with queue.add(stringRequest);? If you initialize the request but never add it to the queue, it won't run, but while this won't cause a crash, it's easy to miss and can make you think something else is wrong. Double-check that line is present!

Open Android Studio's Logcat and filter for AndroidRuntime errors. The crash log will tell you exactly which line of code is causing the problem (like a null pointer or network exception). This is the fastest way to zero in on the issue. Also, test if your Django server is reachable from the emulator by opening the emulator's browser and navigating to http://10.0.2.2:8000—if it loads, the network connection is good, and the problem is in your app code.

内容的提问来源于stack exchange，提问作者franz hernandez