Android应用每次重启触发单应用AOT编译，求助排查方向（使用JNI）

Hey there, let's dig into this frustrating "Optimizing App 1 of 1" issue you're facing every time your device reboots—especially since it only affects your JNI-enabled app. Here's a practical, step-by-step breakdown to help you track down the root cause:

1. Start with System Logs to Get Context #

First, grab detailed logs that will tell you exactly why the AOT compilation is triggering. Run these commands in your terminal:

adb logcat | grep -i dexopt
adb logcat | grep -i aot
adb logcat | grep -i jni

Look for lines mentioning your app's package name—they’ll usually include a specific reason for re-optimization, like failed Native library verification, dex file changes, or signature mismatches. This is the fastest way to narrow down the problem.

2. Audit Your JNI Library Loading Logic #

Since your app uses JNI, this is the most likely culprit. Check these common pitfalls:

• Multiple or incorrect library loads: Are you calling System.loadLibrary() multiple times across your app, or loading the wrong ABI variant? Duplicate loads can confuse the system’s verification process.
• Loading timing: If you’re loading Native libraries in a non-standard place (like a background service that starts on boot), make sure it’s not triggering a state the system interprets as a "modified" app.
• Corrupted or mismatched libraries: Verify all your Native libraries are properly built for target ABIs, and haven’t been corrupted during installation. You can extract the APK and check the lib/ folder to confirm integrity.

3. Check APK/Dex Integrity & Signing #

System-level optimization often triggers when the app’s integrity is in question:

• Dynamic dex modifications: If your app uses plugins, dynamic code loading, or any tool that modifies dex files at runtime, the system might flag it for re-optimization after reboot.
• Signature issues: Ensure your app is signed consistently (no debug/release signature mismatches). Run adb shell pm dump com.your.package.name and look for sections related to dexopt—it will show if the system detected a signature change.
• ExtractNativeLibs setting: If you have android:extractNativeLibs="false" in your AndroidManifest.xml, try switching it to true. Some devices handle embedded Native libraries differently, and this can occasionally trigger post-reboot re-optimization.

4. Rule Out System-Specific Dexopt Policies #

While rare (since only your app is affected), some device manufacturers tweak dexopt behavior. Check Developer Options for any app optimization settings that might target your app. But prioritize app-level issues first—system tweaks are a last resort.

5. Test with a Minimal Reproducible App #

To isolate the problem, build a stripped-down version of your app that only includes:

• A basic Application class loading your JNI library
• A single activity with a simple JNI method call

If this minimal app doesn’t trigger AOT on reboot, gradually add back features from your original app until the issue reappears. This will help you pinpoint exactly which component (third-party library, plugin logic, etc.) is causing the problem.

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