Invalid typeids in shortlist prevent loadout creation

Loading overlay never disappears. Console shows an error:

js.new_loadout.min.js:3045 Uncaught TypeError: Cannot read property '0' of undefined
    at osmium_init_shortlist (js.new_loadout.min.js:3045)
    at osmium_init_sources (js.new_loadout.min.js:2916)
    at osmium_init (js.new_loadout.min.js:6970)
    at js.new_loadout.min.js:6896
    at onsuccess2 (js.new_loadout.min.js:2361)
    at Object.success (js.new_loadout.min.js:2392)
    at c (jquery.min.js:4)
    at Object.fireWith [as resolveWith] (jquery.min.js:4)
    at k (jquery.min.js:6)
    at XMLHttpRequest.r (jquery.min.js:6)
osmium_init_shortlist @ js.new_loadout.min.js:3045
osmium_init_sources @ js.new_loadout.min.js:2916
osmium_init @ js.new_loadout.min.js:6970
(anonymous) @ js.new_loadout.min.js:6896
onsuccess2 @ js.new_loadout.min.js:2361
success @ js.new_loadout.min.js:2392
c @ jquery.min.js:4
fireWith @ jquery.min.js:4
k @ jquery.min.js:6
r @ jquery.min.js:6
XMLHttpRequest.send (async)
send @ jquery.min.js:6
ajax @ jquery.min.js:6
osmium_load_static_client_data @ js.new_loadout.min.js:2375
(anonymous) @ js.new_loadout.min.js:6894
c @ jquery.min.js:4
fireWith @ jquery.min.js:4
ready @ jquery.min.js:4
q @ jquery.min.js:4

[Artefact2]

On Fri, Oct 06, 2017 at 07:22:50PM -0700, Erich Herz wrote: Loading overlay never disappears. Console shows an error: js.new_loadout.min.js:3045 Uncaught TypeError: Cannot read property '0' of undefined at osmium_init_shortlist (js.new_loadout.min.js:3045) at osmium_init_sources (js.new_loadout.min.js:2916) at osmium_init (js.new_loadout.min.js:6970) at js.new_loadout.min.js:6896 at onsuccess2 (js.new_loadout.min.js:2361) at Object.success (js.new_loadout.min.js:2392) at c (jquery.min.js:4) at Object.fireWith [as resolveWith] (jquery.min.js:4) at k (jquery.min.js:6) at XMLHttpRequest.r (jquery.min.js:6) osmium_init_shortlist @ js.new_loadout.min.js:3045 osmium_init_sources @ js.new_loadout.min.js:2916 osmium_init @ js.new_loadout.min.js:6970 (anonymous) @ js.new_loadout.min.js:6896 onsuccess2 @ js.new_loadout.min.js:2361 success @ js.new_loadout.min.js:2392 c @ jquery.min.js:4 fireWith @ jquery.min.js:4 k @ jquery.min.js:6 r @ jquery.min.js:6 XMLHttpRequest.send (async) send @ jquery.min.js:6 ajax @ jquery.min.js:6 osmium_load_static_client_data @ js.new_loadout.min.js:2375 (anonymous) @ js.new_loadout.min.js:6894 c @ jquery.min.js:4 fireWith @ jquery.min.js:4 ready @ jquery.min.js:4 q @ jquery.min.js:4 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #196

This sounds like stale cache to me, have you tried clearing your local storage and force-refreshing the page? (Or try an incognito window first, to see if it solves the problem, then empty your cache.)

Hmm I have cached disabled in my dev tools but seems not working. In cognito worked.

Sorry!

I think I've found the issue - it only happens when I'm logged into my Eve account. This is a big problem cause I can't save any of the fits I create. This account was created by logging in through the Eve API. My character is also mapped (only one on the account). I can give you my account name for troubleshooting if you need it but I don't want to post it here.

[Artefact2]

Is it still the same error, then? Or do you get a different error when trying to save your loadouts?

You can email me your character name or ID (and if you're really paranoid, use my OpenPGP public key) and I'll wipe your shortlist, as that seems to contain an erroneous type ID.

Yes it's the same error. Here's the profile I'm talking about:
https://o.smium.org/profile/3032

If you wouldn't mind clearing that bad data I'd really appreciate it!
Thanks in advance.

[Artefact2]

On Fri, Oct 20, 2017 at 11:39:58PM -0700, Erich Herz wrote: Yes it's the same error. Here's the profile I'm talking about: https://o.smium.org/profile/3032 If you wouldn't mind clearing that bad data I'd really appreciate it! Thanks in advance. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #196 (comment)

I just cleared the invalid array from the database. Please reply if you have any more issues.

Issue is resolved. Thanks very much.