You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
Describe the bug
Using the export private key option on mobile shows the wrong key; selecting to see the zaddy key shows you the taddy key and vice versa. The desktop version (windows at least) works as expected.
This seems like a simple mix-up in calling one key from the other.
To Reproduce
Select the receive button, select either the z or t address, select export private key
Expected behavior
The key that correlates to the desired address is shown instead of the other one.
Desktop (please complete the following information):
OS: Android 13
Browser
Version 1.8.8
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Using the export private key option on mobile shows the wrong key; selecting to see the zaddy key shows you the taddy key and vice versa. The desktop version (windows at least) works as expected.
This seems like a simple mix-up in calling one key from the other.
To Reproduce
Select the receive button, select either the z or t address, select export private key
Expected behavior
The key that correlates to the desired address is shown instead of the other one.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: