For a bit of explanation, this only strictly affects exporting sites to a file. 
It somewhat affects file imports as well, but not as adversely as exports.

A bit of additional information, primarily sourced from here:

https://developer.android.com/about/versions/android-4.4.html

It looks like the ability to WRITE to anywhere on external storage is now a bit 
of a no-no in KitKat and up. This isn't necessarily a HUGE problem for us, but 
a different paradigm that individual users are going to have to get used to. We 
can restore the ability to READ from any location by using 
Environment.getExternalStoragePublicDirectory() rather than 
Environment.getExternalStorageDirectory(), but writing will be restricted to 
whatever is returned by Context.getExternalFilesDir().

Prior to Version 1.1.0 of Cryptnos, users were restricted to importing and 
exporting to just the root of the SD card. In 1.1.0, we allowed users to import 
and export from anywhere on the card as long as they had a recognized file 
manager app installed that allowed them to select the file to import or the 
folder to export to. Perhaps the best fix here will be to go back to the 
original functionality and restrict imports and exports to the folder returned 
by Context.getExternalFilesDir(). This limits the user's freedom a bit, but 
that's what we're stuck with.

The question is whether we should force this upon ALL users, or just those in 
KitKat or above. Frankly, I hate restricting users, but I also dislike having 
to maintain multiple functionalities for multiple versions. So odds are I'll 
probably end up ripping out the file manager connection code and the choice of 
where to where read and save files.

Yeah, I think that sucks too.

We'll definitely need to notify the user of this change and offer suggestions 
on how to move files outside the special magic directory into it.