android context stack + notifications can lead to unintended paths #66

New Issue

Closed

opened 2021-06-28 21:54:19 +00:00 by dan · 0 comments

dan commented

2021-06-28 21:54:19 +00:00

Owner

if you're in a chat and then open new ones from notifications back takes you through all of them

it's a consequence of how we push contexts 
ideally we should probably switch to registering routes, and then going to an absolute loaded route, to prevent that 

if you're in a chat and then open new ones from notifications back takes you through all of them it's a consequence of how we push contexts  ideally we should probably switch to registering routes, and then going to an absolute loaded route, to prevent that 

dan added the

labels 2021-06-28 21:54:19 +00:00

dan added this to the Cwtch Beta 1.1 project 2021-06-28 21:54:19 +00:00

erinn referenced this issue

2021-07-02 23:31:26 +00:00

fix shutdown prompt when clicking notifications #90

erinn closed this issue

2021-07-03 00:12:15 +00:00

dan added the

label 2021-07-14 22:34:38 +00:00

Sign in to join this conversation.

No Label

blocked-on-external

component/bindings

component/connectivity

component/cwtch

component/tapir

cwtch-beta-1.10

cwtch-beta-1.11

cwtch-beta-1.12

cwtch-beta-1.13

cwtch-beta-1.5.x

need-replication-or-investigation

requires-more-effort-than-we-can-spare

waiting-on-fix-confirmation

waiting-on-new-flutter-feature

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/cwtch-ui#66

No description provided.