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

Not tracking #107

Open
Bosnier opened this issue Jul 25, 2023 · 9 comments
Open

Not tracking #107

Bosnier opened this issue Jul 25, 2023 · 9 comments

Comments

@Bosnier
Copy link

Bosnier commented Jul 25, 2023

After the update, time tracking stopped working. It doesn't work in other profiles either.
Chrome 96

image

@Stigmatoz
Copy link
Owner

Yes, I see, I fixed it and need to wait approval from the Google Store team.

@Stigmatoz
Copy link
Owner

The extension has been updated, so let's check it out and please tell me if everything is OK.

@Bosnier
Copy link
Author

Bosnier commented Jul 25, 2023

Nothing has changed with the update.
I installed the version from GitHub and it gives the following error:

image

@Stigmatoz
Copy link
Owner

Can you update Chrome and check again?

@Bosnier
Copy link
Author

Bosnier commented Jul 25, 2023

Sorry, but I don't want to update chrome.

So far I solved the problem by downloading version 1.7.2 and copying the contents of 2.0.1 in the "User Data\Local Extension Settings" folder to the folder belonging to version 1.7.2

Surprisingly this worked

@Stigmatoz
Copy link
Owner

I moved the extension to the manifest version 3 in the current version. (>=2.0.0)

@Bosnier
Copy link
Author

Bosnier commented Jul 25, 2023

I didn't quite get the message of the last comment.
I currently have version 1.7.2 installed, and was able to migrate data from version 2.0.1 installed via the chrome web store.
2.0.1 is still not working for me

@Stigmatoz
Copy link
Owner

I mean, I changed the codebase in version 2.0 and moved the extension to manifest v3. This is a recommended requirement from Google.

And it's a little strange that you have an error. It could probably be related to the Chrome version, but I'm not sure.

@Bosnier
Copy link
Author

Bosnier commented Jul 26, 2023

Looks like it was a bug and was fixed in some release of Chrome.
https://bugs.chromium.org/p/chromium/issues/detail?id=1159438
https://bugs.chromium.org/p/chromium/issues/detail?id=1187361

I also looked at what versions of the manifest used by the other extensions I use (uBlock, ViolentMonkey, The Great Suspender, Decentraleyes). And they all use the version 2 manifest.

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

2 participants