Open ber4444 opened 3 years ago
Can you provide more info on this? What actions were you doing when you encountered this, what Android version were you using, and what device was this on? @ber4444
In the past, we had the same exception. In our environment, when this happens, by doing a clean build and install app again to solved.
In our study, this exception may not by Hyperion.
The cause is unknown, the Resource IDs into resource XML may not be updated when building the app.
Referenced Resource ID in resource XML are expanded to inline resource ID at app building. (ex. @+id/foo
to @ref/0x7f090103
)
And when that happens, cause issue's exception on runtime. However, Hyperion is the first to reference any resource ID at runtime, so occur this issue's problem. This is a coincidence. if the resource ID is not updated, the resource string may be different at runtime.
We couldn't fix this problem. but we no longer see occur it. so that's why we stopped looking into this. that all the information we can given.
same thing happening to me
@Toubap Have you got any more information about what actions were you doing when you encountered this, what Android version were you using, and what device was this on?
tambem aconteceu comigo