-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NDK] [Build Failed] A problem occurred configuring project ':rive_common'. #320
Comments
Hi @RoyalCoder88, you'll need to update the NDK version in your Android app, see here: https://github.com/rive-app/rive-flutter/blob/master/platform_considerations.md#android Please also make sure that CMake is up to date on your Windows system, see here: https://github.com/rive-app/rive-flutter/blob/master/platform_considerations.md#windows |
Hi @HayesGordon , thanks for the quick reply, but I can't update the NDK because Unity widget depends on this specific NDK version :( thanks! |
Having the same issue.. : ( Still no solution ? |
same issues still |
Having same problem with integration with Unity @RoyalCoder88 did you have temporarily solution? |
<img width="1119" alt="image" src="https://github.com/flutter/flutter/assets/66480156/e2e8eed1-3bef-436c-b21f-3891bdbe05bb"> In most cases, a FFI plugin doesn't need its own specific Android NDK version. Just following the Flutter app project's NDK version is enough. If a Flutter app project depends on multiple FFI plugins that use different Android NDK versions, it can be quite wasteful and use excessive disk space due to multiple NDK installations. Using Flutter app project's NDK version is also less error-prone because upgrading the Flutter SDK would be enough when upgrading FFI plugins(If project's `ndkVersion` is `flutter.ndkVersion`), without messing with Android NDK installations. This problem was discussed in some actual FFI plugin repositories, and they are striving to find their own solutions: - superlistapp/super_native_extensions#143 (comment) - cunarist/rinf#60 (comment) - rive-app/rive-flutter#320 - juicycleff/flutter-unity-view-widget#832
<img width="1119" alt="image" src="https://github.com/flutter/flutter/assets/66480156/e2e8eed1-3bef-436c-b21f-3891bdbe05bb"> In most cases, a FFI plugin doesn't need its own specific Android NDK version. Just following the Flutter app project's NDK version is enough. If a Flutter app project depends on multiple FFI plugins that use different Android NDK versions, it can be quite wasteful and use excessive disk space due to multiple NDK installations. Using Flutter app project's NDK version is also less error-prone because upgrading the Flutter SDK would be enough when upgrading FFI plugins(If project's `ndkVersion` is `flutter.ndkVersion`), without messing with Android NDK installations. This problem was discussed in some actual FFI plugin repositories, and they are striving to find their own solutions: - superlistapp/super_native_extensions#143 (comment) - cunarist/rinf#60 (comment) - rive-app/rive-flutter#320 - juicycleff/flutter-unity-view-widget#832
<img width="1119" alt="image" src="https://github.com/flutter/flutter/assets/66480156/e2e8eed1-3bef-436c-b21f-3891bdbe05bb"> In most cases, a FFI plugin doesn't need its own specific Android NDK version. Just following the Flutter app project's NDK version is enough. If a Flutter app project depends on multiple FFI plugins that use different Android NDK versions, it can be quite wasteful and use excessive disk space due to multiple NDK installations. Using Flutter app project's NDK version is also less error-prone because upgrading the Flutter SDK would be enough when upgrading FFI plugins(If project's `ndkVersion` is `flutter.ndkVersion`), without messing with Android NDK installations. This problem was discussed in some actual FFI plugin repositories, and they are striving to find their own solutions: - superlistapp/super_native_extensions#143 (comment) - cunarist/rinf#60 (comment) - rive-app/rive-flutter#320 - juicycleff/flutter-unity-view-widget#832
any news ? |
nothing works for me still :( |
I manage to find two workarounds:
to
so unityLibrary project doesn't force main project to use NDK r23, and main project can use NDK But come with http version conflict that already fix there but not released in latest nor prerelease (as in 21 Aug 2023). Have to walk around it with your own risk. We simply dependency_overrides http version to 1.11.0, full regression test still in pipeline to verify the impact for all these workarounds. |
In case this is useful to anyone else, an alternative workaround I'm using is to use an older version of |
not working |
I'm using rive 0.11.1, and I'm not able to build on Android, with the error:
flutter --version
flutter doctor -v
The text was updated successfully, but these errors were encountered: