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

foreground redeem self created token #170

Closed
KKA11010 opened this issue Sep 8, 2023 · 1 comment · Fixed by #201
Closed

foreground redeem self created token #170

KKA11010 opened this issue Sep 8, 2023 · 1 comment · Fixed by #201
Assignees
Labels
UX User experience related

Comments

@KKA11010
Copy link
Collaborator

KKA11010 commented Sep 8, 2023

"Loving the app so far. One thing I noticed in case it hasn’t been brought up before. The app doesn’t seem to recognize when the token you have on your clipboard is one you created and intent to send to someone vs a token you received from someone so people might redeem their own token as I did the first time I used the app"

The app asks to redeem a token that has been created by the user itself, that makes no sense.

@KKA11010 KKA11010 self-assigned this Sep 8, 2023
@swedishfrenchpress
Copy link
Collaborator

I've been investigating this and encountered the same error. The issue appears inconsistent; I noticed the notification reappeared after just a few minutes of inactivity. For a better user experience, I suggest always hiding this notification if the token is user-generated.
IMG_7597

@KKA11010 KKA11010 added the UX User experience related label Sep 10, 2023
@KKA11010 KKA11010 changed the title redeem token in clipboard foreground redeem self created token Sep 10, 2023
KKA11010 added a commit that referenced this issue Sep 10, 2023
KKA11010 added a commit that referenced this issue Sep 13, 2023
* add a share function helper

* Fixes #170
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX User experience related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants