My app crash until I put manually the memory permission by device settings

andreapetricola · July 28, 2021, 8:07pm

After updating to Kodular version 1.5.0, I believe I encountered an error with the apk files.
When I install the apk on my device and launch the application, it crashes immediately.
Checking his information I saw that he did not have any permissions granted (the app crashes without even asking me for permissions).
I had to manually set the storage permission to allow the app to open.
Before update 1.5.0 I didn’t need such a thing.
is it a Kodular bug? or do I have to use some specific block?
I specify that in my app I use the blocks of “Google Ask Permission” for Write and Read External Storage.

Still-learning · July 28, 2021, 10:25pm

Can you share your screen initialise blocks and the extensions used ?

andreapetricola · July 28, 2021, 10:45pm

Sure, but is long, I’m sorry for this.

Immagine10

andreapetricola · July 31, 2021, 10:26am

Someone who helps me? I need to update my app but until this crashes I don’t

bodymindpower · July 31, 2021, 10:45am

Try this:

and move the File.CreateDirectory block to the PermissionGranted event.

Note: WRITE permission implicitly grants READ permission.

andreapetricola · July 31, 2021, 10:57am

like this:
Immagine
the app keeps crashing, from the app information there is no authorization allowed

bodymindpower · July 31, 2021, 11:04am

Remove all blocks from Screen1.Initialize except for the AskForPermission block and try again:

bodymindpower · July 31, 2021, 11:11am

If that works (and it should), move the removed blocks into the PermissionGranted event.

andreapetricola · July 31, 2021, 11:15am

I put the blocks like this and moved the removed ones to the backpack:
Immagine
but the app crashing again with the same problem

bodymindpower · July 31, 2021, 11:23am

Post the aia or send it to me privately via PM.

andreapetricola · July 31, 2021, 11:31am

Message sended thanks for the help

bodymindpower · July 31, 2021, 12:44pm

Your app crashes even with no (0) blocks.
Apparently some component or extension needs READ / WRITE permission before Screen1.Initialize is triggered. Find out for yourself by removing one at a time and trying again, then the next …
Good luck

andreapetricola · July 31, 2021, 1:05pm

but before the platform update such a thing was not necessary … it’s frustrating.
Well…excuse the ignorant question: how do you give permissions to components and extensions before the screen is initialized?

bodymindpower · July 31, 2021, 1:17pm

I think this is not possible.

andreapetricola · July 31, 2021, 1:19pm

So, excuse the question again: but what do I do?
If I have to remove the problematic extensions, I have to totally redo the app from scratch.
How do I manage this situation?
moreover, if even with 0 blocks the app crashes, it means that the problem could also be the project itself, because 0 blocks means 0 components and 0 extensions, right?

EDIT: in searching for a solution i found this post, the problem was solved

system · August 30, 2021, 1:20pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.