In the last week, I have had a flood of emails(like 5) saying that my app is telling them a folder already exists when it does not.
Checking the code, I see that I am calling File.exists(), and it returns true when it shouldn't. It seems this is happening on Samsung S6, and some S5s that likely have received a recent firmware update. Anything that would cause File.exists() to return false positives? Did Samsung change the directory separator so that paths changed in preferences will now be invalid? Did it start using "archives" as a reserved word? Did it start requiring FileScanners for all files? I can (and probably will) change File.exists() to File.isDirectory(), but I don't have the hardware to confirm that it changes anything. Yes, I know that this is a bit of a longshot, but I am perplexed. Please skip telling me that Samsung can't possibly have as stupid of a bug/feature as this. Topics like this suggest that it is a possibility: http://android.stackexchange.com/questions/109833/images-have-disappeared-from-gallery-but-still-in-my-files-samsung-galaxy-s6 Nathan -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
