-
Notifications
You must be signed in to change notification settings - Fork 984
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
Error: Doesn't support name and white screen if open Wallet 1st time after opening transaction screen from Dapp #4876
Milestone
Comments
@goranjovic it is #4796 :( please take a look tomorrow ( |
goranjovic
added a commit
that referenced
this issue
Jun 21, 2018
…ded stricter check for chat wallet onboarding
jeluard
pushed a commit
that referenced
this issue
Jun 22, 2018
…ded stricter check for chat wallet onboarding Signed-off-by: Julien Eluard <[email protected]>
jeluard
pushed a commit
that referenced
this issue
Jun 22, 2018
…ded stricter check for chat wallet onboarding Signed-off-by: Julien Eluard <[email protected]>
mandrigin
pushed a commit
that referenced
this issue
Jun 25, 2018
Signed-off-by: Igor Mandrigin <[email protected]>
mandrigin
pushed a commit
that referenced
this issue
Jun 25, 2018
Signed-off-by: Igor Mandrigin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Type: Bug
Summary:
Error: Doesn't support name
is shown if user opens Wallet for the first time. If close error message then white screen is shown, so user needs to close app and launch again. If open Wallet after app re-launch then it works fine and shows Wallet screen.Such error happens if user opened some Send Transaction screen from any DApp (e.g use Sign feature in CryptoKitties) prior to opening Wallet. If user does not interact with Dapp then Wallet can be opened fine for the first time.
Expected behavior
No error shown, Wallet screen is opened
Actual behavior
If open wallet then error is shown:
Reproduction
from 00:22 https://app.testfairy.com/projects/4803622-status/builds/8501358/sessions/4394474390/?accessToken=/pX7AYEvRo5MHjOTpineB7jZWSU
Note: on the morning nightly build these issue can't be reproduced but can be reproduced on new nightly triggered in the evening June 20. Merges that were included in the new nightly https://jenkins.status.im/job/status-react/job/nightly/459/changes with this issue:
Additional Information
comment: # (Android or iOS.)
The text was updated successfully, but these errors were encountered: