运行Beacon Finder项目时遇“Unfortunately, Beacon Project has stopped”错误求助

First off, let’s nix the assumption this is an Android Studio bug right away — 9 times out of 10, these runtime crashes tie directly to code or configuration issues specific to your beacon implementation, not the IDE itself. Let’s walk through actionable steps to diagnose and fix this:

1. Prioritize Your Logcat Details #

You mentioned you have Logcat info, but didn’t share it — this is the single most critical piece of data. Look for lines tagged with FATAL EXCEPTION; they’ll spell out exactly what’s breaking the app (like a NullPointerException, missing permissions, or an unregistered beacon service). For example, a line like this points directly to a permission gap:

FATAL EXCEPTION: main
Process: com.yourpackage.beaconproject, PID: 12345
java.lang.SecurityException: Need BLUETOOTH_SCAN permission

2. Validate Your Manifest Configuration #

Beacon projects rely on specific permissions and component declarations — double-check these key areas:

• Bluetooth & Location Permissions: For Android 12+, you need BLUETOOTH_SCAN, BLUETOOTH_CONNECT, plus ACCESS_FINE_LOCATION (beacons use location to scan). Add these inside the <manifest> tag:

  <uses-permission android:name="android.permission.BLUETOOTH_SCAN" android:usesPermissionFlags="neverForLocation" />
  <uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
  <!-- For pre-Android 12 devices -->
  <uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />
  <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" android:maxSdkVersion="30" />
  

• Beacon Service Registration: If you’re using a library like AltBeacon, register its services inside the <application> tag:

  <service android:name="org.altbeacon.beacon.service.BeaconService" android:permission="android.permission.BLUETOOTH_SCAN" />
  <service android:name="org.altbeacon.beacon.BeaconIntentProcessor" />
  

• SDK Compatibility: Ensure your minSdkVersion is set to at least API 21 (most beacon libraries require this minimum).

3. Check Runtime Permission Handling #

Even with manifest permissions, Android 6+ requires you to request dangerous permissions (like ACCESS_FINE_LOCATION, BLUETOOTH_SCAN) at runtime. Skipping this will cause crashes when the app tries to scan for beacons. Here’s a quick Kotlin snippet to handle this:

private val REQUIRED_PERMISSIONS = arrayOf(
    Manifest.permission.BLUETOOTH_SCAN,
    Manifest.permission.BLUETOOTH_CONNECT,
    Manifest.permission.ACCESS_FINE_LOCATION
)

if (ContextCompat.checkSelfPermission(this, REQUIRED_PERMISSIONS[0]) != PackageManager.PERMISSION_GRANTED) {
    registerForActivityResult(ActivityResultContracts.RequestMultiplePermissions()) { results ->
        // Handle permission grant/deny logic here
    }.launch(REQUIRED_PERMISSIONS)
}

4. Rule Out IDE Cache Glitches #

If you still suspect Android Studio might be the culprit after the above checks, try these quick fixes:

• Clear project cache: Go to File > Invalidate Caches... and select "Invalidate and Restart".
• Clean and rebuild: Build > Clean Project followed by Build > Rebuild Project.
• Delete the .gradle folder in your project directory and re-sync with Gradle.

Sharing your exact Logcat error and full manifest content will let us pinpoint the issue even faster!

内容的提问来源于stack exchange，提问作者Shakib Karami