zulip-flutter icon indicating copy to clipboard operation
zulip-flutter copied to clipboard

build: Android NDK version mismatch

Open carun opened this issue 11 months ago • 11 comments

Your project is configured with Android NDK 26.1.10909125, but the following plugin(s) depend on a different Android NDK version:
- integration_test requires Android NDK 26.3.11579264
Fix this issue by using the highest Android NDK version (they are backward compatible).
Add the following to C:\src\zulip-flutter\android\app\build.gradle:

    android {
        ndkVersion = "26.3.11579264"
        ...
    }

carun avatar Dec 27 '24 21:12 carun

Thanks for the report; helpful to have an issue tracking this. We're discussing it in the Zulip development community, here.

chrisbobbe avatar Dec 27 '24 21:12 chrisbobbe

To make it explicit on this thread: that message is only a warning. So even before we fix it, it shouldn't get in the way of building and running the app.

gnprice avatar Dec 27 '24 21:12 gnprice

@chrisbobbe thanks. I'm trying to login using my Gmail, however it shows an error. Not sure who to reach out to.

Your account [email protected] has been deactivated. Please contact your organization administrator to reactivate it.

carun avatar Dec 27 '24 21:12 carun

Do you mean you're trying to log into chat.zulip.org? Or is it a different Zulip organization?

chrisbobbe avatar Dec 27 '24 21:12 chrisbobbe

I'm trying to log into chat.zulip.org.

carun avatar Dec 27 '24 22:12 carun

For contacting the administrators of chat.zulip.org, you can use [email protected]; I think we may not have a more specific address to use.

Note that replies this week and next may be slow due to holidays.

gnprice avatar Dec 28 '24 00:12 gnprice

Hello there! This same issue occured in my some projects after i updated my android studio and AGP etc and hence i solved this by just manually changing the NDK version to newer one. I think that will fix this issue.

maiHydrogen avatar Feb 05 '25 22:02 maiHydrogen

I'm not sure if this is the same issue (let me know if I should log a separate bug), but with 3.29.0 (stable) I'm getting this warning. Either the mismatch detection is new, or Flutter actually downgraded to an unsupported version of the NDK. Is that expected?

I know it's just a warning and there's a workaround, but it doesn't seem right that a new project should use a deprecated NDK.

Your project is configured with Android NDK 26.3.11579264, but the following plugin(s) depend on a different Android NDK version:
- audioplayers_android requires Android NDK 27.0.12077973
- path_provider_android requires Android NDK 27.0.12077973
- sensors_plus requires Android NDK 27.0.12077973

This can be reproduced easily with

flutter create --platforms=android ndk_sample
cd ndk_sample
flutter pub add audioplayers
flutter run

drrnbrns avatar Feb 22 '25 20:02 drrnbrns

it doesn't seem right that a new project should use a deprecated NDK.

Yeah, I agree. Sounds like a good issue to report in the Flutter issue tracker 🙂, flutter/flutter.

This thread is in the tracker of a particular Flutter app, namely Zulip.

gnprice avatar Feb 23 '25 01:02 gnprice

is there something new? I also just upgraded Android Studio and AGP and get this error. I changed the following:

//ndkVersion flutter.ndkVersion ndkVersion = "27.0.12077973"

but it feels like a workaround since it referencing something from Flutter here that should match?

Sesa1988 avatar May 07 '25 18:05 Sesa1988

@Sesa1988 It looks like you subsequently found the issue thread for this in Flutter's own tracker 🙂: https://github.com/flutter/flutter/issues/139427

This thread is in the issue tracker for Zulip, a particular Flutter app.

(For cross-reference: it looks like after the earlier comments above, @drrnbrns filed https://github.com/flutter/flutter/issues/163945 in the upstream tracker, and that was consolidated into the other issue.)

For anyone else who comes across this thread: that message is a warning, not an error. As far as we've seen in Zulip to date, it doesn't get in the way of the app building and running just fine. So although it'd be good to clear up (hence this issue thread and the upstream one), one can also just ignore it until the upstream issue gets fixed.

gnprice avatar May 07 '25 21:05 gnprice