React Native apps fail to build since NDK update to r17 (due to removed support for ARMv5/armeabi)

[sunweiyang]

According to release notes for NDK r17, which was released a couple days ago (https://developer.android.com/ndk/downloads/revision_history):

Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error.

It seems like React Native still references armeabi-v7a across its codebase.

In the meantime, I had to use a workaround (explained in original issue at android/ndk#700) to get my React Native projects built for Android. (A true solution would remove all references to armeabi-v7a from the codebase, but this is something quick-and-dirty for the lazy or time-constrained.)

EDIT: For everyone's convenience, the workaround (macOS) is to replace the bare NDK r17 ~/Library/Android/sdk/ndk-bundle/toolchains/mips64el-linux-android-4.9/ and ~/Library/Android/sdk/ndk-bundle/toolchains/mipsel-linux-android-4.9/ directories with those of the old NDK r16.

[react-native-bot]

Thanks for posting this! It looks like your issue may be incomplete. Are all the fields required by the Issue Template filled out?

If you believe your issue contains all the relevant information, let us know in order to have a maintainer remove the ":clipboard:No Template" label.

[sunweiyang]

I believe the issue template isn't quite relevant to this issue, which discusses Android NDK's relationship to the RN codebase as a whole. Maintainers, please let me know if this is not the case, and I'll gladly provide any other information you wish.

[hramos]

I agree, it's OK to ignore the template in this particular case. The bot shouldn't nag again now that the For Discussion label has been applied.

[steverob]

Any updates on this?

[krystiansliwa]

Any workaround for that?

[kelset]

Please don't pollute this issue with "me too/any updates".

Until better solution:

1. Don't update the NDK unless strictly necessary
2. follow the workaround OP linked

[sunweiyang]

For everyone's convenience, the workaround (macOS) is to replace the bare NDK r17 ~/Library/Android/sdk/ndk-bundle/toolchains/mips64el-linux-android-4.9/ and ~/Library/Android/sdk/ndk-bundle/toolchains/mipsel-linux-android-4.9/ directories with those of the old NDK r16.