Status Update
Comments
dl...@atlassian.com <dl...@atlassian.com> #2
Hello,
I'm only a little familiar with Power Apps. Is your app a mobile app or a web app?
This link
The primary
If your app does not work on Android mobile devices, you can also consider the
za...@google.com <za...@google.com> #3
dl...@atlassian.com <dl...@atlassian.com> #4
No, it is not supposed to take a raw value. The height
takes either a @DimenRes
(just realized I put DrawableRes
before which is incorrect) or Dp
if you look at the function signature, but this passes in a raw integer that doesn't map to a resource, so you end up with a crash and the stack trace that I shared. This ends up propagating to the system launcher and results in a potential crash loop like on the S22 that prevents user's from using the launcher and the phone for the most part. The only way to recover from this is install a new version of the app with a fixed widget and restart the phone.
dl...@atlassian.com <dl...@atlassian.com> #5
To be clear, this issue is the exception propagates outside the widget, potentially impacting the phone and the user's ability to use their phone (not just the widget) if the launcher doesn't gracefully handle the exception as exhibited by the Samsung S22. I understand the crash loop is likely occurring due to the app launchers not handling the exception properly, but considering the result could be catastrophic to user experience by preventing them from using the launcher, this is something that should be addressed by the Glance or widget team as it could negatively impact Android as a product if this was erroneously shipped into production by any app maker.
za...@google.com <za...@google.com> #6
Thanks for your detailed report. We have filed a bug on the launcher to track this issue.
We're also investigating whether resource existence can be tested in process in a practical way in the library too.
Description
Component used:
LazyColumn -> Image -> GlanceModifier.height
Version used:
1.0.0-alpha05
Devices/Android versions reproduced on:
Issue:
When building a Glance widget, I misconfigured a
GlanceModifer.height
parameter that ended up causing a crash in an infinite loop of the device's launcher making the tested Samsung phone unusable until I installed a fix and restarted the phone. Further testing had varying results dependent on device.The issue is caused by a widget misconfiguration, but should probably be handled within Glance rather than allowing the device's launcher to crash as this could potentially unresolvably impact a user's experience outside of the app/widget.
The issue seems to only manifest when the misconfiguration occurs in a
LazyColumn
item, but I haven't tested too many other configurations.Stacktrace:
Code sample:
Result of the issue seems to be different per manufacturer and OS version. Devices tested, all with default launchers: