IssueTracker

Thank you Zarah! It turns out there will definitely be a handful of error messages that I missed, as I learned some of them are hiding among other error messages that look like they're internal use only and should never surface to the user. At this point it looks like the best approach is to fix messages one by one as we see them leaking out :)

I'll fix this one shortly. If you see more odd messages, even if it makes 80% sense but could be written better, please keep 'em coming!

Hmm, so an interesting update... this error is not generated by data binding. :( It's generated by a deserialization library that we're using (SAX). I was baffled for a bit for why I couldn't find it in our codebase.

See also this random SO post, which shows the same error in a totally different context: https://stackoverflow.com/questions/31202318/org-xml-sax-saxparseexception-the-value-of-attribute-id-associated-with-an-el

I agree with you it's not written as well as it could be, but I'm also not sure I can do anything about it.

For what it's worth, we are also tracking https://issuetracker.google.com/119876558 which should hopefully help people fix this issue before they even get the compile error.

It makes me sad but I'm going to close this as infeasible. Feel free to ping with any addition thoughts, though.

Oh no! Really sorry to hear that. I wholeheartedly agree with the suggestions in that issue -- Lint warnings might be sufficient.

I have also flagged the incorrect documentation on developer.android.com -- the major reason why I think a whole bunch of people see this error.

I am in the process of filing another issue for you, so keep your eyes peeled! (Hopefully we can do something about that one)

Sounds good - thanks Zarah!