-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issues of show the migrate ckb data dialog testing #301
Comments
Because users have canceled the migrate, after users reopen Neuron, it will show the migrate dialog again.
It's an exception with development operations.
It has told you that the ckb node data has locked, so migration failed, you need to delete the lock file and try to migrate again. |
1.To No.1 issue I have reopened neuron again,but it not show. |
This situation will not occur during normal operation, and the data also needs to migrate even if the users have not created a wallet.
There may exist unknown conditions to cause migration failure, and this is one of the conditions, we can tell users how to do when the exception happens. But we can not know which the exception will come. |
reopen-neuron.movFrom this video, we know that the migrate dialog will show after restarting the Neuron. Neuron was downloaded from https://github.com/nervosnetwork/neuron/actions/runs/6527826934. |
I have deleted the lock file and local storage again ,then I reopen the app,it does not show the migrate dialog,this is the log. |
From the log, it shows that your 8114 port has been used, could you check your 8114 port? |
1.It costs several minitues to show migrate window again after I click cancel or X button in migrate pop up window.It is hard to see this migrate window.
2023-10-16.15.42.49.mov
2.After I clear Users/${username}/Library/Application Support/Neuron/Local Storage,when I click the app,it requires to create a new wallet,then the migrate pop up window show up in create wallet window.
3.When I click migrate button ,it pop up an error window.
The text was updated successfully, but these errors were encountered: