Fixed
Status Update
No update yet.
Comments
yb...@google.com
ap...@google.com
Hi, sorry for the trouble. I am working on improving our radio HAL. Unfortunately, it will take a while because it is very large. Please do not send non-ASCII characters in SMS.
da...@google.com
[Deleted User] <[Deleted User]>
Hi, I don't know if it may be implemented as quick fix on the actual code, but looks like Ñ is the only alphabet letter having the issue (at least between ones widely used within GSM 03.38 GSM 7-bit).
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
da...@gmail.com
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
I see, maybe we missed that one Unicode somewhere then. Could be easier to fix then. I will take a look this week. Thank you for pointing this.
da...@gmail.com
Just to get the full picture, I've tested with all characters included here https://en.wikipedia.org/wiki/GSM_03.38 both in Basic Character Set (they should take 1 char of the 160) and Basic Character Set Extension (they should take 2 char, first is ESC prefix) and the only one causing the issue is Ñ
Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.
Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.
Description
Version used: 1.1.1
Kotlin version: 1.2.51
Room can't detect the TypeConverter of a List<Model> if that Model itself is written in Java and if I convert this class to Kotlin, it works as expected!
I got this error no matter where I put the TypeConverters annotation!
error: Cannot figure out how to save this field into database. You can consider adding a type converter for it.
A project where this can be reproduced is attached!