It no longer makes sense to list all other bugs related to the File component here.
So again my conclusion:
As I said before, all functions / methods of the File component can be performed with one of the File extensions and / or my MFile extension. Since these have been working well for years (most recently also on Android 11+), it shouldn’t really be a problem to implement this with the File component as well.
As long as this has not been implemented without bugs (and this also applies to AI2 with regard to the WRITE permission problem on Android 11+) I recommend using the extensions mentioned (instead of the File component).
I have already explained in detail several times how to fix the problems and bugs regarding the File component.
But apparently nobody (at least from the platform executives) is listening to me.
Save an image with Canvas in one of the Shared folders - issue / bug
Following the AI2 logic with DefaultFileScope=Legacy an image created with Canvas should then be saved in one of the Shared folders if the path at Canvas.SaveAs is set to e.g. /Documents/myCanvas.jpg has been set.
However, this is not the case. The image is always stored in the ASD.
**So there is no way to save directly to a Shared folder in Kodular (with Canvas).
You always have to take the detour of moving it back there later.