Fixed
Status Update
No update yet.
Comments
el...@google.com
I created a thread on the android-developers forum related to this bug:
http://groups.google.com/group/android-
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
developers/browse_thread/thread/6caa57135927e242/86d4d895e88a5ebb?
lnk=gst&q=custom+account#86d4d895e88a5ebb
ap...@google.com
My personal theory is that Google broke this part of the API intentionally to keep
the lock-in on sync functionality they've enjoyed since Android 1.0.....
the lock-in on sync functionality they've enjoyed since Android 1.0.....
el...@google.com
li...@linkly.com.au
[Comment deleted]
el...@google.com
el...@google.com
ExternalSource.java bug
protected void inflate(Context context, XmlPullParser parser)
{
final AttributeSet attrs = Xml.asAttributeSet(parser); << It can't read any
attributes from the ContactsDataKind tag. It should located blow the second while
loop.
try
{
int type;
while((type = parser.next()) != XmlPullParser.START_TAG &&
type != XmlPullParser.END_DOCUMENT)
{
// Drain comments and whitespace
}
if(type != XmlPullParser.START_TAG)
{
throw new IllegalStateException("No start tag found");
}
if(!InflateTags.CONTACTS_SOURCE.equals(parser.getName()))
{
throw new IllegalStateException("Top level element must be " +
InflateTags.CONTACTS_SOURCE);
}
protected void inflate(Context context, XmlPullParser parser)
{
final AttributeSet attrs = Xml.asAttributeSet(parser); << It can't read any
attributes from the ContactsDataKind tag. It should located blow the second while
loop.
try
{
int type;
while((type = parser.next()) != XmlPullParser.START_TAG &&
type != XmlPullParser.END_DOCUMENT)
{
// Drain comments and whitespace
}
if(type != XmlPullParser.START_TAG)
{
throw new IllegalStateException("No start tag found");
}
if(!InflateTags.CONTACTS_SOURCE.equals(parser.getName()))
{
throw new IllegalStateException("Top level element must be " +
InflateTags.CONTACTS_SOURCE);
}
el...@google.com
Any feedback from Google guys?
It doesn't seem to be fixed in Android 2.2 and actually is going to be a blocking issue for third party sync providers. We cannot claim to sync contacts if the user cannot edit them.
Looking at the code, the fix is very easy (at least to let sync providers to use the same contact structure used by Google accounts).
Please let us know if and when you can work on this.
It doesn't seem to be fixed in Android 2.2 and actually is going to be a blocking issue for third party sync providers. We cannot claim to sync contacts if the user cannot edit them.
Looking at the code, the fix is very easy (at least to let sync providers to use the same contact structure used by Google accounts).
Please let us know if and when you can work on this.
Description
Component used: Room Version used: 2.7.0-alpha-07 (multiplatform) Devices/Android versions reproduced on: No run device needed. Only a Mac to compile on iOS
If this is a bug in the library, we would appreciate if you could attach:
Tested commands :
I'm using a relation with Kotlin Uuid (experimental in 2.0.20) mapped to ByteArray (with UuidTypeAdapter) and stored as BLOB in the database. When I try to run the ksp task to generate iOS code, an error occurs.
I suppose the same issue happens for every non JVM targets.
When I don't use relation (Replace MyEntityEmbed by MyFirstEntity in MyDao), the code compiles correctly.
I think room tries to generate a code near to the one generated for android which uses ByteBuffer to decode BLOBs.