File component could not error

[hammerhai (Nathan)]

Thankfully I have the right one for you!

To see instructions on how the storage extension works with paths, view this post…

Moon – 4.0.0-alpha.1

I’m pulling the plug The plug is no longer being pulled! See more by going to this post! Device M’ was a pleasant project to work on last year. Although I did have plans to previously “pull the plug” on Device M’, those plans have been trashed and have ever since changed… According to this post. Since Device M’ is now open-sourced, I would like to thank my Beta Testers! You were all wonderful! Thank you… @yanquisalexander @avmcreators02 @David @FahadAhmad @Feder…

To download the storage extension, view the following post and open the “Original reply (includes v3.0.1 and v3.1.1)”…

Moon – 4.0.0-alpha.1

Original reply (includes v3.0.1 and v3.1.1) Android 12 & Extended Support Hello everyone! Recently the Android 12 Developer Preview was released, and APIs are already changing. With that happening, I am keeping a close eye on what’s changing for a specific reason. That is, I’ve decided that I will continue releasing major upgrades to Device M’. It may come as a surprise, but it is to simply keep up with consumers keeping their devices longer and OEMs supporting them longer. Q & A Summaries…

@bodymindpower

Where could be the problem to ask for WRITE permission at Screen.Initialize

No, when doing anything with files, the File component will ask for permissions REGARDLESS of it’s path.