Firestore error: "transactionGetDocument called for non-existant transactionId 0"

[ghost]

When I read a document after a transaction, this line is printed to my logs.

Does this indicate the transaction has failed/is not atomic?

const ok = await fsDb.runTransaction(async (t) => {
    t.set(docRef, data);
    // t.update(docRef, data);
    return true;
});
const d = await docRef.get();

transactionGetDocument called for non-existant transactionId 0

react-native-firebase/ios/RNFirebase/firestore/RNFirebaseFirestore.m

Line 50 in 94852c8

DLog(@"transactionGetDocument called for non-existant transactionId %@", transactionId);

Environment

1. Application Target Platform:
   iOS

2. Development Operating System:
   macOS

3. Build Tools:
   Xcode

4. React Native version:
   version "0.55.3"

5. React Native Firebase Version:
   version "4.0.6"

6. Firebase Module:
   Firestore

[ghost]

@Salakar Are transactions still safe to use, or does this log message indicate an error state?

[Salakar]

@enzomd they are still safe, that log is purely there as a safeguard / fyi i.e. between RN reloads of your app in dev native vs JS can become out of sync, therefore, the transaction could exist in native but not in JS and vice versa.

Am assuming this was local dev of course?

[Salakar]

@enzomd I've reworked the transaction logic for iOS in v5.1.0, could you try out the RC and report back in a new issue if you're still seeing this log, thank you.

yarn add [email protected] (use /tests app on master as a reference for SDK versions)

---

Loving react-native-firebase and the support we provide? Please consider supporting us with any of the below:

• 👉 Back financially via Open Collective
• 👉 Follow React Native Firebase and Invertase on Twitter
• 👉 Star this repo on GitHub ⭐️