You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the app gets into a state where a contact is removed / no longer exists but the user still has a proof request from said contact, the proof can no longer be declined, it just triggers an error and exists somewhat permanently in the notification list on the home screen. Haven't found a reproducible way to get into such a state but I can confirm it's possible.
Expected behavior
@knguyenBC should the user be able to delete contacts who have active proof requests? If such a contact is deleted, should all their associated proofs be deleted as well? Should proofs that are orphaned like this not show up in notifications?
Steps to reproduce
Screenshots and/or log output
Environment
Occurs on Android
Occurs on iOS
Build #: local, latest main on Jan 17
Android Device Model:
iOS Device Model:
Workaround
Severity
High
Medium
Low
The text was updated successfully, but these errors were encountered:
Description of problem
If the app gets into a state where a contact is removed / no longer exists but the user still has a proof request from said contact, the proof can no longer be declined, it just triggers an error and exists somewhat permanently in the notification list on the home screen. Haven't found a reproducible way to get into such a state but I can confirm it's possible.
Expected behavior
@knguyenBC should the user be able to delete contacts who have active proof requests? If such a contact is deleted, should all their associated proofs be deleted as well? Should proofs that are orphaned like this not show up in notifications?
Steps to reproduce
Screenshots and/or log output
Environment
Build #: local, latest main on Jan 17
Android Device Model:
iOS Device Model:
Workaround
Severity
The text was updated successfully, but these errors were encountered: