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

Owner token stuck on "Minting..." #14699

Closed
jrainville opened this issue May 10, 2024 · 1 comment · Fixed by #14884, status-im/status-go#5209, status-im/status-go#5249 or #14957
Closed

Owner token stuck on "Minting..." #14699

jrainville opened this issue May 10, 2024 · 1 comment · Fixed by #14884, status-im/status-go#5209, status-im/status-go#5249 or #14957
Assignees
Labels
backend-team bug Something isn't working E:Desktop Comm Perms and Minting MVP Misc tasks about Community permissions that are not part of another Epic, due for the MVP
Milestone

Comments

@jrainville
Copy link
Member

Bug Report

Description

Some tokens can get stuck in the "Minting..." state, and it can even be the Owner token. If that happens, it basically borks the community as you cannot try again.

We need to not only try to make sure if never happens, but also find a way to fix that state if it happened previously (retroactively fix those that were stuck previously).

Steps to reproduce

  1. Mint a token in a community
  2. Wait
  3. Maybe it gets stuck
    Restart 1 until it gets stuck

Expected behavior

Tokens get updated when the transaction is minted, or at least end up being updated with a decent delay

Actual behavior

tokens have a chance to get forever stuck in the Minting state

Additional Information

  • Status desktop version: 2.28.1
@jrainville jrainville added bug Something isn't working backend-team E:Desktop Comm Perms and Minting MVP Misc tasks about Community permissions that are not part of another Epic, due for the MVP labels May 10, 2024
@jrainville jrainville added this to the 2.28.1 Beta milestone May 10, 2024
@jrainville
Copy link
Member Author

After discussion, we think it's better to wait and see if the transaction refactor fixes the issue, as it should at least mitigate it.

So we'll wait for the 2.29 RC, test it and if needed, apply a fix on that one.

The reason is that if we were to do a fix only for 2.28.1, it would be on the old system, so we'd be duplicating work.

@jrainville jrainville modified the milestones: 2.28.1 Beta, 2.29.0 Beta May 13, 2024
endulab added a commit that referenced this issue May 22, 2024
endulab added a commit that referenced this issue May 22, 2024
endulab added a commit that referenced this issue May 28, 2024
endulab added a commit that referenced this issue May 28, 2024
endulab added a commit that referenced this issue May 28, 2024
endulab added a commit that referenced this issue May 28, 2024
endulab added a commit that referenced this issue May 28, 2024
endulab added a commit that referenced this issue May 28, 2024
@endulab endulab linked a pull request May 28, 2024 that will close this issue
jrainville pushed a commit that referenced this issue May 28, 2024
jrainville pushed a commit that referenced this issue May 28, 2024
jrainville pushed a commit that referenced this issue May 28, 2024
jrainville pushed a commit that referenced this issue May 28, 2024
jrainville pushed a commit that referenced this issue May 28, 2024
jrainville pushed a commit that referenced this issue May 28, 2024
* fix(@desktop/communities): add hidden button to refresh (retrack transaction) community tokens

Issue #14699

* chore(@desktop): upgrade status-go

Issue #14699
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment