Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError every single time any note is updated #72

Open
Lulullia opened this issue May 5, 2022 · 9 comments
Open

TypeError every single time any note is updated #72

Lulullia opened this issue May 5, 2022 · 9 comments

Comments

@Lulullia
Copy link

Lulullia commented May 5, 2022

Hi,
While I was doing some theme stuff in the inspector I noticed that every time I changed anything in any note, I get this error below.
I investigated the source of the problem by disabling my plugins one by one and is seems that MetaEdit is the one causing the error (at least with it off there's nothing wrong).

I included the full log below, I hope it'll be helpful.

In addition to this, I noticed that everytime I load the plugin or change its settings, I get this printed (it's not an error though):
MetaEdit: (LOG) automator of type 'ProgressProperties' does not exist.

When I change the toggle "Kanban helper" for example, I get the same thing but with "KanbanHelper" instead of "ProgressProperties".

I'm not sure what this all means. I currently do not use MetaEdit and have empty settings, it's just enabled like that.

Uncaught (in promise) TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at OnFileModifyAutomatorManager.onFileModify (eval at <anonymous> (app.js:1:1494667), <anonymous>:5266:29)
onFileModify @ VM8231:5266
await in onFileModify (async)
eval @ VM8231:5239
e.tryTrigger @ app.js:1
e.trigger @ app.js:1
t.trigger @ app.js:1
t.onChange @ app.js:1
e.trigger @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
e.reconcileFileCreation @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
e.reconcileFileInternal @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
e.reconcileFile @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
e.reconcileInternalFile @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
(anonymous) @ app.js:1
n @ app.js:1
Promise.then (async)
e.queue @ app.js:1
e.write @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
t.modify @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
T @ app.js:1
t.save @ app.js:1
a @ app.js:1
setTimeout (async)
l @ app.js:1
n.requestSave @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
setTimeout (async)
l @ app.js:1
(anonymous) @ app.js:1
e.update @ app.js:1
_dispatch @ app.js:1
e.dispatch @ app.js:1
wS @ app.js:1
CS @ app.js:1
xS @ app.js:1
c @ app.js:1
pc @ app.js:1
keydown @ app.js:1
e.runCustomHandlers @ app.js:1
(anonymous) @ app.js:1
@sundevista
Copy link

I have same issue

@TfTHacker
Copy link

I am seeing the same thing. Yes it is a bit distracting while debugging :-)

@dredhorse
Copy link

This should be fixed, but there is no newer version 😞 #66 (comment)

@jdmorg0
Copy link

jdmorg0 commented May 20, 2022

Having this issue as well. Hopefully that fix gets released soon.

@imeed166
Copy link

same here

@jaxxor44
Copy link

same

@ChitaGideon
Copy link

ChitaGideon commented Nov 21, 2022

almostly the same with version 1.7.2
image

@tonyxiao
Copy link

image

Same. Is this repo still being maintained?

@TfTHacker
Copy link

@tonyxiao I switched over to Metadata menu for similar features just to not see this error any longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants