I'm using: android.content.ContextWrapper.getExternalFilesDir(null)
as the location to store my app's files. The app is designed to run on API versions 8 (Android 2.2) onwards. Whilst testing on the emulator running 2.2 I find that if I upgrade the application then it deletes the existing files in this location. This has been discussed before: https://groups.google.com/d/topic/android-developers/to1AsfE-Et8/discussion Dianne Hackborn gave details of the patch which was made to Froyo, presumably in a subsequent build. According to: http://developer.android.com/resources/dashboard/platform-versions.html 2.2 still comprises about 20% of devices so I'd like to support it but I don't want to risk deleting users' data which in my app is user generated and might not be recoverable. The Platform Versions report doesn't break the figures down by build number so it's difficult to know how many users could be affected by this. Can anyone help? Am I worrying unnecessarily? Were many 2.2 devices released with this bug still in? If the emulator had been patched I might not have spotted the problem but the fact that it isn't makes me reluctant to ignore it. I know I could sidestep the issue by simply choosing my own directory but I'd like to follow best practices if I can. TIA Simon -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
