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

Collection.watch() not returning generated response #5858

Closed
SipNWork opened this issue May 30, 2023 · 8 comments
Closed

Collection.watch() not returning generated response #5858

SipNWork opened this issue May 30, 2023 · 8 comments
Labels
Encryption:Off Frequency:Always Needs-Attention Reporter has responded. Review comment. O-Community Repro:Always Reproduction-Required T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed

Comments

@SipNWork
Copy link

SipNWork commented May 30, 2023

How frequently does the bug occur?

Always

Description

Collection.watch invoked to get realtime updates from specific collection, but not getting triggered even when logs showing Ok on app services.

React-native configurations

"react": "18.2.0",
"react-native": "0.71.8",
"@realm/react": "^0.4.3",
"realm": "11.9.0",

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

No response

Version

0.4.3

What services are you using?

Atlas App Services: Functions or GraphQL or DataAPI etc

Are you using encryption?

No

Platform OS and version(s)

MAC os

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

@SipNWork SipNWork added the T-Bug label May 30, 2023
@SipNWork SipNWork changed the title Collection.watch() not not returning generated response Collection.watch() not returning generated response May 30, 2023
@takameyer
Copy link
Contributor

@SipNWork Have you set up any polyfills, such as react-native-polyfill-globals? These are necessary in order to use watch. You can find more info in our documentation

@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label May 30, 2023
@SipNWork
Copy link
Author

our documentation

Yes, Added all three in my app.js file.

@github-actions github-actions bot added Needs-Attention Reporter has responded. Review comment. and removed Waiting-For-Reporter Waiting for more information from the reporter before we can proceed labels May 30, 2023
@takameyer
Copy link
Contributor

@SipNWork There is an issue with fetch on Android that may be causing this. Are you seeing this problem on iOS as well?

@sync-by-unito sync-by-unito bot added Waiting-For-Reporter Waiting for more information from the reporter before we can proceed and removed Needs-Attention Reporter has responded. Review comment. labels Jun 1, 2023
@SipNWork
Copy link
Author

SipNWork commented Jun 2, 2023

@SipNWork There is an issue with fetch on Android that may be causing this. Are you seeing this problem on iOS as well?

Yes, I am facing this on IOS.

@github-actions github-actions bot added Needs-Attention Reporter has responded. Review comment. and removed Waiting-For-Reporter Waiting for more information from the reporter before we can proceed labels Jun 2, 2023
@takameyer
Copy link
Contributor

@SipNWork We have this covered in our integration tests and it is passing. Can you possibly create a sample repo to reproduce this issue? Then we can help further to diagnose the problem.

@sync-by-unito sync-by-unito bot added Reproduction-Required Waiting-For-Reporter Waiting for more information from the reporter before we can proceed and removed Needs-Attention Reporter has responded. Review comment. labels Jun 5, 2023
@sync-by-unito sync-by-unito bot closed this as completed Jun 27, 2023
@sync-by-unito
Copy link

sync-by-unito bot commented Jun 27, 2023

➤ takameyer commented:

Closed as the issue has become stale. Please open again if you can provide a reproduction.

@SipNWork
Copy link
Author

const reply = await new DefaultNetworkTransport().fetch(request)

File - mongo-client.js , line no - 216
relative path - node_modules/realm/lib/mongo-client.js

Fetch never resolves any response. I checked the logs in mongodb console and request was successful.

Configurations
"react": "18.2.0",
"react-native": "0.71.8",
"realm": "11.9.0",

@github-actions github-actions bot added Needs-Attention Reporter has responded. Review comment. and removed Waiting-For-Reporter Waiting for more information from the reporter before we can proceed labels Jul 19, 2023
@SipNWork
Copy link
Author

@SipNWork We have this covered in our integration tests and it is passing. Can you possibly create a sample repo to reproduce this issue? Then we can help further to diagnose the problem.

Would be helpful if you could connect with me on Gmeet or Zoom to resolve this issue. Our release is blocked due to this issue.

@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label Jul 28, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Encryption:Off Frequency:Always Needs-Attention Reporter has responded. Review comment. O-Community Repro:Always Reproduction-Required T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed
Projects
None yet
Development

No branches or pull requests

2 participants