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
Appsync filter subscriptions does not work!!! #2521
Comments
Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂. |
Hey thanks, for transferring. Please help I don't know if I'm doing something wrong, or it is a bug? I'm now stuck in my project because of this... |
So I followed this video with no filters and even this is not working. subscription MySubscription { This is my model: Please prioritize this issue. |
Okay the issue is, when I logged in, in both tabs with the same user_pool user then it works. But if I do it with different one. So that one user create the ask and the another user listen to that, it does not work. Is this the right behaviour in AppSync? Because in my App it should work. That if any user is creating an ask and some user listener to that, should get notified. |
Hi @juri-diener, Thank you for the additional details. I have a follow-up question: I notice that your subscription filter using a single |
@AnilMaktala Yes, they have the same OrgID. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v21.7.3
Amplify CLI Version
11.0.5
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
If I run the subscription with the filter. I don't receive the item. If I remove on the subscription the filter, I get the object if an Ask is created.
Expected behavior
Should work when filtering on subscription.
Reproduction steps
Like the image above.
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: