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. > > Otherwise, consider this > > Reviewed-by: Dominik Csapak <d.csa...@proxmox.com> > Tested-by: Dominik Csapak <d.csa...@proxmox.com> _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
