I have to persist 2 strings for my application even after the application is uninstalled. Regarding that the end users don’t have SD cards for their devices and they don’t have internet connection, how could I persist those 2 strings even after the app is uninstalled?
I would highly appreciate any response.
Unless you’re targeting VERY old phones, you don’t need to worry about not having external storage. As long as you use
Environment.getExternalStorageDirectory() as your reference, you shouldn’t have a problem, though if you’re absolutely concerned about this you can check if the external storage doesn’t exist and then opt to go to internal storage. Check out this link from the developer docs for a little more insight.
If External truly isn’t available, you could then save to Internal memory, but you will have to declare a new permission for that, which may ward off some people.
You have to write it to an SD card/internal storage, and hope the user does not remove that. However, this is a very fragile approach. There is no other solution, as far as I know.
Phones internal storage is also treated as an “SD card”. If you create a folder and save it in a text file, it should be safe given user does not manually delete folders after uninstall.
Please check out a section “Saving files that should be shared” in the following web page. Making a file that persists after uninstall entails making it available to other apps/user to read and modify. If those file options aren’t intended, you should consider an alternative app design.
After re-install, your app can access the created public directory by using the following function:
public static File getExternalStorageDirectory ()
Regarding the function above, per Google:
Note: don’t be confused by the word “external” here. This directory can better be thought as media/shared storage. It is a filesystem that can hold a relatively large amount of data and that is shared across all applications (does not enforce permissions). Traditionally this is an SD card, but it may also be implemented as built-in storage in a device that is distinct from the protected internal storage and can be mounted as a filesystem on a computer.
Also, Google recomments placing shared files into a an existing public directory as to not pollute user’s root namespace.
Are the strings unique to each user or are they app specific? In either case, the right thing to do would be to save it in some kind of remote server. Firebase is what I use for something like this. Check for its existence in your
Application class and download and save it to
SQLite if it doesn’t exist. For user specific data however, you are going to need some kind of authentication so you know which user is getting what.Firebase does this perfectly well too.
Going by the requirements (no internet, no SD card) of the OP however,I don’t see any other way besides one that isn’t unethical.