Settings namespace not launching correctly (natively) on RPi

[Vegz78]

Hi,

There is some peculiar behaviour with the settings namespace/extension when launched the first time (natively - .elf) on a RPi:
Vegz78/McAirpos#14 (comment)

It's still inconclusive, but preliminary tests suggests that maybe it might have something to do with write permissions inside the .elf.data folders that each game creates on the first launch, but on subsequent loading of the same game it no longer requires 777 permissions to write the storage files(755 is sufficient and the process owner is user pi).

Does anyone have enough detailed knowledge on the inner workings of the settings namespace to suggest a reason for or remedy for this behaviour?

Or maybe someone could test on MS' official MakeCode Arcade image with uf2 files to check if the same happens on the pi in this environment? Appreciate any help and insight!

[Vegz78]

Further testing has revealed:

1. The settings namespace functions and properties mostly work when running natively as .elf executables on the RPi, but one usually has to run/execute the game 2 times and with chmod 755 all around to ensure that the storage is written properly in the game_file.elf.data folder.
2. Except the settings.exists("string") property, which causes segmentation fault:
   Crashes(segfault?) - exists property - settings namespace - Raspberry Pi pxt-arcade#3812

Closing this issue, as it does not seem to be an issue with this settings extension, and it's mostly working with some work-arounds, except the above mentioned segfault.