A Alex_197 Well-Known Member Licensed User Longtime User Aug 30, 2020 #1 May I ask you a question myself - if for Android 10 we need to make so many changes for write permissions as we see in many threads on this forum - what about backward compatibility? I still have many customers who are using Android 8 or 9 and I don't want them to upgrade their phones to Android 10 just because Android 10 requires so many changes. Is it possible?
May I ask you a question myself - if for Android 10 we need to make so many changes for write permissions as we see in many threads on this forum - what about backward compatibility? I still have many customers who are using Android 8 or 9 and I don't want them to upgrade their phones to Android 10 just because Android 10 requires so many changes. Is it possible?
Erel B4X founder Staff member Licensed User Longtime User Aug 31, 2020 #2 Nothing has changed in Android 10 related to runtime permissions. The changes are explained here: android.jar / targetSdkVersion / minSdkVersion Upvote 0
Nothing has changed in Android 10 related to runtime permissions. The changes are explained here: android.jar / targetSdkVersion / minSdkVersion
A Alex_197 Well-Known Member Licensed User Longtime User Aug 31, 2020 #3 Erel said: Nothing has changed in Android 10 related to runtime permissions. The changes are explained here: android.jar / targetSdkVersion / minSdkVersion Click to expand... So if I use RuntimePermissions.GetSafeDirDefaultExternal to get a Dir name it will be Ok with TargetSDK 29 and 30 and will be Ok for Android 9 and 10? Upvote 0
Erel said: Nothing has changed in Android 10 related to runtime permissions. The changes are explained here: android.jar / targetSdkVersion / minSdkVersion Click to expand... So if I use RuntimePermissions.GetSafeDirDefaultExternal to get a Dir name it will be Ok with TargetSDK 29 and 30 and will be Ok for Android 9 and 10?
