Status Update
Comments
yo...@gmail.com <yo...@gmail.com> #2
Speeds up sometimes (see the timestamps):
5:29:15.858 E Invalid resource ID 0x00000002.
15:29:15.859 E Invalid resource ID 0x00000003.
15:29:15.859 E Invalid resource ID 0x00000001.
15:29:15.859 E Invalid resource ID 0x00000004.
15:29:15.859 E Invalid resource ID 0x00000005.
15:29:15.903 E Invalid resource ID 0x00000002.
15:29:15.903 E Invalid resource ID 0x00000003.
15:29:15.903 E Invalid resource ID 0x00000001.
15:29:15.903 E Invalid resource ID 0x00000004.
15:29:15.903 E Invalid resource ID 0x00000005.
15:29:15.926 E Invalid resource ID 0x00000002.
15:29:15.926 E Invalid resource ID 0x00000003.
15:29:15.926 E Invalid resource ID 0x00000001.
15:29:15.926 E Invalid resource ID 0x00000004.
15:29:15.926 E Invalid resource ID 0x00000005.
15:29:15.960 E Invalid resource ID 0x00000002.
15:29:15.960 E Invalid resource ID 0x00000003.
15:29:15.960 E Invalid resource ID 0x00000001.
15:29:15.960 E Invalid resource ID 0x00000004.
15:29:15.960 E Invalid resource ID 0x00000005.
15:29:15.994 E Invalid resource ID 0x00000002.
15:29:15.994 E Invalid resource ID 0x00000003.
15:29:15.994 E Invalid resource ID 0x00000001.
15:29:15.994 E Invalid resource ID 0x00000004.
15:29:15.994 E Invalid resource ID 0x00000005.
15:29:16.025 E Invalid resource ID 0x00000002.
15:29:16.025 E Invalid resource ID 0x00000003.
15:29:16.025 E Invalid resource ID 0x00000001.
15:29:16.025 E Invalid resource ID 0x00000004.
15:29:16.025 E Invalid resource ID 0x00000005.
15:29:16.059 E Invalid resource ID 0x00000002.
15:29:16.059 E Invalid resource ID 0x00000003.
15:29:16.060 E Invalid resource ID 0x00000001.
15:29:16.060 E Invalid resource ID 0x00000004.
15:29:16.060 E Invalid resource ID 0x00000005.
15:29:16.093 E Invalid resource ID 0x00000002.
15:29:16.093 E Invalid resource ID 0x00000003.
15:29:16.093 E Invalid resource ID 0x00000001.
15:29:16.093 E Invalid resource ID 0x00000004.
15:29:16.093 E Invalid resource ID 0x00000005.
15:29:16.137 E Invalid resource ID 0x00000002.
15:29:16.137 E Invalid resource ID 0x00000003.
15:29:16.137 E Invalid resource ID 0x00000001.
15:29:16.137 E Invalid resource ID 0x00000004.
15:29:16.139 E Invalid resource ID 0x00000005.
15:29:16.159 E Invalid resource ID 0x00000002.
15:29:16.159 E Invalid resource ID 0x00000003.
15:29:16.159 E Invalid resource ID 0x00000001.
15:29:16.159 E Invalid resource ID 0x00000004.
15:29:16.159 E Invalid resource ID 0x00000005.
15:29:16.192 E Invalid resource ID 0x00000002.
15:29:16.192 E Invalid resource ID 0x00000003.
15:29:16.192 E Invalid resource ID 0x00000001.
15:29:16.192 E Invalid resource ID 0x00000004.
15:29:16.192 E Invalid resource ID 0x00000005.
15:29:16.225 E Invalid resource ID 0x00000002.
15:29:16.225 E Invalid resource ID 0x00000003.
15:29:16.225 E Invalid resource ID 0x00000001.
15:29:16.225 E Invalid resource ID 0x00000004.
15:29:16.225 E Invalid resource ID 0x00000005.
15:29:16.258 E Invalid resource ID 0x00000002.
15:29:16.258 E Invalid resource ID 0x00000003.
15:29:16.258 E Invalid resource ID 0x00000001.
15:29:16.258 E Invalid resource ID 0x00000004.
15:29:16.258 E Invalid resource ID 0x00000005.
15:29:16.293 E Invalid resource ID 0x00000002.
15:29:16.293 E Invalid resource ID 0x00000003.
15:29:16.293 E Invalid resource ID 0x00000001.
15:29:16.293 E Invalid resource ID 0x00000004.
15:29:16.293 E Invalid resource ID 0x00000005.
15:29:16.325 E Invalid resource ID 0x00000002.
15:29:16.325 E Invalid resource ID 0x00000003.
15:29:16.326 E Invalid resource ID 0x00000001.
15:29:16.326 E Invalid resource ID 0x00000004.
15:29:16.326 E Invalid resource ID 0x00000005.
15:29:16.366 E Invalid resource ID 0x00000002.
15:29:16.366 E Invalid resource ID 0x00000003.
15:29:16.367 E Invalid resource ID 0x00000001.
15:29:16.367 E Invalid resource ID 0x00000004.
15:29:16.367 E Invalid resource ID 0x00000005.
15:29:16.375 E Invalid resource ID 0x00000002.
15:29:16.375 E Invalid resource ID 0x00000003.
15:29:16.375 E Invalid resource ID 0x00000001.
15:29:16.375 E Invalid resource ID 0x00000004.
15:29:16.375 E Invalid resource ID 0x00000005.
15:29:16.409 E Invalid resource ID 0x00000002.
15:29:16.409 E Invalid resource ID 0x00000003.
15:29:16.409 E Invalid resource ID 0x00000001.
15:29:16.410 E Invalid resource ID 0x00000004.
15:29:16.410 E Invalid resource ID 0x00000005.
15:29:16.442 E Invalid resource ID 0x00000002.
15:29:16.442 E Invalid resource ID 0x00000003.
15:29:16.442 E Invalid resource ID 0x00000001.
15:29:16.442 E Invalid resource ID 0x00000004.
15:29:16.443 E Invalid resource ID 0x00000005.
15:29:16.480 E Invalid resource ID 0x00000002.
15:29:16.480 E Invalid resource ID 0x00000003.
15:29:16.480 E Invalid resource ID 0x00000001.
15:29:16.481 E Invalid resource ID 0x00000004.
15:29:16.481 E Invalid resource ID 0x00000005.
15:29:16.492 E Invalid resource ID 0x00000002.
15:29:16.493 E Invalid resource ID 0x00000003.
15:29:16.493 E Invalid resource ID 0x00000001.
15:29:16.493 E Invalid resource ID 0x00000004.
15:29:16.493 E Invalid resource ID 0x00000005.
15:29:16.526 E Invalid resource ID 0x00000002.
15:29:16.526 E Invalid resource ID 0x00000003.
15:29:16.526 E Invalid resource ID 0x00000001.
15:29:16.526 E Invalid resource ID 0x00000004.
15:29:16.526 E Invalid resource ID 0x00000005.
15:29:16.559 E Invalid resource ID 0x00000002.
15:29:16.559 E Invalid resource ID 0x00000003.
15:29:16.559 E Invalid resource ID 0x00000001.
15:29:16.559 E Invalid resource ID 0x00000004.
15:29:16.559 E Invalid resource ID 0x00000005.
15:29:16.593 E Invalid resource ID 0x00000002.
15:29:16.593 E Invalid resource ID 0x00000003.
15:29:16.593 E Invalid resource ID 0x00000001.
15:29:16.593 E Invalid resource ID 0x00000004.
15:29:16.594 E Invalid resource ID 0x00000005.
15:29:16.608 E Invalid resource ID 0x00000002.
15:29:16.608 E Invalid resource ID 0x00000003.
15:29:16.609 E Invalid resource ID 0x00000001.
15:29:16.609 E Invalid resource ID 0x00000004.
15:29:16.609 E Invalid resource ID 0x00000005.
15:29:16.642 E Invalid resource ID 0x00000002.
15:29:16.642 E Invalid resource ID 0x00000003.
15:29:16.642 E Invalid resource ID 0x00000001.
15:29:16.642 E Invalid resource ID 0x00000004.
al...@google.com <al...@google.com>
gm...@google.com <gm...@google.com>
ps...@google.com <ps...@google.com> #3
Hi, it would be helpful it you could provide more information.
- When does this happen?
- How can we replicate it?
- Can you attach logs (idea.log and logcat)
- Is this a compose project?
As for your question: yes, Layout Inspector works by injecting code into the app being inspected.
yo...@gmail.com <yo...@gmail.com> #4
Yes, the app uses Compose.
This seems to happen when I run the app and then open the embedded layout inspector.
The logcat is just full of the logs seen above repeated over and over.
ps...@google.com <ps...@google.com> #5
Could you provide idea.log when the issue happens?
Would it be possible to share the project you're working on? If not, could you attach a video so we can see exactly what's going on?
jl...@google.com <jl...@google.com> #6
It looks like the logging comes from the framework:
The device must be using API 34 ?
I tried to add a few string resources to a small compose demo app. I got one message like this without opening the Layout Inspector:
E Invalid resource ID 0x00000000.
And when I opened the Layout Inspector I got 4 more output lines and then it stopped - even when interacting with the app and the Layout Inspector.
To me that is acceptable.
If you are unable to share your app: can you think of what kind of resources the app is using ?
yo...@gmail.com <yo...@gmail.com> #7
I can't share the whole app code, but I could probably do a screen share session if you want (you can email me).
There are lots of resources in the app, like any non-trivial app.
This happens when I am interactively using the Layout Inspector.
jl...@google.com <jl...@google.com> #8
Is your app a mixture of views and compose or a 100% compose app ?
If it is a mixture: are the messages more frequent when clicking on compose nodes or views in the component tree.
jl...@google.com <jl...@google.com> #9
Looking at the code:
The compose inspector does not deal with resource ids (directly) but the view inspector does.
So I think the messages are from getting attributes of views.
In that case: we should be able avoid the logcat entries.
It is also possible that some of the resource ids indeed are invalid in your app.
I believe you can see that by inspecting the generated R file.
There should be indicators if the an id is invalid.
jl...@google.com <jl...@google.com>
jl...@google.com <jl...@google.com> #10
The fix is expected to be included with Android Studio Iguana canary 9.
an...@google.com <an...@google.com> #11
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Iguana | 2023.2.1 Canary 11
- Android Gradle Plugin 8.3.0-alpha11
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
Embedded Layout inspector spams logcat with
Invalid resource ID
errors:Looks like there is something on a half second loop printing these 5 lines over and over and over:
Is layout inspector injecting code into my app process?