关于React-Native 0.64.3无需升级至0.66版本即可适配Android 12的可行性问询

Great question! Let's break this down clearly: You don't have to upgrade to React Native 0.66 to target Android 12, but there are important tradeoffs to consider.

The React Native 0.66 release note emphasizes it's the first version with official out-of-the-box support for Android 12—meaning the core team tested and updated the framework to handle Android 12's new APIs and behavior changes. However, older versions like 0.64.3 can still be adapted to target Android 12 with manual tweaks and patches. Here's how to approach it:

Steps to adapt RN 0.64.3 for Android 12 #

1. Update Android SDK configuration #

• Open android/build.gradle and adjust these values to target Android 12 (SDK 31):

  compileSdkVersion = 31
  targetSdkVersion = 31
  buildToolsVersion = "31.0.0"
  

• Ensure you've installed SDK 31 via your Android SDK manager.

2. Comply with Android 12's new rules #

• Add the mandatory POST_NOTIFICATIONS permission to AndroidManifest.xml (required for apps targeting SDK 31 to show notifications):

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

• Fix implicit Intent restrictions: Android 12 blocks most unspecified implicit Intents. Either specify the target app's package name, or add the QUERY_ALL_PACKAGES permission (or more granular app query permissions if possible).
• Update PendingIntent flags: Android 12 requires using FLAG_IMMUTABLE or FLAG_MUTABLE when creating PendingIntent instances. You'll need to patch any RN core or third-party code that creates PendingIntent without these flags.

3. Patch React Native core compatibility gaps #

RN 0.64.3's core code wasn't built for Android 12, so you'll need to resolve API conflicts:

• For example, Android 12 changes activity launch rules; you may need to update MainActivity.java or MainApplication.java to comply.
• Use tools like patch-package to apply custom fixes to RN core modules without forking the entire framework.

4. Update third-party native libraries #

Many popular RN libraries (camera, image picker, location tools, etc.) may not support SDK 31 on versions compatible with RN 0.64.3:

• Check if the library has an updated version that supports Android 12 and works with RN 0.64.3.
• If not, use patch-package to modify the library's native code to meet Android 12 requirements.

Important caveats #

Manual adaptation works, but it comes with tradeoffs:

• You'll miss official bug fixes and security patches for Android 12 that the RN team added in 0.66 and later versions.
• Edge cases and unexpected crashes may arise, since RN 0.64.3 wasn't tested against Android 12 by the core team.
• Maintenance overhead will be higher, as you'll need to track Android 12-specific patches alongside regular updates.

When upgrading to RN 0.66 makes sense #

If you want a smoother, more maintainable experience, upgrading to RN 0.66 is the better choice:

• It includes all Android 12 compatibility fixes out of the box, so you don't have to manually patch core code.
• Most popular third-party libraries have versions that support RN 0.66 and Android 12.
• You'll get access to other improvements (iOS 15 support, performance tweaks) that come with the newer RN version.

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