Before this morning, there was still DownloadToASD, and it didn't work.
Now:
The image shows the entire code for screen 1.
The extensions include ASDDownloader only.
The app starts, but apparently the file has not been downloaded, or is not in the right place, because in the visit screen, I do not have the markers corresponding to the data of the .csv file supposed to be downloaded.
With the DownloadToASD extension, I didn't need to enter the full path.
Does the full path change from one smartphone to another?
If so, it will be complicated to install it on different smartphones.
The extension works like a charm, but I want to know how to create a folder inside the Documents folder. In the MFile extension, when I use the block Create Directory with the path file:///storage/emulated/0/Documents/123, it successfully creates the 123 folder inside Documents.
However, when I use your extension and call the Create Folder block with either "file:///storage/emulated/0/Documents/123" or "/storage/emulated/0/Documents/123", it doesn't create the folder.
What is the best approach to achieve this?
Here visibility referred to ShowNotification property which is by default set to false.
Since companion doesn't have android.permission.DOWNLOAD_WITHOUT_NOTIFICATIO permission it will throw runtime error.
To avoid this while testing is companion it is advised to enable show notification so that the runtime error will not throw. In Apk it will not cause any issue.
Shortly after releasing your extension, I gave you several hints regarding required storage permissions. However, I just noticed that your extension doesn't declare any storage permissions at all.
There are at least 16 methods that definitely require storage permissions. And on Android under 4.4 (KitKat, API 19), storage permissions are required in every case (including for the ASD).