@bodymindpower whats the solution what changed should we do to remain our app in production or can able to update that. i had read the artical from the link given by you, but still didn’t know what particularly changes we have to do ?
This new storage thing is quit confusing, I am still trying to understand that what changes should I do to satisfy Google’s guidelines 🥲
I have Also Received the mail But I didn’t Check my inbox So what is the solution
Ok, So, We have to wait Kodular to fix this problem…
Is it possible to have a communication on it ?
As I understand it, there shouldn’t be any problems as long as the app targets Android 10 (API 29), which is currently still the case with Kodular and AI2 (at least until the end of July 2021).
I think this is a general warning about
requestLegacyExternalStorage that will only become relevant once Kodular is targeting Android 11 (API 30).
(But it’s true, it’s a bit misleading.)
Android 10 devices:
requestLegacyExternalStorage works regardless of targetSdkVersion
Android 11 devices:
- targetSdkVersion = 29:
- targetSdkVersion = 30:
Got same mail from Google, like to know in what components of Kodular platform having this requestLegacyExternalStorage command.
This is declared in each app in the
This is correct. No changes have to be made to apps at this moment; you can continue to update your apps well beyond May 5 as Kodular currently targets Android 10.
Once we bump the target SDK level to 30, users who wish to access the entire filesystem will have to let Google know why. I believe we’ll have more information about this as we implement scoped storage and the media store into our apps.
However it is specified “To release your app on Android 11 or newer after May 5th, you must either:” which suggests that the apps we update or publish will not be compatible with Android 11, or Google Play won’t make them available on devices with A11
No, as @Vishwas and I said earlier, this is not true as long as Kodular is still targeting API level 29 (Android 10). So ignore the message / warning.
I also encountered this problem, all published applications received this letter, and it was not a general letter, but specifically sent for each application. It is very strange because even on the google play page in the permission tab for the application there is no requestLegacyExternalStorage. Google can easily demolish applications after May 5, the question is how to solve this problem?
By ignoring it.
im same problem please fix this problem kodular team
How about reading before posting.
There is nothing to fix for Kodular.
! yes it is big problem
if i add this code in manifest and update my application. Will it fix the problem?
<uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE" />
Yes and no. You’ll need to have a valid explanation for adding it… Why do you need to access the shared filesystem?
same problem here please solve this problem