Broken on Chrome?

[kerim]

When I tried to use this on Chrome the pop-up window was a blank line. Disabling other extensions didn't help. (Authentication was not an issue.) Using Chrome on macOS.

[keithjgrant]

Is this installed from the Chrome Extension store or directly from the repository?
If I understand correctly, you were able to authenticate in the Omnibear window, but then when you re-opened it, it was blank? What URL were you on? Can you post a screenshot?

[m-metcalfe]

After authenticating in Chrome - in this case, Chrome OS Version 65.0.3325.167 (Official Build) beta (64-bit), micro.blog as the micro blog, and Twitter as the authentication provider - no UI is displayed except for a small, blank outline.

Following error is displayed in the console:

Uncaught SyntaxError: Unexpected token u in JSON at position 0 at JSON.parse (<anonymous>) at new t (index.js:1) at _ (index.js:1) at O (index.js:1) at w (index.js:1) at index.js:1 at g (index.js:1) at m (index.js:1) at e.render (index.js:1) at HTMLDocument.<anonymous> (index.js:1)

[kerim]

That's what it looks like for me as well. From the Chrome extension store. No problem authenticating.

[keithjgrant]

Did this error happen upon updating to version 1.0.0? (i.e. were you using a previous version before this occurred?)

[kerim]

First time install. I just learned about OmniBear and was eager to link it to my micro.blog...

[keithjgrant]

Interesting. Okay, I have a solid idea what might be doing this (parsing your user settings before they are defined). I'll see if I can hunt it down tomorrow.

[keithjgrant]

Version 1.0.1 is publishing now to the Chrome extensions store. You should see an update within the next hour or so.

I’m believe this will fix the issue, but not 100% certain, so I’ll leave this ticket open until you can confirm.

[m-metcalfe]

Updated to 1.0.1. UI doesn't disappear. I can create and submit a post, and happily get a 500 error back from the server. Imagine that last bit's my problem, though!

[kerim]

Loads, the UI doesn't disappear, and it authenticates, but then I get "error posting note"...

[keithjgrant]

Version 1.1.0 is publishing now to Chrome & Firefox stores. Once you get the update, can you

a) Enable the new logging feature, and
b) verify the issue still occurs

If you’re still having an issue, can you paste the relevant logs here?

[keithjgrant]

Assuming this is fixed. Let me know if you’re still having trouble and I’ll re-open this issue.