Thanks for your prompt reaction. But I see that not telling you the whole story made it unclear to you, sorry for this.
As a matter of fact, I did perform some testing, which consisted of:
- Trying to identify AI Companion's external private storage on my cell using "My Files" app. It looked to be:
- Copying one of my own files from my own directory on the cell to the one above (file "Al_DVD-list-1col.prn" as visible above).
- Then testing as usual my App with Companion on my cell .. and this worked
- Connecting my cell to my PC with an USB cable and opening the cell's directory from my PC (W10) using the usual Windows Explorer .. and then I got the following
So, from the PC, my issue was that I had no visibility on my file "Al_DVD-list-1col.prn", hence my 1st question about being or not able to access a no-READ-permission-external-private-storage from a PC.
- Then I unchecked the "Legacy mode" flag .. and my app stopped functioning again
So, either that "edu.mit.appinventor.aicompanion3/files" is not AI Companion's external private storage, either it is the right storage, but something else blocks in Android. Either way, I don't gain the knowledge just reading MIT AI's and others' documentation .. hence all my questions
NOTE: About your other note "How should an app or certain functions of an app be tested without an app or any code existing?" -> This is not what I've tried to express.
My understanding of AI Companion, wrong perhaps, is that it doesn't compile on the fly but interprets AI's blocks (or something close to this), a little like the BASIC language a "long" time ago So, my new app not being yet compiled (or "generated" in my previous sentence), there should be no specific app related external private storage yet existing, hence my question "how can I test all this using AI2 companion when no app got generated yet?"
.. and for this 2nd question, I'm now guessing I'll have to do all this in two steps, one test with the app generated / downloaded onto my cell, but not functioning because using the wrong file directories path, but hopefully having then visibility on the app's newly created external private storage, and a 2nd test after having re-generated the app with the correct file path .. we'll see