![]() So there you have it Google simply don’t want proper, grown-up, commercial apps running on Android. Yes, one could do this on Android 10 if one marked the app with READ_EXTERNAL_STORAGE and/or WRITE_EXTERNAL_STORAGE, but now on Android 11 even if one marks one’s app with MANAGE_EXTERNAL_STORAGE you still can’t access a db created by another app OR a previous version of one’s own app.Īnd even if ANY of the above were possible, one would fall foul of the policy at Google instigated by the ‘spotties’ which says ‘anything we don’t like or approve of, you won’t be able to upload to the Play Store’ so go take a hike, Mr Old Fogey Developer. Even if the db resides in an ‘external’ or so-called ‘public’ directory in fact even if it resides in ANY directory ANYWHERE within one’s particular version of Android. it only allows access to itself by its creator application and EVEN if one deletes the application (leaving the db behind) and downloads EXACTLY the same application (without any changes whatsoever) then that app cannot open the db - created by a previous incarnation of itself - in any shape or form whatsoever. that database is inextricably linked – glued if you will – to the application that created it i.e. I have spent the last week-end reading all the docs and trying hundreds of different test and it boils down to this: when one builds an Android app, one is casting it in concrete, because even if one finds an external directory AND one manages to create a database inside it. They don’t know how, and they can’t learn how, to do it and they don’t WANT to know how to do it. ![]() Google will ‘pull the rug out from under your feet because the ‘spotties’ have never written – or can ever know how to write – a proper commercial or scientific operating system. So if one develops an application - and targets a particular Android version – one is going to come unstuck one day. As Ken Olsen (and I paraphrase here) once opined ‘ here on the East Coast we develop computers, out on the West Cost they just build toys’ and that’s the nub of it.Īndroid 11 closed all the loopholes that Android 10 allowed so ALL of us grown-up developers at the mercy of Google who now ship every new tablet, phone and device with Android 11 or Android 12 or whatever one thing for certain is – they are never going to go backwards. Its because the ‘spotty-faced kids who can’t get a date’ at Google ‘developed’ a system and are petrified of allowing users to do anything useful on it. ![]() I have also tried the solution to create pre-populated DB but with no luck: Īny idea why this is happening? We also have users on OnePlus and Pixel reporting the same A Persistent Android Database Is Never Going To Happen Operating System and version (simulator or device): Oppo Color OS 11, Android 11Īs shown above, the db was created but at /data/data//databases/.React Native SQLite Storage Version used: "5.0.0".Note that this code works fine on older Color OS and other Android phone like Samsung and Huawei Your Environment Related to Android 11? Steps to Reproduce (for bugs) Expected BehaviorĭB connection is as usual and DB can be opened. I have verified the app and plugin work fine on Color OS 7 and 10, but broken on 11. OPEN database: StorageExtension.db failed, aborting any pending transactionsĪnd following if trying to call any transaction:Įrror: openDatabase ] ![]() After updating their phone's OS( Color OS) to 11(Android 11), SQLite operation is broken. Some of our users have reported an issue related to the SQLite lib.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |