It should work if you download the file to your ASD, then copy/move it to the Download folder.
From what you say about your workflow, there doesn't appear to be any need to move the file from the ASD, given that both devices fetch/save the data from/to a file on google drive ?
What does that mean? Do you upload the file to GD via the app or do you do it from your computer?
It remains unclear which steps should be taken:
And where does this file (with this path) come from?
If you are testing in apk then have you asked for READ_EXTERNAL_STORAGE permission?
This are the steps:
The first time that you use the app, the app asks permission to the external storage so you can agree.
little error: 5. In Testimport_copy ...
If you want tot use the app Testimport.apk on another tablet (to import the downloaded clublijst.csv ) from the Download directory the same error occurs.
That's right for my own google drive, but not if another user uses my app. The url will be diferent.
You can ask the user to copy-paste their URL into a TextBox, and substitute the link for the aforementioned component's text value.
Edit: Admittedly, my solution isn't very practical.
This is why I asked how the file should be uploaded to GD.
Explain precisely what the goal / purpose of your app is.
In other words, why should the csv file be uploaded to the user's GD?
The gaol is that data of members of the club kan be exported to an external storage on the cloud or e-mailed, so that the same data can be imported in another tablet.
The will be used by different users in different clubs. So you can't anticipate on wich external storage the user will save the data. Once the data (clublijst.csv) is on the external storage, the user must download it (or store it) himself to the Download directory of the app in the other tablet, so it can be imported to the ASD of the app.
Why not just share the link / file from one google account to all other users, then every user can access the same file ?
Each club has his own file. The datafile changes.
new information, after 25 posts !! 
Is it really that difficult to accurately describe the steps and purpose of the app. I had asked enough times. We are wasting a lot of time here, completely unnecessarily.
Sorry if this wasn't clear. Each club makes his own memeberslist and must have the posibility te export it to his own external storage, from where he can download it.
This can all still be stored in a folder on google drive in one google account, with correct permissions provided for all users to access (you could even do this with just one spreadsheet, with a sheet tab for each club...)
Have a good think about your methods and your workflow, then when you are ready.....
Yes ...
But how and by whom is the list drawn up? How do these people know what format this list should be generated in?
