chore: Bump NDK version

[BenjaminHalko]

A plugin says it requires NDK version 26.1.10909125, so the NDK version has been changed from flutter.ndkVersion to 26.1.10909125

[oSumAtrIX]

I don't know if this is right. From what I saw building still worked

[BenjaminHalko]

Yep, building still works, but you get this error:

[oSumAtrIX]

Yep, building still works, but you get this error:

Which plugin causes this. This wasn't an issue before.

[BenjaminHalko]

It might have happened after upgrading intl to 0.19.0 which is necessary to use flutter_localizations, but it is hard to say for certain. It has been happening for at least a month judging from the build logs, but any further and the logs have been deleted.

[oSumAtrIX]

A git bisect should be helpful finding the commit, or it may be that plugin, even though it's actually a dependency. I don't know if it's correct practice to simply just pin the ndk version. It is set to flutter.ndkVersion by default for a reason

[BenjaminHalko]

The other option is to simply get rid of ndkVersion all together and it will instead use the NDK version provided by the AGP. This gets rid of the error.

[oSumAtrIX]

What's the reason for it being set to flutter.ndkVersion

[BenjaminHalko]

OK, so flutter.ndkVersion is an NDK version that is supposedly the "most compatible" with the flutter framework. I think currently it is 23.something

[BenjaminHalko]

But you are fully allowed to change the NDK version if there is a version mismatch.

[oSumAtrIX]

Why would the intl dependency rely on an NDK not most compatible with Flutter. I think downgrading the library makes more sense

[BenjaminHalko]

Unfortunately, flutter_localizations depends on intl 0.19.0 and flutter_localizations is from the flutter SDK. That said other plugins that have been recently updated/added are skeletons and file_picker. So it might be one of those...

Edit: Error was present before upgrading skeletons

Edit: After looking at the source code of file_picker, it doesn't seem to require a specific NDK version.

[BenjaminHalko]

It could have been a dependency of a package that got upgraded...