Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect to Chats main view happens after QR code scan on 'Add bootnode' or 'Add mailserver' screen #8044

Closed
Serhy opened this issue Apr 25, 2019 · 4 comments · Fixed by #8048

Comments

@Serhy
Copy link
Contributor

Serhy commented Apr 25, 2019

Type: Bug

Summary: There is the same bug when contact scans QR code on the Add bootnode and Add mailserver screens: contact redirected from Add bootnode / Add mailserver screens.

On iOS its redirect to blank screen.
On Android there is a redirect to Chats/Dapps/Wallet/Profile screens (it depends, apparently, which tab was active prior navigation)

It's noticeable (on Android) that QR code value has read and inserted in editbox, - but then it always follows by redirect

Expected behavior

Contact keep staying on the same screen after QR code got scanned at 'Add bootnode' / 'Add mailserver' screens

Actual behavior

Contact redirected from respective screen after QR code got scanned at 'Add bootnode' / 'Add mailserver' screens

1111

Reproduction 1

  • Open Status and create new account
  • Profile -> Bootnodes ->+ -> tap Scan QR code -> scan valid QR code

Reproduction 2

  • Open Status and create new account
  • Profile -> Mailserver ->+ -> tap Scan QR code -> scan valid QR code

Additional Information

  • Status version: Develop, Release 0.12.0
  • Operating System: Android and iOS
@rachelhamlin
Copy link
Contributor

@jeluard do you mind taking a look at it while we firm up designs for onboarding?

@jeluard
Copy link
Contributor

jeluard commented Apr 26, 2019

@rachelhamlin Sure!

@jeluard
Copy link
Contributor

jeluard commented Apr 26, 2019

@Serhy Please give #8044 a try. It will help us pinpoint the issue.

@Serhy
Copy link
Contributor Author

Serhy commented Apr 26, 2019

@Serhy Please give #8044 a try. It will help us pinpoint the issue.

#8048 -> fixes current #8044 and #7995 issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants