-
-
Notifications
You must be signed in to change notification settings - Fork 5
Account switching stops #9
Comments
The error is from the |
I disabled the extension and the error persists. My rules are |
I see tons of messages (several per second) like the below in the service worker console: |
Turned on error collection and saw this: Uncaught (in promise) Error: Extension context invalidated. |
I logged out of all accounts, cleaned all github cookies, removed all rules. Then i logged in again (through the extension) and created the rules. I've done this before and after a while the extension stops working. But this time I also looked at the console and see |
This just happens again, now there's no infinite loop in the service worker, instead, I see that ittayd is selected even though the URL matches one of the other patterns. Could it be the account attribute that appears in the conditions in console? |
Note that even though 'ittayd' is selected, when I load the repository I get a "Confirm your account recovery settings" window and after I confirm there are errors |
Deleting cookies and reloading the page doesn't help |
I removed the .* rule and can't manually switch to ittaysw at the home page or otherwise. |
@ittayd, Can you provide the accounts you want to switch? So that I can give help on the auto-switching rules. |
ittaysw and ittayd (those you can see in the thread) |
I'm afraid the rule |
But if I don't have this rule then the profile will never auto switch to ittayd. After it switches to ittaysw, I'll need to manually switch to ittayd. |
It might be because the
Back to your problem, if you have two accounts, you could define two rules for auto-switching. You can define one regexp for one account. And define a regexp, which is the opposite of the previous one. Then auto-switching rules could work. If you can describe all the conditions, I could try to give the regexp. |
So allow me to set the priority of rules, or, set the priority by their visual order in the plugin's dialoge. I'll try the opposite regex thing |
I now see the error |
The syntax of the But I didn't see any error for your regexp. |
I think there's a bug in the code somewhere that makes the extension to stop selecting the right rule. |
Note that after the bug happens I can't switch manually (the door icon in the extension) or exit an account (the x button) |
When I right click the extension and choose "inspect pop-up" and go to the Application tab, the session and local and shared storage seem to be empty |
Even if I remove the 'ittaysw' profile from the extension, it loggs me as ittaysw. I delete all github cookies and load the homepage and it logs me as ittaysw (i disable it, remove all cookies and load the homepage and am not logged in) |
And now I see the profile is back in the extension... |
I managed to remove the profiles from the extensions. In github try to login, get an error page. Disabled the extension, try to login, works fine. The extension probably has a bug where it keeps a mangled login in storage somewhere, which it tries to apply, but fails. |
After some time (a day or so) of running, the extension stops switching accounts. Not via rules nor manually.
I don't know how to analyze this. In the console I see this:
lockdown-run.js:17 Lockdown failed: TypeError: At intrinsics.Object.groupBy expected boolean not function
at isAllowedPropertyValue (lockdown-install.js:1:53384)
at isAllowedProperty (lockdown-install.js:1:53807)
at visitProperties (lockdown-install.js:1:55095)
at isAllowedPropertyValue (lockdown-install.js:1:53041)
at isAllowedProperty (lockdown-install.js:1:53807)
at visitProperties (lockdown-install.js:1:55095)
at lockdown-install.js:1:55523
at repairIntrinsics (lockdown-install.js:1:144597)
at lockdown-install.js:1:145462
at lockdown-run.js:4:3
(anonymous) @ lockdown-run.js:17
Show 1 more frame
Show less
lockdown-more.js:99 Protecting intrinsics failed: ReferenceError: harden is not defined
at lockdown-more.js:69:13
at Set.forEach ()
at protectIntrinsics (lockdown-more.js:44:22)
at lockdown-more.js:97:5
(anonymous) @ lockdown-more.js:99
Show 1 more frame
Show less
VM1245:11 Refused to get unsafe header "6"
t @ content.min.js:137
(anonymous) @ content.min.js:151
(anonymous) @ VM1245:11
l @ inpage.js:17
c @ inpage.js:17
(anonymous) @ inpage.js:17
(anonymous) @ inpage.js:17
85 @ inpage.js:17
i @ inpage.js:1
(anonymous) @ inpage.js:1
(anonymous) @ inpage.js:1
(anonymous) @ inpage.js:1
1.../../shared/modules/provider-injection @ inpage.js:1
i @ inpage.js:1
e @ inpage.js:1
(anonymous) @ inpage.js:1
(anonymous) @ contentscript.js:1
1.../../shared/constants/app @ contentscript.js:1
i @ contentscript.js:1
e @ contentscript.js:1
(anonymous) @ contentscript.js:1
Show 7 more frames
Show less
VM1245:11 Refused to get unsafe header "6"
t @ content.min.js:137
(anonymous) @ content.min.js:151
(anonymous) @ VM1245:11
l @ inpage.js:17
a.setDefaultLevel @ inpage.js:17
(anonymous) @ inpage.js:1
(anonymous) @ inpage.js:1
1.../../shared/modules/provider-injection @ inpage.js:1
i @ inpage.js:1
e @ inpage.js:1
(anonymous) @ inpage.js:1
(anonymous) @ contentscript.js:1
1.../../shared/constants/app @ contentscript.js:1
i @ contentscript.js:1
e @ contentscript.js:1
(anonymous) @ contentscript.js:1
Show 7 more frames
Show less
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
Refused to load the font '' because it violates the following Content Security Policy directive: "font-src github.githubassets.com".
The text was updated successfully, but these errors were encountered: