Fixed
Status Update
No update yet.
Comments
ga...@gmail.com
I'm having the same problem and unfortunately there's no trace of the error (I can't find it on logs at least).
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
My scenario: I have an App Engine project for Java, with billing enabled, with running backends, with HRD (mirrored from an old Master/Slave project), some idle instances and no custom domain.
yb...@google.com
yb...@google.com
I also have this error. Any idea?
ga...@gmail.com
I'm seeing the same problem. I believe this is the only way to use the Blobstore with Google Cloud Storage, correct? I'd be happy to create a different storage account but it doesn't seem possible to use the Blobstore/GS integration...
yb...@google.com
I too am having this problem with the application parrot-pairing, although the otherwise-identical app parrot-pairing-dev worked fine the first time.
Description
Version used: 1.0.0-alpha9
The errorHandler field of SupportSQLiteOpenHelper.Configuration[0] uses android.database.DatabaseErrorHandler[1]. The problem is that the onCorrupted method of DatabaseErrorHandler has android.database.SQLiteDatabase as parameter, which custom implementations won't have an instance of because they write their own implementation of android.arch.persistence.db.SupportSQLiteDatabase[2]. My proposal would be to add a SupportDatabaseErrorHandler which uses SupportSQLiteDatabase instead of the platform one.
[0]:
[1]:
[2]: