From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Shan Shaji <s.shaji@proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve_flutter_frontend v1] chore: update `compileSdkVersion` to 35 and `targetSdkVersion` to 36
Date: Thu, 3 Jul 2025 16:03:22 +0200 [thread overview]
Message-ID: <20499aba-f114-4a55-92bd-e43eca44cab7@proxmox.com> (raw)
In-Reply-To: <20250702091056.60732-1-s.shaji@proxmox.com>
LGTM, and built + tested fine here,
but maybe someone else also wants to take a look too... (@thomas?)
Does it even make sense to set the targetSdkVersion higher than the compiled one?
Otherwise, consider this
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
On 7/2/25 11:10, Shan Shaji wrote:
> The current target API level is 34(Android 14). According to
> google play requirements the target API level should be
> within one year of latest Android release.
>
> To fix the issue update `compileSdkVersion` to 35 (Android 15)
> and `targetSdkVersion` to API level 36 (Android 16). The
> `compileSdkVersion` was not updated to API level 36 as
> `biometric_storage` [5] plugin's compileSdk is 35.
>
> Plugins (pve_flutter_frontend):
> - flutter_inappwebview [0]
> - shared_preference [1]
> - path_provider [2]
> - url_launcher [3]
>
> Plugins (proxmox_login_manager):
> - shared_preference [4]
> - biometric_storage [5]
>
> [0] - https://pub.dev/packages/flutter_inappwebview/versions/6.0.0#requirements
> [1] - https://pub.dev/packages/shared_preferences/versions/2.3.4
> [2] - https://pub.dev/packages/path_provider/versions/2.1.5
> [3] - https://pub.dev/packages/url_launcher/versions/6.3.1
> [4] - https://pub.dev/packages/shared_preferences/versions/2.2.3
> [5] - https://github.com/authpass/biometric_storage/blob/63c3dc3cd74729c78e4fc2de54b36e0db9540cbf/android/build.gradle#L34
>
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
>
> The version was updated as we received an email from Google play
> to update the target API level and release a new version before
> 31st August 2025.
>
> The exact versions of the plugins are taken from the `.lock` file
> as we are using the caret versioning for our dependencies in
> `pubspec.yaml`.
>
> android/app/build.gradle | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/android/app/build.gradle b/android/app/build.gradle
> index bcb364d..a749e46 100644
> --- a/android/app/build.gradle
> +++ b/android/app/build.gradle
> @@ -44,7 +44,7 @@ def keystoreSecret = System.getenv('PROXMOX_APP_KEYSTORE_SECRET')
> : keystoreProperties['keyPassword']
>
> android {
> - compileSdkVersion 34
> + compileSdkVersion 35
> namespace "com.proxmox.app.pve_flutter_frontend"
>
> sourceSets {
> @@ -55,7 +55,7 @@ android {
> defaultConfig {
> applicationId namespace
> minSdkVersion 23
> - targetSdkVersion 34
> + targetSdkVersion 36
> versionCode flutterVersionCode.toInteger()
> versionName flutterVersionName
> testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-03 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:10 Shan Shaji
2025-07-03 14:03 ` Dominik Csapak [this message]
2025-07-03 14:20 ` Tim Marx
2025-07-03 14:28 ` Thomas Lamprecht
2025-07-03 14:25 ` Thomas Lamprecht
2025-07-03 14:45 ` Dominik Csapak
2025-07-03 14:56 ` Thomas Lamprecht
2025-07-03 15:18 ` Tim Marx
2025-07-04 6:52 ` Shan Shaji
2025-07-04 8:53 ` Thomas Lamprecht
2025-07-04 11:15 ` Shan Shaji
2025-07-07 9:51 ` Shan Shaji
2025-07-03 14:36 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20499aba-f114-4a55-92bd-e43eca44cab7@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox