Johannes
Johannes
One possible fix is by modifying the `IsolateHolderService.startLocatorService()` method in `IsolateHolderExtension.kt` in a way that I`solateHolderService.backgroundEngine` gets initialized earlier: https://github.com/oligazar/background_locator/blob/master/android/src/main/kotlin/rekab/app/background_locator/IsolateHolderExtension.kt I don't know if that fixes the root problem, but...
@mehdok I'm actually not the one who implemented this. From what I understand, the try/catch might be for logging purposes and therefore isn't critical.
Hi @mehdok, any updates on this issue?
@mehdok what's the curent status? It would be good to know whether or not we can expect updates to this project in the future. Thanks!
Any news on the status of this? Would love to see all Firestore data types supported. Could somebody please share a code snippet that would be required to add support...
Ok, thanks for your reply. Could you share how the workaround you suggested, using custom fields would work? Something really simple, like giving the user a text field where comma...
@fgatti675 hm ok. I tried a custom field implementation as per your link for the type GeoPoint. However, in the CMS, I still get the error "Currently the field geopoint...
@fgatti675 ah yeah, I did. I'll update the code snippet. So in the create/edit view the field is showing the error message.
Agree, the Isolates documentation doesn't yield enough information to make Streams across isolates work. Also seems outdated in regards to Flutter APIs (e.g. RootIsolateToken.instance may return null).