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
Lss-Ankit opened this issue
Oct 9, 2019
· 2 comments
Labels
bugSomething isn't workingPriority: P4Lowqaquick-fixThings that should be quick fixes- Good for first issues & ramping uptriagedlabel for issues that have been assigned a prioritywallet
App version: App store v1.4.2, Celo staging v1.4.2, Play store v1.5.0 Repro on: Samsung Galaxy Note9 (8.1.0), Google Pixel 2 XL (9.0) Priority: Low Test Account: 3158095552/BackupKey
Repro Steps:
Launch the app.
Make sure user is on ‘Choose Language’ page.
Tap device back button to close the app.
Relaunch the app.
Observe
Investigation:
Every time the restart App option is shown when the user closing the app by device back button.
Issue does not repro when user relaunched the app after killing it
Issue is not reproed if the app is opened after it is backgrounded using the device home button.
Impact: Bad user experience Current Behavior: Current Behavior: Celo Logo is not shown and app is not launched after some time it shows the “Restart App” button. Expected Behavior: Celo logo should shown and Restart App button should instantly
bugSomething isn't workingPriority: P4Lowqaquick-fixThings that should be quick fixes- Good for first issues & ramping uptriagedlabel for issues that have been assigned a prioritywallet
App version: App store v1.4.2, Celo staging v1.4.2, Play store v1.5.0
Repro on: Samsung Galaxy Note9 (8.1.0), Google Pixel 2 XL (9.0)
Priority: Low
Test Account: 3158095552/BackupKey
Repro Steps:
Investigation:
Impact: Bad user experience
Current Behavior: Current Behavior: Celo Logo is not shown and app is not launched after some time it shows the “Restart App” button.
Expected Behavior: Celo logo should shown and Restart App button should instantly
Attachment: Android_AppLogoIsnotShown.mp4 (Bug Observed at 05 secs)
The text was updated successfully, but these errors were encountered: