> The crash no longer happens. But the edge-case of the fullscreen sim-unlock
> snap-decision needs to be handled in special way. Since there's no UX-design
> for this, I will suppress it if there are already snap-decisions in queue or
> avoid new snap-decisions getting displayed, if there's still a fullscreen
> snap-decision displayed. That has to happen on the backend though.
Not sure I understand correctly, what do you mean with suppressing it? Does that mean delaying it or dropping it? I'm not sure we should just drop it while I guess I'm fine with delaying it until the other notifications have been handled.
> The crash no longer happens. But the edge-case of the fullscreen sim-unlock
> snap-decision needs to be handled in special way. Since there's no UX-design
> for this, I will suppress it if there are already snap-decisions in queue or
> avoid new snap-decisions getting displayed, if there's still a fullscreen
> snap-decision displayed. That has to happen on the backend though.
Not sure I understand correctly, what do you mean with suppressing it? Does that mean delaying it or dropping it? I'm not sure we should just drop it while I guess I'm fine with delaying it until the other notifications have been handled.