Status Update
No update yet.
Comments
ad...@google.com
ad...@google.com
po...@microsoft.com
We are also running into a similar problem in a sharded instrumented test. The app doesn't actually crash but the test fails and there is some unexpected white space showing in our emulator. (See attachment)
to...@gmail.com
Re *"Numerous people have updated the external bug saying that it sometimes causes apps to crash."*
Actually, people have reported that using 28 tools on 27 emulator, they always get this message, and they occasionally get app crashes. Without further info, all this tells the developers is that there is some issue "using 28 tools on 27 emulator" - the message itself is reporting something that developers have stated is not the *cause* of the occasional crashes, as the message happens regardless of whether the app crashes or not.
Therefore, the only possible way to proceed is for someone to create a *simple* test case that occasionally crashes under this scenario.
But here's the irony: such a simple test case would reveal some bug that could then be fixed. And presumably then will be fixed. Yet this message will still be there, waiting for the next person to come along and mistakenly believe it is related to their crash...
Actually, people have reported that using 28 tools on 27 emulator, they always get this message, and they occasionally get app crashes. Without further info, all this tells the developers is that there is some issue "using 28 tools on 27 emulator" - the message itself is reporting something that developers have stated is not the *cause* of the occasional crashes, as the message happens regardless of whether the app crashes or not.
Therefore, the only possible way to proceed is for someone to create a *simple* test case that occasionally crashes under this scenario.
But here's the irony: such a simple test case would reveal some bug that could then be fixed. And presumably then will be fixed. Yet this message will still be there, waiting for the next person to come along and mistakenly believe it is related to their crash...
Description
This bug is randomly CRASHING APPS.
The internal version of this bug was closed as "working as intended / won't fix" due to (apparently) an assumption that it only caused log spam. And the public bug (listed above) was closed as a duplicate.
However that assumption is wrong. Numerous people have updated the external bug saying that it sometimes causes apps to crash. That has happened to me also. Unfortunately no one has been able to reliably reproduce the crash.
I see people have tried to create new bugs about this to bring attention to it, but the issue tracker gate-keepers just keep closing them as duplicates or (not enough info provided to reproduce).
Please just reopen the original bugs until the issue can finally be resolved.