Error when running runTransaction inside electron application. Throws INTERNAL ASSERTION FAILED: Unexpected state

[Sapython]

Operating System

Windows 10

Browser Version

Firefox 117.0.1 (64-bit

Firebase SDK Version

9.21.0

Firebase SDK Product:

Firestore

Describe your project's tooling

Angular app with electron.

Describe the problem

I was trying to run a transaction. The specific code is this

return runTransaction(this.firestore,async (transaction)=>{
      let kotTokenNumber = (await transaction.get(doc(this.firestore,'business/'+this.dataProvider.businessId+'/settings/settings'))).data()['kitchenTokenNo'];
      let orderTokenNumber = (await transaction.get(doc(this.firestore,'business/'+this.dataProvider.businessId+'/settings/settings'))).data()['orderTokenNo'];
      transaction.update(doc(this.firestore,'business/'+this.dataProvider.businessId+'/settings/settings'),{kitchenTokenNo:increment(1),orderTokenNo:increment(1)});
      return {kotTokenNumber,orderTokenNumber};
    });

this functions normally and correctly in a browser but when running it inside a electron application it fails.

and this is the error it throws

[2023-09-23T15:42:36.151Z]  @firebase/firestore: Firestore (9.21.0): FIRESTORE (9.21.0) INTERNAL ASSERTION FAILED: Unexpected state
ABe @ main.017ae000de9fe4ff.js:462
error @ main.017ae000de9fe4ff.js:462
xl @ main.017ae000de9fe4ff.js:462
gr @ main.017ae000de9fe4ff.js:462
wr @ main.017ae000de9fe4ff.js:462
(anonymous) @ main.017ae000de9fe4ff.js:462
(anonymous) @ main.017ae000de9fe4ff.js:462
mee @ main.017ae000de9fe4ff.js:462
s @ main.017ae000de9fe4ff.js:462
invoke @ polyfills.b8c5491cd9d2f3fa.js:1
onInvoke @ main.017ae000de9fe4ff.js:462
invoke @ polyfills.b8c5491cd9d2f3fa.js:1
run @ polyfills.b8c5491cd9d2f3fa.js:1
(anonymous) @ polyfills.b8c5491cd9d2f3fa.js:1
invokeTask @ polyfills.b8c5491cd9d2f3fa.js:1
onInvokeTask @ main.017ae000de9fe4ff.js:462
invokeTask @ polyfills.b8c5491cd9d2f3fa.js:1
runTask @ polyfills.b8c5491cd9d2f3fa.js:1
_ @ polyfills.b8c5491cd9d2f3fa.js:1
processTicksAndRejections @ node:internal/process/task_queues:96
Promise.then (async)
q @ polyfills.b8c5491cd9d2f3fa.js:1
R @ polyfills.b8c5491cd9d2f3fa.js:1
scheduleTask @ polyfills.b8c5491cd9d2f3fa.js:1
onScheduleTask @ polyfills.b8c5491cd9d2f3fa.js:1
scheduleTask @ polyfills.b8c5491cd9d2f3fa.js:1
scheduleTask @ polyfills.b8c5491cd9d2f3fa.js:1
scheduleMicroTask @ polyfills.b8c5491cd9d2f3fa.js:1
ee @ polyfills.b8c5491cd9d2f3fa.js:1
z @ polyfills.b8c5491cd9d2f3fa.js:1
(anonymous) @ polyfills.b8c5491cd9d2f3fa.js:1
(anonymous) @ polyfills.b8c5491cd9d2f3fa.js:1
(anonymous) @ main.017ae000de9fe4ff.js:462
emit @ node:events:513
endReadableNT @ node:internal/streams/readable:1358
processTicksAndRejections @ node:internal/process/task_queues:83

Steps and code to reproduce issue

Create an angular project and then create a runTransaction function like mentioned here then build it and run it inside of electron application.

[dconeybe]

Hi @Sapython. I'm not familiar with angular or electron. Would you be able to provide a minimal app that I can use to reproduce this issue, ideally a github repo I can clone and run? Also, are you able to deminify the stack trace? The message "unexpected error" is a general, catch-all error message and the specific line numbers in Firestore would really help isolate the problem.

[dconeybe]

Also, I just noticed that you are using a 5-month-old version of the Firebase SDK: 9.21.0. Could you please upgrade to the latest version (10.4.0 at the time of writing) and reproduce? There was a fix in v10.0.0 that fixed the source maps and without this fix you won't be able to meaningfully deminify the stack trace.

[google-oss-bot]

Hey @Sapython. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@Sapython if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.