I don't see where the blocks delete files from the:
/storage/emulated/0/Android/data/edu.mit.appinventor.aicompanion3/files
directory ? (or am I missing something)
Ok, I understand it's supposed to clear the whole ASD. Yes, of course that's not a problem either, but it's not the topic here.
Please expand your block
If I understand well your block delete the folder, will this folder be re-created by companion?
Can I use this block instead of use Delete all assets button ?
How about trying it out?
Anyway, the answer is yes.
Why did you make many blocks for deleting assets files instead of deleting asd folder ?
Read the topic.
1 Like
For example: If many files have already been downloaded to the ASD (e.g. big videos), then these files would have to be downloaded again afterwards.
The purpose of the app is to only delete the assets and NOT all files in the root direcrtory and all subfolders of the ASD - as the topic already says.
for me, I choose to download the aia, unzip,delete assets folder, upload again.
But what for? What is that supposed to do?
ah, I misunderstand you. you are deleting the files in assets only from cellphone. but what is that for?
The app is about emptying the assets folder on the test device. This is useful, among other things, if extensions are to be updated correctly (as already explained in the description).
all this will update the extension in companion.
Is that a statement or a question?
If it's a statement, then it's true.
It will update all used extensions with Companion.
yes it's a statement. All this can update the extension, why need to delete all files from assets manually?
Yes, if there is only a problem with one extension, just emptying the comp folder would also be sufficient. But why make it more complicated than necessary? Because the assets are read in again when you restart anyway.
1 Like
What are you talking about here? Take some screenshots so I can understand what's going on and how you do it.
(I recently encountered this issue when I saw ghost files being loaded from my empty Media folder in leftover code, much to my confusion.)
Here is the fastest and simplest way I found, using facilities of the MIT AI2 Android emulator/Companion setup:
Getting to the Settings app from a Companion session was non-obvious to me, so I made a video of it, leaving the emulator at its desktop, primed for a possible drag onto its desktop of a fresh Companion .apk, in case self-updating fails.
1 Like
Yes, but this removes all permissions as well.
So it has the same effect as uninstalling and reinstalling the companion app.
1 Like