Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

[Extension] First project not visible #116

Closed
kptdobe opened this issue Oct 29, 2021 · 3 comments · Fixed by #167
Closed

[Extension] First project not visible #116

kptdobe opened this issue Oct 29, 2021 · 3 comments · Fixed by #167
Labels
bug Something isn't working released

Comments

@kptdobe
Copy link
Contributor

kptdobe commented Oct 29, 2021

I followed the Show&Tell instructions and installed the extension. I just added my first project: open the sidekick via bookmarklet, click the share button, go to that page, click "ok" to add to extension and click "ok" to open extensions.

First observation: the project I just added is not there.
Second observation: I pasted the share url to add the project again and it says the project has already been added.

See

image

@kptdobe kptdobe added the bug Something isn't working label Oct 29, 2021
@kptdobe
Copy link
Contributor Author

kptdobe commented Oct 29, 2021

Ok, maybe it is the project I am using which uses credentials in the fstab and those seem to be expired.
Nevertheless, my extension is completely broken at the moment (I can manually add projects but they are not visible)

@rofe
Copy link
Contributor

rofe commented Oct 29, 2021

Really odd... I assume the configs also don't show up when you refresh the options page? Do you see any JS errors in the console?

The extension needs the permission to use the chrome.storage API to store configurations. Maybe you need to grant it explicitly. More info may also be available when clicking the Details button of the extension on chrome://extensions.

@trieloff
Copy link

trieloff commented Dec 2, 2021

🎉 This issue has been resolved in version 3.23.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants