Fixed
Status Update
No update yet.
Comments
yb...@google.com
ya...@google.com
ya...@google.com
Hello everyone. Is this bug going to be fixed? I have to install 3rd party app to emulate the location. I really need this feature. Please, fix it.
gm...@gmail.com
Issue happens also on ubuntu 22.04
ya...@google.com
Issue happens also on POP_OS 22.04
gm...@gmail.com
I have the same issue on Ubuntu 22.04. There is for a quick moment a white square where the map should be, but it is gone in a blink. Not sure if it is related, but when selecting a saved route, a grey overlay with the text "Loading Saved Route.." appears. This remain in place forever until the emulator is closed. (screenshot attached)
ya...@google.com
Same, blank map, white square at first but then nothing.
Also keeps loading when uploading saved route.
SDK does not change anything, I'll try changing API 33 to another one maybe that's the issue.
Ubuntu 22.04
Also keeps loading when uploading saved route.
SDK does not change anything, I'll try changing API 33 to another one maybe that's the issue.
Ubuntu 22.04
ap...@google.com
Same happening to me on Ubuntu 22.04.
I tried several API emulators (23 to 33).
Also tried deleting and creating emulators again.
Also tried rolling back the emulator version a couple of versions prior.
Calling the emulator in the command line instead of in the IDE, does not solve it either.
Nothing worked and I have both problems: map does not appear and when clicking the routes, it gets stuck on Loading.
I tried several API emulators (23 to 33).
Also tried deleting and creating emulators again.
Also tried rolling back the emulator version a couple of versions prior.
Calling the emulator in the command line instead of in the IDE, does not solve it either.
Nothing worked and I have both problems: map does not appear and when clicking the routes, it gets stuck on Loading.
Description
Version used: 2.0.0
Devices/Android versions reproduced on: Wileyfox Swift (API 25)
Not reproduced on Android Emulator API 15 (probably due to different SQLite version).
SQLite constraint violation on method annotated with @Insert(onConflict = OnConflictStrategy.ROLLBACK) causes SQLiteException instead of SQLiteConstraintException.
Stack trace example:
E/AndroidRuntime: FATAL EXCEPTION: Thread-8
Process: gmk57.roomtest, PID: 2152
android.database.sqlite.SQLiteException: cannot rollback - no transaction is active (code 1)
at android.database.sqlite.SQLiteConnection.nativeExecute(Native Method)
at android.database.sqlite.SQLiteConnection.execute(SQLiteConnection.java:555)
at android.database.sqlite.SQLiteSession.endTransactionUnchecked(SQLiteSession.java:439)
at android.database.sqlite.SQLiteSession.endTransaction(SQLiteSession.java:401)
at android.database.sqlite.SQLiteDatabase.endTransaction(SQLiteDatabase.java:524)
at androidx.sqlite.db.framework.FrameworkSQLiteDatabase.endTransaction(FrameworkSQLiteDatabase.java:90)
at androidx.room.RoomDatabase.endTransaction(RoomDatabase.java:266)
at gmk57.roomtest.DataDao_Impl.insertRollback(DataDao_Impl.java:99)
at gmk57.roomtest.MainActivity.violateRollback(MainActivity.java:67)
Taking into account that
1) Room wraps methods annotated with @Insert, @Update and @Transaction in explicit transaction, and
2) ABORT, FAIL and ROLLBACK all throw SQLiteConstraintException, effectively rolling back this transaction
- the broader question is: is there any reason to provide FAIL and ROLLBACK options at all?
I also think the documentation should clearly describe the behavior of each strategy in specific case of Android + Room (e.g. which strategies throw an exception and which do not), instead of just linking to partly irrelevant SQLite documentation.
Sample project attached.