Fixed
Status Update
No update yet.
Comments
yb...@google.com
Same proble on epic 4g
lo...@gmail.com
Same problem on htc evo
yb...@google.com
Sample problem/bug on Samsung Captivate (Galaxy S) running 2.2. Probably pretty annoying to my co-workers...
yb...@google.com
Same problem om Samsung Galaxy S II
yb...@google.com
Same issue on my HTC Thunderbolt. Please fix, would make me very very happy to hear notifications while at work and listening to music, instead of going all day missing all sorts of notifications because i need to keep my phone on silent. Really kinda expected this feature to already be part of the great package that is android+HTC so let’s add this seemingly simple addition and quite us all down!
lo...@gmail.com
Same here, pretty annoying. Using a Samsung Galaxy S running 2.2.1
Description
Version used: beta-1
Devices/Android versions reproduced on: happens at compile time
The sample project attached to this bug report shows that Room does not check if I'm trying to get an entity from another table. The consequence is that sometimes I get an error which doesn't really say much: "error: incompatible types: <null> cannot be converted to boolean". This error is triggered by Kotlin's Boolean, which in the bytecode can be sometimes primitive types and so null fails to match. But when using another type, everything would be fine except that we are querying the wrong table for that entity.
See in the sample project the SomeDao.kt class: the first query causes a compile time error, while the second one (which for me is still invalid and would crash immediately in Kotlin since the type is non null) apparently is OK (is that expected? I understand that this is what allows Room to returns a different object from the entity and that's really powerful, but at the same time it opens the doors for a lot of mistakes which won't be catched at compile time)