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

Tapping on transaction submitted notification returns an Oops notification #1421

Closed
ibrahimtaveras00 opened this issue Mar 12, 2020 · 4 comments
Assignees
Labels
next up prioritized to be picked up next type-bug Something isn't working v1

Comments

@ibrahimtaveras00
Copy link
Contributor

ibrahimtaveras00 commented Mar 12, 2020

This does not happen to every single transaction, so it is inconsistent but I may have found a way to get it to happen more frequently:

  • either use your own request link or you can use mine (for Rinkeby)

Screen Shot 2020-03-09 at 3 01 36 PM

  • if using your own in the app, simply go to burger menu > Receive > Request > enter in your amount > and then tap QR code and scan it, or send yourself the link
  • in my example, upon scanning the QR code, I then get sent to the old send screen, where I continue
  • complete the transaction
  • now tap on the notification that says "Transaction submitted"
  • notice how it sends you to transaction history with an oops, something went wrong notification?

Screen Shot 2020-03-11 at 7 56 14 PM

Flow seen here = https://recordit.co/m4qJzlpA1Q

@ibrahimtaveras00 ibrahimtaveras00 added type-bug Something isn't working v1 labels Mar 12, 2020
This was linked to pull requests Mar 12, 2020
This was unlinked from pull requests Mar 12, 2020
@omnat
Copy link
Contributor

omnat commented Mar 18, 2020

I couldn't replicate this @ibrahimtaveras00
Tried your QR code and my own. Both worked. Is this error still happening for you?

@ibrahimtaveras00
Copy link
Contributor Author

Just tried again today and was able to reproduce it on the first try on the Google Pixel 3 XL

Seen here = https://recordit.co/Q8SrbBoEQ7

@omnat
Copy link
Contributor

omnat commented May 2, 2020

Hmm, just tried it again, and could replicate

@omnat omnat added the next up prioritized to be picked up next label May 2, 2020
@ibrahimtaveras00
Copy link
Contributor Author

I could no longer replicate this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next up prioritized to be picked up next type-bug Something isn't working v1
Projects
None yet
Development

No branches or pull requests

2 participants