We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It really does seem like there is a bug that is falsely indicating that users are low on R/Cs when they are not.
@jhonejhone just told me he received it but HiveBlock indicates https://hiveblocks.com/@jhonejhone
Enough credits for approximately: 45 comments 100+ votes 100+ transfers 100% recharged in 1 hour
It's hard to diagnose since I don't experience it.. I am using Hive Keychain on Desktop or Posting Key on Mobile Phone.
The text was updated successfully, but these errors were encountered:
When this happen we need a report from our user with screenshot or what they do so we can debug it, can he recall what he did?
Sorry, something went wrong.
If you look in the upper left had side, there is a time.. it was screenshotted at 14:35 today (Sunday, May 16) https://hiveblocks.com/@jhonejhone
He tried to make a post.
P.S. I will ask him for more information.
is this keychain or posting key?
Posting Key, since it's Mobile @stinkymonkeyph
Were you able to check the time of when he experienced this bug, and cross reference it with https://hiveblocks.com/@jhonejhone
To find out what triggered it? @stinkymonkeyph
stinkymonkeyph
No branches or pull requests
It really does seem like there is a bug that is falsely indicating that users are low on R/Cs when they are not.
@jhonejhone just told me he received it but HiveBlock indicates
https://hiveblocks.com/@jhonejhone
Enough credits for approximately:
45 comments
100+ votes
100+ transfers
100% recharged in 1 hour
It's hard to diagnose since I don't experience it.. I am using Hive Keychain on Desktop or Posting Key on Mobile Phone.
The text was updated successfully, but these errors were encountered: