React-native-firebase: Promise when set data offline

[rodolfobarretoweb]

Hello guys, I have a question.

I have this action on my project:

export function save(data) {
    return (dispatch, getState) => {
        return Firebase.database().ref(`profiles/${data.uid}`).set(data).then(() => {
           dispatch({ type : SAVE_PROFILE });
        });
     }
}

But when I go to offline mode this promise never resolving. How to fix that ?

PS: The data persiste localy, just the promise never resolving

---

"react": "16.0.0-alpha.12",
"react-native": "0.45.1",
"react-native-firebase": "1.1.1"

I test this using genymotion and real device

[rodolfobarretoweb]

Hi, additional information:

When I try to get data, the promise always resolving online or offline. So, probably has a bug on set method of this library.

[Ehesp]

Hey, is it still actually setting/updating on Firebase?

[rodolfobarretoweb]

Yes, pretty sure

[chrisbianca]

@rodolfobarretoweb is this on iOS as well as Android? Do you have persistence enabled?

[rodolfobarretoweb]

@chrisbianca Yes, I have the persistence enable, but I not test in ios devices.

[SamMatthewsIsACommonName]

@rodolfobarretoweb @chrisbianca my experience with this is that for update and set the callback happens when the data actually syncs with the real database (not the local cached version)

[rodolfobarretoweb]

@SamMatthewsIsACommonName Yes, works like you describe but the promise haft to be solved, independent of synchronization or not

[chrisbianca]

Unfortunately this is out of our control as we rely on the native SDK behaviour. As the iOS documentation states, the set method will only resolve when the data has been committed to the Firebase servers.

https://firebase.google.com/docs/reference/swift/firebasedatabase/api/reference/Classes/DatabaseReference#/c:objc(cs)FIRDatabaseReference(im)setValue:withCompletionBlock:

[i2chris]

What's the workaround for this? Do we just stop using promises and assume the data was written? Seems a shame.

[koloff]

It seems like the only workaround is to check if offline and resolve the promise, hoping the data got written.

[claycoleman]

I'm seeing similar problems with adding data to collections, which I presume is due to the same problem. @chrisbianca I know you closed this a while ago, but any thoughts on a workaround on this besides hoping the data gets written? My app needs the id of the new doc after creating it, and as the docs are still being created offline and assigning unique ids, it seems there should be a way to access the them.

UPDATE

Aha! I did a bit more digging and found these two SO posts:

https://stackoverflow.com/questions/49818095/firebase-firestore-when-do-promises-from-offline-write-operations-resolve
https://stackoverflow.com/questions/49829714/firebase-firestore-get-document-id-after-adding-data-offline

For my purposes, the second solution is sufficient.