Fixed
Status Update
Comments
be...@citymapper.com <be...@citymapper.com> #2
Actually, the second part of that (@font/some_other_font not being resolved) doesn't seem to be the case after re-opening the project. The main issue (@app_font not being resolved by the IDE in layout files despite working correctly at build/run time) is still there however
rm...@google.com <rm...@google.com> #3
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
xa...@google.com <xa...@google.com>
rp...@google.com <rp...@google.com> #4
(Adding to 3.5 hotlist in case this is a regression)
be...@google.com <be...@google.com> #5
This is not a regression, our XML stack doesn't handle "non-values" resource types well in res/values files. We'll have to rework it as soon as possible to fix this.
be...@google.com <be...@google.com>
lu...@google.com <lu...@google.com> #6
Thanks for the bug, this has been fixed in Android Studio 4.1 onwards. If you still experience any issues with font references, reply to this bug or open a new one!
Description
i.e.
<resources>
<item name="app_font" type="font">@font/some_other_font</item>
<resources>
Additionally in the above statement @font/some_other_font also cannot be resolved in the IDE, despite the font existing and the project building successfully.
Seen in AS 3.5 Canary 5
I've attached a small repro project (see layout/activity_main.xml and values/fonts.xml)