-
Notifications
You must be signed in to change notification settings - Fork 35
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
fix "not a subscriber" diagnostic to reflect the actual error... #823
Comments
@srirambv - i think that this is a different bug, specifically that sometimes the browser seems to lose track of the fact that a user is a subscriber. i occasionally see the same error when I do select POAPs or NFTs. i've changed the title to reflect this. if you disagree, please let me know so we can drill down a bit. |
update: it looks like Sri called it right, so there are a couple of things we can debug here! |
The actual error is being hidden by that message. I can see from this interaction that the correct subscription cookies were set, the subscription server returned the error:
But chose to display the message "Sorry, you are not a subscriber", presumably as a catch-all error message. |
so, two things: first, instead of "Sorry, you are not a subscriber" we should display second, do we know why the subscription service says it's unable to verify? |
hmmm... OK, let me see what kind of errors i see. cf., #850 |
This is fixed now. I see the error 823.mp4@johnhalbert @mrose17 with selecting just moderator POAP/NFT the call room gets created. Should the message read to either select the required POAP/NFT or moderator POAP/NFT ? |
Cf., #850 in other words, a room is not required… |
Description
Show proper message when a user doesn't select any POAP/NFT when creating a Web3 Talk room
Steps
Start Web3 call
Sorry, you are not a subscriber
message instead of showing the actual reasonActual Result
Wrong.Error.Message.mp4
Expected Result
Should show the actual reason for not creating the room
Additional Information
cc: @mrose17
The text was updated successfully, but these errors were encountered: