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

🐛 [BUG] - <Unable to accept request, when got invited for Push chat> #1350

Closed
pranshurastogi opened this issue Dec 20, 2023 · 1 comment · Fixed by push-protocol/push-sdk#941
Assignees
Labels
bug Something isn't working

Comments

@pranshurastogi
Copy link
Member

Expected Behaviour

  • After accepting the intent of the request, address should be a part of group
  • While creating the conditional gating group, when we click on button it should stop other process or show loader.

Current Behaviour

  • Request Intent is not getting accepted 'Failed to load resource: the server responded with a status of 403 (Forbidden)'
  • While clicking on create group button, it creates 6-7 group. All of them have a different chat id.
  • Also, sometimes when request is sent to invite in the group, it does not reflects on other end.

Reproduction steps

1. Go to 'app.push.org'
2. Click on 'chat'
3. Create a conditional gated group with invite conditions
4. Try to send an invite and accept it.
5. Also, while creating group it should stop all other process until unless, group is created.

Screenshots

https://bafkreidr3omwohcmvtkqwz3vgls4wqepaxbnth2mnhkhvvj47mmubecpm4.ipfs.nftstorage.link/

Relevant Logs

No response

Dapp Env

Prod (app.push.org)

Browsers

Chrome

@Aman035
Copy link
Member

Aman035 commented Dec 21, 2023

For the 1st issue - Request Intent is not getting accepted 'Failed to load resource: the server responded with a status of 403 (Forbidden)'
It is resolved by fix: invite condition #1398

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants