You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser version: Edge Version 126.0.2592.56 (Official build) (64-bit)
Extension version: 2.0.20_0
Relevant integration (if any):
🐛 Describe the bug
I just restarted Edge and ofc it auto-updated (hurray), and now my side-loaded Toggle extension is broken. Restoring Windows to a few weeks ago doesn't fix it, and I'm experiencing the same bug on Mac Chrome, so I actually suspect the problem might be a change on Toggl's end with how authentication works.
It looks like this now.
Expected behaviour
If there is a workaround to e.g. replace part of the v2 extension with something from the v3 one, it would be awesome if you could let me know.
I expect clicking the Toggl button extension to bring up the regular menu, and for it to show I'm logged in, WITH THE v2 extension.*
*I have the group policy enabled for my browser to continue to use v2, so it becoming unsupported is not a concern at the moment.
Steps to reproduce
Load version 2.0.20_0 or load the attached as an unpacked extension (after enabling Developer Mode).
Click the Toggl button and/or navigate to the extension settings.
Other details or context
Looking at the extension options, it looks like my login isn't being detected properly.
I tried reloading the extension, resetting the settings, and reinstalling (whereupon it let me re-login). But the extension itself still doesn't detect my login properly.
I also see these two errors in Edge now about the extension, but I'm not sure how long they have been there (they might be unrelated?):
Both are related to the manifest, e.g., Manifest contains a differential_fingerprint key that will be overridden on extension update.
I'm using an old version of Toggl because I need to use a custom integration (because it's been years and Toggl still hasn't added an official version of the integration I want), and newer versions of the extension don't allow custom integrations.
The text was updated successfully, but these errors were encountered:
weirdalsuperfan
changed the title
Manifest contains a differential_fingerprint key that will be overridden on extension update.
Login not detected properly - showing up as empty
Jun 19, 2024
Relevant integration (if any):
🐛 Describe the bug
I just restarted Edge and ofc it auto-updated (hurray), and now my side-loaded Toggle extension is broken. Restoring Windows to a few weeks ago doesn't fix it, and I'm experiencing the same bug on Mac Chrome, so I actually suspect the problem might be a change on Toggl's end with how authentication works.
It looks like this now.
Expected behaviour
If there is a workaround to e.g. replace part of the v2 extension with something from the v3 one, it would be awesome if you could let me know.
I expect clicking the Toggl button extension to bring up the regular menu, and for it to show I'm logged in, WITH THE v2 extension.*
*I have the group policy enabled for my browser to continue to use v2, so it becoming unsupported is not a concern at the moment.
Steps to reproduce
2.0.20_0.zip
Try logging in.
Click the Toggl button and/or navigate to the extension settings.
Other details or context
Looking at the extension options, it looks like my login isn't being detected properly.
I tried reloading the extension, resetting the settings, and reinstalling (whereupon it let me re-login). But the extension itself still doesn't detect my login properly.
I also see these two errors in Edge now about the extension, but I'm not sure how long they have been there (they might be unrelated?):
Both are related to the manifest, e.g.,
Manifest contains a differential_fingerprint key that will be overridden on extension update.
I'm using an old version of Toggl because I need to use a custom integration (because it's been years and Toggl still hasn't added an official version of the integration I want), and newer versions of the extension don't allow custom integrations.
The text was updated successfully, but these errors were encountered: