Re: [pve-devel] [PATCH pve_flutter_frontend v1] chore: update `compileSdkVersion` to 35 and `targetSdkVersion` to 36

From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Shan Shaji <s.shaji@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:45:18 +0200	[thread overview]
Message-ID: <9e82aa80-6e7e-406e-9ea0-92ec3dc7c79e@proxmox.com> (raw)
In-Reply-To: <a4adab73-1ce4-48a3-b66e-86770523cde8@proxmox.com>

On 7/3/25 16:25, Thomas Lamprecht wrote:
> Am 03.07.25 um 16:03 schrieb Dominik Csapak:
>> 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?
> 
> Yeah, that can be fine, the targetSdkVersion basically denotes what (API)
> version one tested the App against and signals Android that it doesn't need
> to enable any backward compat handling as long as the Android (API) version
> is equal or lower than the provided targetSdkVersion.
> 
> Such compat handling could e.g. be w.r.t. App permissions, if there are
> newer more granular one, or the default set got reduced it might break older
> apps, so that is only enabled if the app signals that it supports it,
> naturally with some time window to not allow uploading an app (update) to
> avoid that this can be misused.
> 
> The compileSdkVersion is the API the app is compiled against and thus
> one can only actively use newer APIs if one increases this. Most of the time
> one want's to have those two in sync, but it's fine if the targetSdkVersion
> gets higher, it just cannot be lower than the compiled one.

sorry to continue this, but there is something I don't really understand here
(not that I want to say you're wrong, just wanting to understand)

how can my 'target sdk version' be higher than my 'compiled sdk version' ?

in that, how can i target sdks that are newer than the one i compile against?
wouldn't that mean that the old sdk (e.g. 35 in our case) must have
knowledge about the next version ?

e.g i found an article[0] about those versions (not sure how good or representative it is)

that explicitely says:

---
If you made it through the bolded notes, you’ll notice a relationship between the three values:

minSdkVersion <= targetSdkVersion <= compileSdkVersion
---

which would mean that my target version can't be higher than my compile version...

that said, the app built successfully with these values, and I noticed no problem
with either android 15 and 16 (in an emulator...)

0: 
https://medium.com/androiddevelopers/picking-your-compilesdkversion-minsdkversion-targetsdkversion-a098a0341ebd

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel