Assigned
Status Update
Comments
ad...@google.com <ad...@google.com> #2
I see same issue and have been debugging it.
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
Description
Hello Android Team,
I am encountering a scenario similar to the one detailed in the Google Issue 396612325 .
In Continuous Glucose Monitoring (CGM) apps, it's vital for patients to receive alerts, especially when their glucose levels are critically low. These alerts are crucial for patient safety.
With the introduction of Android 15:
When the
setInterruptionFilter
is configured toINTERRUPTION_FILTER_NONE
, patients will miss these critical alerts.Is there a method to ensure the delivery of critical alerts in Android 15? Alternatively, can this capability be included in Android 16?