Mark Grimes
Mark Grimes
Thanks for the response. `pFirestore` and `pStorage` have duration for the whole app, so they're fine. I'm 99% sure `callback` is still alive but checking that now. I wondered about...
Removing `fileRef` makes no difference.
Some other naive testing, considering I don't really understand the internals. If I fake the Firestore data so that I can go straight to the file download, it works fine....
Not easily. It's coded as a pure C++ library which is later included in an iOS app, and anything like `dispatch_async( dispatch_get_main_queue(), ^{ ... } );` isn't available at that...
I had a look at the code base again, and the relevant part is actually in an Objective-C++ shim that then calls into the pure C++. So I was able...
I tried with the address sanitizer early on, and got loads of crashes where it said the sanitizer couldn't allocate memory. There was also one where it said it couldn't...
Sure, if it helps you figure out what's going on.
I've tried this twice with fresh downloads of that package and clean builds, and I get zero log lines with "zzyzx". You meant "zzyzx" literally right? I added `::firebase::SetLogLevel( ::firebase::kLogLevelVerbose...
Okay, I have a minimal public repository which has the same bug: https://github.com/mark-grimes/FirebaseCppDoubleCallback The assert isn't triggered every single time, but it's higher than 50%. Hopefully you can trace through...
Is there any progress on this from the Storage team? We're having separate issues related to having to run Firestore completion handlers on the main thread, and would prefer not...