-
Notifications
You must be signed in to change notification settings - Fork 4k
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
🐛 [cloud_firestore] iOS: Rework is incompatible with multi-isolate Apps #4108
Comments
A alternative solution would be to use That way you'd not need to keep a @Salakar WDYT |
That could work also. If you're willing I'm open to receiving a PR to help speed this along quicker |
any solution? https://stackoverflow.com/questions/65032058/how-do-i-register-firestore-callback-in-ios @ened How do you fix this isse? |
@bhanuka96 from the SO description, the PR could help you. Try adding this to pubspec.yaml: dependency_overrides:
cloud_firestore:
git:
url: https://github.com/ened/flutterfire.git
ref: fix/4108-cloud-firestore
path: packages/cloud_firestore/cloud_firestore
cloud_firestore_platform_interface:
git:
url: https://github.com/ened/flutterfire.git
ref: fix/4108-cloud-firestore
path: packages/cloud_firestore/cloud_firestore_platform_interface Then do a `flutter clean && flutter pub get`` - then build your iOS App again and try. |
@ened Thanks. no luck, |
@bhanuka96 you will need to use both.. |
@ened I cannot get package.
|
@bhanuka96 Did you add it to |
@ened
|
Bug report
Our iOS App runs the FG isolate (Flutter main application as usual) plus 1, sometimes 2, long-lived isolates in the background.
Upon registering the Firestore plugin for the second instance, the first instance's Dart side will loose connectivity to the native side, causing Snapshot listeners functionality to stop.
We need Firestore to work in both isolates, as one of them revolves about listening to document changes for user requested actions and the other one is pertinent to the background functionality of our App.
Steps to reproduce
Steps to reproduce the behavior:
You will need two isolates, to test this behavior.
You can try this using
flutter_workmanager
orflutter_uploader
.Attempt to listen to a document
snapshots
stream on both references, you will find that one of them can receive contents.Expected behavior
Both isolates will subscribe to the value and receive it equally well.
Additional context
The issue seems to stem from how the plugin is instantiated on iOS, in the registerPluginsMethod:
Pay close attention to the line
instance.channel = channel
. This is correct, however - because instance is a singleton object shared among the Apps isolates (retrieved via[FLTFirebaseFirestorePlugin sharedInstance]
), one isolate instantiation and the plugin initialization of will override the previous one.I'm omitting doctor / pub output as this should be a code level issue.
This used to work in the cloud firestore version before the rework; I assume with it's own caveats.
@Salakar
The text was updated successfully, but these errors were encountered: