Fixed
Status Update
No update yet.
Comments
ni...@google.com
Fixed in ConstraintLayout 2.0.0-alpha2. We'll also need to update the navigation library to use a less vague attribute.
du...@gmail.com
Thanks!
il...@google.com
wk...@google.com
wk...@google.com
il...@google.com
We've changed app:type to app:argType to avoid the conflict. This will be available in Navigation 1.0.0-alpha04
lo...@gmail.com
Either I'm doing something wrong with version 1.0.0-alpha04 or something is broken. After updating the gradle file and replacing app:type with app:argType it seems that all arguments in the generated classes are strings. In picture 1 (see attachments) I'm declaring an activity with requires an non-nollable integer. In picture 2 there's the declaration for a fragments with has an action to show the activity from picture 1. As you can see in picture 3, the generated argument type is string and not interger.
Am I missing something or is it a bug?
Am I missing something or is it a bug?
wk...@google.com
did you update your safe args plugin classpath to alpha04 as well or just the runtime navigation library dependency?
lo...@gmail.com
It's always the little things... Thanks a lot for the hint, now it's working! :)
Description
Navigation version: 1.0.0-alpha2
I recently added the new CL2 to my project alongside the Navigation library, where I have 2 navigation xml files that contain argument objects for some fragments.
The error I receive (there are multiple as there are multiple arguments) is:
> Android resource linking failed
error: 'integer' is incompatible with attribute type (attr) enum [deltaRelative=0, parentRelative=2, pathRelative=1] [weak].
error: 'string' is incompatible with attribute type (attr) enum [deltaRelative=0, parentRelative=2, pathRelative=1] [weak].