ARC runtime: app can't open its database
Reported by
kmans...@gmail.com,
May 19 2016
|
|||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Steps to reproduce the problem:
I have this Android app called AquaMail.
Have had it repackaged using ARC Welder and released on Chrome Store for a while now, but there are some Chrome OS specific network issues (reported as a separate bug) since about 45 or so -- and so I decided to check where things are at now, with Chrome 50.
Things are worse than ever before.
The app's unable to open its SQLite database. At all.
Managed to get logcat output, it has these errors:
NOT IMPLEMENTED: chmod("/data/data/org.kman.AquaMail/databases/Messages.sqldb", 0660)
These are probably happening when my code calls:
context.openOrCreateDatabase(dbname, flags, null);
( flags = 0x0008, ENABLE_WAL )
A standard official Android method which has worked on real Android forever and also in ARC Welder for a long time (last checked around 45-46).
Now it doesn't. Basic stuff. App completely unusable.
---
Second thing I noticed is that the logcat is full of errors related to OAUTH2, apparently having to do with Contact sync, this is not related to my app at all, but as far as I can see is built into the Android image of ARC Welder.
I am logged into a @gmail account in Chrome, so I guess the ARC runtime is trying to sync my contacts.
There are "unexpectedly stopped" popups, i.e. crashes, too - and it's Google Play Services. Guess it's related to the failing contact sync, but it's only a guess.
---
I am very concerned about these regressions, esp. given the now official news about Google Play (and all apps) being made available on Chrome OS devices, automagically.
Now maybe I'm missing something, maybe ARC Welder is no longer supported and is no longer supposed to work.
But as far as I am able to tell (using ARC Welder), the experience of running Android apps on Chrome using ARC Welder has regressed to the point of being completely unusable.
What is the expected behavior?
Android code being able to open a database by using a standard official Android API.
What went wrong?
1 - Android code not able to open a database.
2 (unrelated) Google Play Services inside ARC runtime crashing, and there are OAUTH2 errors related to Contact sync in the logcat.
WebStore page:
Did this work before? Yes Before 45 or so
Chrome version: 50.0.2661.102 Channel: stable
OS Version: Fedora 23 x64
Flash Version: N/A
,
May 11 2017
,
May 11 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by kmans...@gmail.com
, May 20 2016