Ubuntu环境下NativeScript调试/部署APK安装失败问题求助

Hey there, let's dig into this problem you're facing—manual APK installs work fine, but tns debug android, tns deploy android, or tns run throw that vague "system issues" error. Since manual installation works, the root cause is almost certainly related to how the NativeScript CLI interacts with your device via ADB, or specific device permissions that the CLI triggers but manual installs don't. Here's a step-by-step breakdown to fix this:

1. Verify ADB Connection & Device Authorization #

First, let's rule out basic ADB connectivity problems:

• Recheck USB Debugging Permissions: On your Android device, if you see a pop-up asking to "Allow USB debugging" for your computer, make sure to check the "Always allow from this computer" box and tap "Allow". Sometimes this permission resets after a device restart or USB port change.
• Restart ADB Service: Run these commands in your terminal to refresh the ADB connection:

  adb kill-server
  adb start-server
  

  Then run adb devices to confirm your device shows up as device (not unauthorized).

2. Check Device Installation Permissions #

Android has several settings that can block CLI-initiated installs even if manual APK installs work:

• Enable "Unknown Sources" or "Install via USB": Go to your device's Settings > Security & Privacy > More Security Settings. Look for options like "Allow app installs from unknown sources" or "USB installation" and ensure they're enabled. For newer Android versions (10+), you may need to specifically allow installs from your connected computer.
• Disable Battery Optimization for ADB: Some aggressive battery saver modes can interfere with ADB operations. Go to Settings > Battery > Battery Optimization, find the "Android System" or "ADB" entry (if visible), and set it to "Not optimized".

3. Clean & Reconfigure Your NativeScript Project #

Corrupted build cache or misconfigured CLI settings can cause this too:

• Clean Project Cache: Run tns clean in your project directory to wipe old build artifacts, then try tns run android again. This clears any stale configuration that might be causing installation conflicts.
• Target Your Device Directly: Instead of letting the CLI auto-detect, explicitly specify your device ID with:

  tns run android --device 988dd2483731455242
  

  This avoids any issues with multiple devices/emulators being connected accidentally.

4. Validate Debug APK Signing & Compatibility #

The CLI installs debug APKs, while manual installs are likely release builds—there could be differences here:

• Check Debug Signing Configuration: Open your project's App_Resources/Android/app.gradle file and verify the debug signing block is intact (NativeScript uses a default debug keystore automatically, so this shouldn't be broken unless you modified it). It should look something like:

  signingConfigs {
      debug {
          storeFile file("debug.keystore")
          storePassword "android"
          keyAlias "androiddebugkey"
          keyPassword "android"
      }
  }
  

• Confirm Android Version Compatibility: Check your App_Resources/Android/src/main/AndroidManifest.xml for the minSdkVersion value. Ensure your device's Android version is equal to or higher than this number—if not, update the value to match your device's OS version.

5. Get Detailed Error Logs from ADB #

The NativeScript CLI error is too vague—let's get the real error from ADB directly:

• Locate your debug APK (usually at platforms/android/app/build/outputs/apk/debug/app-debug.apk in your project folder).
• Run this command to attempt installation via ADB, which will return a specific error code:

  adb install -r platforms/android/app/build/outputs/apk/debug/app-debug.apk
  

  Common errors here include INSTALL_FAILED_INSUFFICIENT_STORAGE (not enough space on device), INSTALL_FAILED_DUPLICATE_PERMISSION (conflicting app permissions), or INSTALL_FAILED_VERIFICATION_FAILURE (device blocking unsigned debug APKs). Use this specific error to narrow down the fix further.

内容的提问来源于stack exchange，提问作者Lester Lynch