Error

[matthewhisle]

I am getting the following error... It ONLY happens after device has been used for a long time. If I refresh chrome cache, it works fine again

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'name') at nt (jsstore.worker.min.js:2:64964) at jsstore.worker.min.js:2:69300

Again, if I refresh chrome and delete all data, it works again.

It appears that it has an issue with the dbName... AKA the name of the database. Any advice?

[matthewhisle]

const isDbCreated = await connection.initDb(database);
if (isDbCreated === true) {
    //alert("db created");
}
else {
    // alert("db opened");
}

It is failing on the line const isDbCreated

Without ANY code change, if I clear the chrome storage on phone, it starts to work again. This error is random, and only every once in awhile after lots of usage.

[matthewhisle]

Thank you for the reply! I am currently using the LATEST version of JSSTORE.

It was failing right here on e.name .... This is in jsstore.worker.min.js

[ujjwalguptaofficial]

I will check this, thanks.

[matthewhisle]

Thank you! I really appreciate it. This will help me tremendously, we love jsstore!

[matthewhisle]

I saw an error before in this forum where someone got the exact same error that I got here. Then it was because the person wasn't initializing the connection right. Is it possible that the real error is in the initialization of the connection, then causing this error message to occur for me. Upon investigation, the connection is getting stuck and requests add up in the queue. Perhaps an error in the service worker?

[matthewhisle]

Thread name "connection.dropDb() not works" in these forums

You'll notice my error message is IDENTICAL to his. Except his was thrown simply because he did not initialize database first. Mine was thrown ON the database initialization call.

[matthewhisle]

Keep in mind, the oddity is that with this... It works 100% fine, then after awhile it starts to fail and gives the error up there on this line with 0 code changing... Then if I clear all chrome data, it works again

[ujjwalguptaofficial]

Thanks for the explanation, i will spend time on this and let you know.

[matthewhisle]

Thank you so much. Let me know if there is any way I can help.

[ujjwalguptaofficial]

This is the code where error is occuring.

but it's not possible as there is already a null check when this class is initiated .

I will keep my eye on it, but if you find something let me know.

[matthewhisle]

Was there any recent version where you did not have a null check there? Because that is exactly where the error was getting thrown. And this was in the initialization of the database

[matthewhisle]

This is still happening. Not sure why.

[matthewhisle]

Same error message

[matthewhisle]

I think the error message is a RESULT of the connection var being messed up.

[matthewhisle]

Inactivity timer gets set to -1 and it starts to queue any task I try to run on the DB and won't run anything. The "request queue" just starts to pile up. It is like the worker is getting stuck somehow.

[matthewhisle]

It seems like its the connection var getting stuck. How often do connections expire? Do you recommend me wrapping the DB Initialization in a try catch and if it hits the catch, destroy the connection and recreate it? I am declaring the connection in a .js file that is used by multiple HTML pages.

[ujjwalguptaofficial]

connection.terminate is supposed to terminate everything and release the resources. So it's normal - if you want to use query on this connection, you gotta reinitialize using initDb api.

[ujjwalguptaofficial]

https://jsstore.net/docs/terminate

[matthewhisle]

Understood. What I am referring to is when this glitch occurs, I am initializing the connection but it's stuck in terminated state with inactivity timer set to -1000

[ujjwalguptaofficial]

the reintialization should work, if its not working then please give me a reproducible repo.

Also if you are able to reproduce the issue, we can get on a call to debug and fix this.

[matthewhisle]

Thank you so much! Will do. Waiting to get my hands on a device of my team when it stops working. Will hit you up then!

[matthewhisle]

[matthewhisle]

Finally got my hands on another device that failed. Note this only happens once every blue moon!

[matthewhisle]

Init_DB itself gets stuck in the request queue

[matthewhisle]

Please let me know any additional info you need to debug. I am remote debugging the specific device that is "Locked Up"

[matthewhisle]

Since its the connection itself seemingly getting stuck I can't even enable log status

[matthewhisle]

I will give this a try tomorrow when I am able to update my production site with this new code and will let you know what happens. Thank you!

[matthewhisle]

Just as a side note, I get the same error even if I initialize connection with no worker TypeError: Cannot read properties of undefined (reading 'name')
at nt (:7:64964)
at :7:69300

[matthewhisle]

Just learned something REALLY odd. If I initialize another database on page load with a different name it loads fine and now shows 2 databases in my application... So its like something is stuck with that SPECIFIC database name

[matthewhisle]

So if I try to run initDb on cadmusscribe it gives all those errors. If I run it to create cadmusscribe1, no issues. Both have identical schema

[matthewhisle]

I used indexedDB.deleteDatabase() on cadmusscribe, and now everything works great.

[matthewhisle]

Hey I have been using the indexeddb.deletedatabase() call on the catch to rebuild teh database when this happens and its been working okay for me, just wanted to check if you have seen any root cause for why the JSMeta is getting deleted and messing up the local database?