-
Notifications
You must be signed in to change notification settings - Fork 2
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
Master Issue List #11
Comments
@ukane-philemon Thanks! Nice stuff! Will add these to cake-tech#986 : Will try to fix these in the current pr: Unsure if a problem: |
Thanks for yor input @JoeGruffins. I'm yet to test on ios. As for the last the last two issues you sited, I'm not sure if it's intended until the cake wallet team say something about them. |
New Issues:
The wallet becomes watch-only and users are not able to send from it. However, the send and exchange btns remains active and the user gets an error:
But the desc I used for the first and second tx were combined. Also, the tx note field is editable, it shouldn't be. Upstream issues I think:
|
Some of your new issues don't seem to be dcr specific. Will add the one about our qr code needing something useful to the TODOS |
I think the note field should be editable, its for user notes? |
That's an already concluded transaction. Besides, the note was from the sender, a receiver shouldn't be able to edit it. |
Yeah, I listed everything I could find, maybe the cake team would be interested in fixing them. I proly should create an upstream issue master list yeah? |
Adding another bug found by you.
After a restart:
|
Other Issues(so I don't forget to check back):
|
This is going to be a single list of issues discovered from Cake Wallet Testing. Issues added here that seem to be upstream related can be commented on and we can create an upstream issue. I'll upload this issue list from time to time.
Importing a wallet whose seed already exists works (for dcr and btc).
Clicking on the Scan Qr btn does nothing (on macos, proly upstream but I doubt if dcr wallet has support for this on mobile):
The text was updated successfully, but these errors were encountered: