We all know about the mess that Marshmallow brought with extended memory. I do have an occasional patient who complains that they can't access the database which is kept in an "extended memory" folder as it has been for years (and as many apps do). The only way I can replicate their problem is to turn off the new memory permission setting in Settings for my app. But the patient usually has that on (as it is usually on by default). Code is exactly the Google recommended procedure for this. Either something has corrupted their database though in the past when someone had this they sent me a copy of the database and it was okay. Or something is blocking it. Or some manufacturers have messed this feature up on the phone. My tests both with Android 6 emulators and a device show everything okay.
-- 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]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/b783bce9-2631-47b4-b4f5-42624a8319ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
