CRUD operations in offline mode - Firestore - Android

[AkshayAdiga1997]

If I have a where clause based on modified_date (firestore servertimestamp) field
where('md', '>=', last_fetch_firestore_timestamp)
, I get the document in IOS even when offline. The metadata.hasPendingWrites of the document would be true (even though the modified_date field value is now null) But the same scenario fails on android.
Note: where clause is required. Pl let me know what am I missing here. Thanks

[mikehardy]

This may be due to underlying platform differences - I strongly suspect it is actually.
If you've checked the actual code through here to make sure that the underlying javascript (then Obj-C and Java) API calls seem sensible, my best - though unfortunately difficult - suggestion is to make a quickstart for each platform where you verify behavior and confirm whether it's an upstream issue or not

https://github.com/firebase/quickstart-ios/tree/master/firestore
https://github.com/firebase/quickstart-android/tree/master/firestore

I strongly recommend checking both of those repo's issues list (especially android since that appears to be the platform not meeting expectations?) to see if they have anything.

Also make absolutely sure you are on the most up to date react-native-firebase version so you have the updated native SDKs

[mikehardy]

It does sound important. The platforms should behave the same. But it sounds like it needs to be pursued with the firebase-android-sdk quickstart for verification. Very curious to hear results - it could be something we are doing as we wrap the APIs but things like this are usually deeper

[AkshayAdiga1997]

@mikehardy Hey! Any updates on this? I am not sure if I can work on the quickstart thing as it is completely native IOS/Android and I am not good at it. Any other way I can be of any help to solve this issue? I want this to be fixed for my upcoming startup. Pl help me out. Thanks.

[mikehardy]

Hi @AkshayAdiga1997 - sorry, I am not planning on spending any time on this. I'm waiting to hear your results

[AkshayAdiga1997]

@mikehardy Sorry if you don't mind can you explain what results are you expecting here? Will try my best to get it out soon.

[mikehardy]

@AkshayAdiga1997

My prior comment:

This may be due to underlying platform differences - I strongly suspect it is actually.
If you've checked the actual code through here to make sure that the underlying javascript (then Obj-C and Java) API calls seem sensible, my best - though unfortunately difficult - suggestion is to make a quickstart for each platform where you verify behavior and confirm whether it's an upstream issue or not

https://github.com/firebase/quickstart-ios/tree/master/firestore
https://github.com/firebase/quickstart-android/tree/master/firestore

I strongly recommend checking both of those repo's issues list (especially android since that appears to be the platform not meeting expectations?) to see if they have anything.

Also make absolutely sure you are on the most up to date react-native-firebase version so you have the updated native SDKs