"Manage cards" stuck in "Loading cards!" screen

Both on my own deck, and on other decks I downloaded, I can’t get past “Loading cards!” after clicking on the “Manage Cards” button.

1 Like

Hi,

This might have to do with the caching mechanic that’s being used to make it load faster. Could you go to the settings page (from the sidemenu) and click on the wipe cache button there?

This should clear your cache and allow your browser to try and cache the cards again. If this doesn’t help and it gets stuck again, you can toggle on the “no cache” option at the settings, right below the button you clicked in the first part.

Sorry for the inconvenience, the tech used to cache the data sometimes works really well and sometimes less well. I’ll try to make it as failsafe as possible.

In case you have a bit of technical knowhow, I’d love to know if it logged any errors in the console. If not then you can disregard this last part.

Let me know if it works for you.

1 Like

Thanks for the quick reply! Here are some logs from the console.

Regular logs from before the error:

theme? default-theme [app.b44923f5c731000616b2.js:222:7104] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js) [NOTE: these things were links but because I’m a new user it’s limited to 3 so I separated the markdown link and replaced kitsun.io with kitsun_io :D]

setting theme yo [app.b44923f5c731000616b2.js:222:14673] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

1 [app.b44923f5c731000616b2.js:222:5363] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

order by cookie [9.4d278f1903c8598157a3.js:7:29560] (https://kitsun_io/static/js/9.4d278f1903c8598157a3.js)

2 [app.b44923f5c731000616b2.js:222:5363] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

3 [app.b44923f5c731000616b2.js:222:5363] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

starting [11.1abd0525b3bc293260f6.js:1:27301] (https://kitsun_io/static/js/11.1abd0525b3bc293260f6.js)

init db [app.b44923f5c731000616b2.js:198:100048] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

– loadDatabase - begin [app.b44923f5c731000616b2.js:1:69189] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

initializing idb [app.b44923f5c731000616b2.js:1:70675] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

yoyo [11.1abd0525b3bc293260f6.js:1:41664] (https://kitsun_io/static/js/11.1abd0525b3bc293260f6.js)

appending! [app.b44923f5c731000616b2.js:222:14014] (https://kitsun_io/static/js/app.b44923f5c731000616b2.js)

Error message in the console:

IndexeddB open error
error

bubbles: true

cancelBubble: false

cancelable: true

composed: false

currentTarget: null

defaultPrevented: false

eventPhase: 0

explicitOriginalTarget: IDBOpenDBRequest
​​
error: DOMException: “A mutation operation was attempted on a database that did not allow mutations.”
​​
onblocked: function onblocked()
​​
onerror: function onerror()
​​
onsuccess: function onsuccess()
​​
onupgradeneeded: function onupgradeneeded()
​​
readyState: “done”
​​
source: null
​​
transaction: null
​​
: IDBOpenDBRequestPrototype { onblocked: Getter & Setter, onupgradeneeded: Getter & Setter, … }

isTrusted: true

originalTarget: IDBOpenDBRequest
​​
error: DOMException: “A mutation operation was attempted on a database that did not allow mutations.”
​​
onblocked: function onblocked()
​​
onerror: function onerror()
​​
onsuccess: function onsuccess()
​​
onupgradeneeded: function onupgradeneeded()
​​
readyState: “done”
​​
source: null
​​
transaction: null
​​
: IDBOpenDBRequestPrototype { onblocked: Getter & Setter, onupgradeneeded: Getter & Setter, … }

returnValue: true

srcElement: IDBOpenDBRequest
​​
error: DOMException: “A mutation operation was attempted on a database that did not allow mutations.”
​​
onblocked: function onblocked()
​​
onerror: function onerror()
​​
onsuccess: function onsuccess()
​​
onupgradeneeded: function onupgradeneeded()
​​
readyState: “done”
​​
source: null
​​
transaction: null
​​
: IDBOpenDBRequestPrototype { onblocked: Getter & Setter, onupgradeneeded: Getter & Setter, … }

target: IDBOpenDBRequest
​​
error: DOMException: “A mutation operation was attempted on a database that did not allow mutations.”
​​
onblocked: function onblocked()
​​
onerror: function onerror()
​​
onsuccess: function onsuccess()
​​
onupgradeneeded: function onupgradeneeded()
​​
readyState: “done”
​​
source: null
​​
transaction: null
​​
: IDBOpenDBRequestPrototype { onblocked: Getter & Setter, onupgradeneeded: Getter & Setter, … }

timeStamp: 10612

type: “error”

<get isTrusted()>: function isTrusted()

: EventPrototype { composedPath: composedPath(), stopPropagation: stopPropagation(), stopImmediatePropagation: stopImmediatePropagation(), … }
app.b44923f5c731000616b2.js:1:71363
onerror https://kitsun.io/static/js/app.b44923f5c731000616b2.js:1

And then:

uncaught exception: [object Event] app.b44923f5c731000616b2.js:1:71395
onerror https://kitsun.io/static/js/app.b44923f5c731000616b2.js:1

Doesn’t look like the format gets pasted very nicely and I got too lazy to expand everything but hopefully that helps.

I haven’t tried clearing the cache yet in case you want me to expand some part of the error message.

P.S.: I lol’d at the various “yo” logs

ETA: I re-logged in on incognito so it shouldn’t be some bad cache data on my side, I think.

1 Like

Thats actually super helpful, thanks! I think the database might be at the limit of what your browser is allowing, which is why its throwing the error. I’ll make it wipe the database and fetch the cards from the server as a fallback. Thanks a bunch!

Haha some leftovers from previous debugging :laughing:

1 Like

@Kelitt These logs are from incognito mode on Firefox? As some googling shows me that this error pops up only in incognito mode in Firefox, and might actually not be the error that you’re getting when using “normal” firefox/chrome/etc :sweat_smile:

If it’s the incognito error, could you maybe check for the logs in the usual mode that you use to access Kitsun?

Ah, I was using incognito the entire time, sorry it wasn’t clear.

I just tried without it and it works fine, logs look pretty normal:

initializing idb app.b44923f5c731000616b2.js:1:70675

yoyo 11.1abd0525b3bc293260f6.js:1:41664

appending! app.b44923f5c731000616b2.js:222:14014

onupgradeneeded app.b44923f5c731000616b2.js:1:70911

init success app.b44923f5c731000616b2.js:1:71123

getting all chunks app.b44923f5c731000616b2.js:1:72333

getChunks: 2ms - timer ended app.b44923f5c731000616b2.js:1:72743

No chunks app.b44923f5c731000616b2.js:1:69332

no timestamp yet! 11.1abd0525b3bc293260f6.js:1:30747

timestamp? null [some hash looking thing so I redacted it] 11.1abd0525b3bc293260f6.js:1:31012

inserting timestamp [some hash looking thing so I redacted it] 1572812522948 11.1abd0525b3bc293260f6.js:1:42489

– exportDatabase - begin app.b44923f5c731000616b2.js:1:68418

get dirty chunk ids: 0ms - timer ended app.b44923f5c731000616b2.js:1:68693

get chunks&serialize: 0ms - timer ended app.b44923f5c731000616b2.js:1:68875

get dirty chunk ids: 0ms - timer ended app.b44923f5c731000616b2.js:1:68693

get chunks&serialize: 1ms - timer ended app.b44923f5c731000616b2.js:1:68875

makeChunks: 1ms - timer ended app.b44923f5c731000616b2.js:1:69029

put: 1ms - timer ended app.b44923f5c731000616b2.js:1:72185

combining data! 11.1abd0525b3bc293260f6.js:1:43040

save chunks to idb: 3ms - timer ended app.b44923f5c731000616b2.js:1:71807

exportDatabase: 5ms - timer ended

I also tried the workaround you mentioned (in incognito again) - wiping the cache doesn’t help, disabling it entirely works fine.

1 Like

Ah I see. Glad to hear it’s working like that.

I’ve just deployed a new update which should force a no-cache way of getting the cards in case the database initialization fails. But I’m not sure whether it’d work for this specific case.

It doesn’t seem to be working, I’m getting pretty much the same error.

Hey, I’m new to Kitsun and I am having the same problem.

I already cleared my cache but it still doesn’t work.
Any idea what I could do?

1 Like

Oh, so apparently the problem is with my edge browser somehow. It works perfectly fine on chrome, so problem solved (kind of). Still strange…

1 Like

Were you using the newest version of edge? (With the new greenish symbol)

That one is based on chrome (chromium) so it should work as well, I think. The old version (that most people still use) is on it’s way out and uses a different “core” so to say…

That said, I wasn’t aware of problems with Edge, I’ll try to reproduce the problem soon. Sorry about that!

You mean you weren’t aware that the company who made Internet Explorer had made another browser? :smile:

1 Like

Hahaha, I was definitely aware of problems with Edge in general, just not of problems with Edge for Kitsun in specific :laughing:

1 Like