Ben White

Tasks.call() is still present in firebase_core, cloud_firestore, firebase_analytics, firebase_crashlytics, firebase_performance

I am seeing this as well. In the 'state' of the stateful widget where I am calling MobileScanner, I added an override for dispose, and called _controller.stop(). Even that didn't...

Just pulled the flutterfire firebase_analytics example. Made the following changes ``` android/app/build.gradle compileSdkVersion 31 ``` ``` android/build.gradle classpath 'com.android.tools.build:gradle:7.1.3' I also added the following: allprojects { gradle.projectsEvaluated { tasks.withType(JavaCompile) {...

I am not sure why this feature request was closed. It would be a new feature and could put comments on it's usage. In my use case, I do not...

Added some debugging to the function. This is the debug from the android sdk: `W/Firestore(18105): (24.11.0) [WriteStream]: (a26a33) Stream closed with status: Status{code=NOT_FOUND, description=No document to update: projects/project-name/databases/(default)/documents/CollectionA/DocumentB/CollectionC/missing_document, cause=null}.` This...

Updated integration test.

@russellwheatley I can't reproduce locally, so added some debug. If someone could start the workflow, that would be great. https://github.com/firebase/flutterfire/actions/runs/10113353206

I was able to get it the workflows running locally. Seems to be some inconsistency between actual android firestore, emulated android firestore, emulated macOS firestore, and emulated ios firestore. Actual...

@russellwheatley Do you have a preference on how to proceed?