[Enhancement proposal]: Upgrading the Android SDK dependency to version 35

[leaf-node]

Please check the following before submitting a new issue.

• I have searched the existing issues.
• I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

• Android
• iOS
• Windows

Proposal

Could you please upgrade to the latest Android SDK?

Pitch

When compiling Flutter apps for Android, an outdated Android SDK must be downloaded to compile apps with this module. As a result, some app builds require multiple versions of the Android SDK. For some context, see: flutter/flutter#63533 (comment).

[gwhizofss]

Does this mean that if we are on Android SDK 35 within our Flutter project, we cannot use this library yet? I don't see how using an older SDK would work, we are on 35 for many reasons. @TimHoogstrate

[leaf-node]

Flutter libraries that target an older version of the Android SDK are generally compatible with apps that target SDK 35. The main problem is that when using one of those libraries, the user has to download both SDK 35 and whatever that library is using. I haven't seen any breakage from that behavior, but it is somewhat of an inconvenience, impacting disk space and possibly the duration of CD jobs.

When upgrading a library's target SDK, there is a possibility of incompatibility, but I suspect that most of the time nothing breaks, or is hopefully caught by a compiler when building a Flutter app with a specific library.

[TimHoogstrate]

It has been released in permission_handler v 12.0.0.