firebase-js-sdk icon indicating copy to clipboard operation
firebase-js-sdk copied to clipboard

DOMException: Failed to execute 'put' on 'IDBObjectStore': The transaction is not active.

Open pratt3351 opened this issue 1 year ago • 4 comments

Operating System

mac OS

Browser Version

all of browser

Firebase SDK Version

10.7.2

Firebase SDK Product:

Analytics

Describe your project's tooling

with react-native + react-native web.

Describe the problem

intialize firebase sdk and call any other firebase module just always throw this errors

DOMException: Failed to execute 'put' on 'IDBObjectStore': The transaction is not active. at Proxy. (https://localhost/scripts/script.340834.js:381329:26) at _callee6$ (https://localhost/scripts/script.340834.js:389062:24) at tryCatch (https://localhost/scripts/script.340834.js:388438:1357) at Generator. (https://localhost/scripts/script.340834.js:388438:4172) at Generator.next (https://localhost/scripts/script.340834.js:388438:2208) at asyncGeneratorStep (https://localhost/scripts/script.340834.js:388442:103) at _next (https://localhost/scripts/script.340834.js:388443:194) at tryCallOne (https://localhost/scripts/script.340834.js:133892:12) at https://localhost/scripts/script.340834.js:133973:15 at run (https://localhost/scripts/script.340834.js:238290:9)

what's wrong with my project..? i'm using react-native 0.72.7, and react-nativeweb 0.19.9 version

Steps and code to reproduce issue

i have this babel presets.

{
      presets: [
        [
          '@babel/preset-env',
          {
            loose: true,
            corejs: { version: '3.22', proposals: true },
            useBuiltIns: 'entry',
            targets: { ie: '11' },
          },
        ],
        ['@babel/preset-react', { runtime: 'automatic' }],
        '@babel/preset-typescript',
      ],
      plugins: defaultPlugins,
    }

pratt3351 avatar Jan 28 '24 13:01 pratt3351

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

google-oss-bot avatar Jan 28 '24 13:01 google-oss-bot

This error is generated by the browser's implementation of the IndexedDB API. Can you provide us with a minimal reproducible test case that we can try to debug on our side? Thanks!

DellaBitta avatar Feb 05 '24 14:02 DellaBitta

Hey @pratt3351. 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 avatar Feb 12 '24 02:02 google-oss-bot

This error is generated by the browser's implementation of the IndexedDB API. Can you provide us with a minimal reproducible test case that we can try to debug on our side? Thanks!

well, i dont know exactly test it. it is occurs when initiate firebase sdk and using some kind of functions that produce by firebase remote config functions

pratt3351 avatar Feb 12 '24 15:02 pratt3351

We've seen intermittent errors in Safari's implementation of IndexedDB, and we're looking to find a way to reproduce them. We've added many protections about this in the last few months but they were best guesses since we didn't have a reproducible test case, and we're still seeing errors.

If you can provide any more information about the state of the client then that would be extraordinarily helpful. For instance, another user has recently reported that IndexedDB clears its storage database if someone leaves the Safari dev tools open for an hour.

DellaBitta avatar Apr 05 '24 15:04 DellaBitta

Hey @pratt3351. 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 avatar Apr 12 '24 01:04 google-oss-bot

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

@pratt3351 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.

google-oss-bot avatar Apr 18 '24 01:04 google-oss-bot