ok i figured it out.
i understand that you guys doing a tedious job but if appinventor had a better debug environment it would help us all a lot
so here is what happens
in the motiontrack.initialize
the list was never generated because it was after the
so the add.items to list loop was never executed because the program jumped out of the block and then the list was length 0 - makes sense.
once i move the add.item loop to the top (just BEFORE the file stuff) all worked.'
also because of the file1.scope block
i get in the development environment the run time error
'item is neither class nor type'
but this shows up only once and all is ok
to ABG's question
you are right that is a questionable code and i took it out.
the purpose was that i tried to preserve the data in case the INITIALIZE is done again when i leave the app and come back but that does not work either i guess, so you are right - was a bad idea.
all this file stuff in android 11 is still a black box to me but at least now i can continue in the development environment with out the pop up error.
we need better debugging and break points.
so thanks again and i am really sorry you had to crawl through my code - not nice i know.
i am not sure how i can support your work, where do i donate?
but i hope my 2 hour debug activity and explanation also helps you a little