Website domain changed - extension no longer recognizes it

[navara]

The application domain changed to https://app.ynab.com/ and since then extension doesn't recognize it.

[navara]

Replacing youneedabudget.com for ynab.com in "c:\Users\USERNAME\AppData\Local\Google\Chrome\User Data\Default\Extensions\lmhdkkhepllpnondndgpgclfjnlofgjl\3.5.0_0\manifest.json" and restarting Chrome, while having Developer mode enabled, works as a workaround.

[kathekon]

Unfortunately, suggestion didn't work for me (I'm on a mac).

For other mac users, who want to give it a shot, the file is here: /Users//Library/Application Support/Google/Chrome/Default/Extensions/lmhdkkhepllpnondndgpgclfjnlofgjl/3.5.0_0/manifest.json

[crytting]

It isn't working for me either. I'm using brave and found the correct extension, but the json change didn't do anything.

[navara]

As mentioned above, I also have Developer mode (a switch in Extensions) enabled, so I don't need to update the checksum or sign it with the certificate (and it does indeed throw errors about it). The browser used is the current Chrome.

I would attach a modified manifest, but Github doesn't like it.

Line 14:       "matches": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],
Line 20:    "host_permissions": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],
Line 43:       "matches": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],

[axenstarr]

replacing as in delete it? What do I repalce it with? I tried deleted it but that did nothing... so I restored it from the recycle bin.

[axenstarr]

As mentioned above, I also have Developer mode (a switch in Extensions) enabled, so I don't need to update the checksum or sign it with the certificate (and it does indeed throw errors about it). The browser used is the current Chrome.

I would attach a modified manifest, but Github doesn't like it.

Line 14:       "matches": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],
Line 20:    "host_permissions": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],
Line 43:       "matches": [ "http://*.ynab.com/*", "https://*.ynab.com/*" ],

I addd those lines to the json file but no change. I kept the default ones though does that matter?

[renancouto]

Unfortunately, suggestion didn't work for me (I'm on a mac).

For other mac users, who want to give it a shot, the file is here: /Users//Library/App
lication Support/Google/Chrome/Default/Extensions/lmhdkkhepllpnondndgpgclfjnlofgjl/3.5.0_0/manifest.json

I think Chrome has some sort of caching there that doesn't pick up manifest changes (security reasons?).

What I did to get it working on a Mac was to go to the extension page (chrome://extensions/?id=lmhdkkhepllpnondndgpgclfjnlofgjl), turn "Site access" off (it was only showing the old domain, even after I've changed on the manifest), restart Chrome, and then manually turn it on the new domain entries. After all of that, refresh Ynab to have the extension working again.

[nzifnab]

Duplicate of #3067 and fixed by #3068 ; this fix has been merged in it looks like.

[navara]

I addd those lines to the json file but no change. I kept the default ones though does that matter?

I've replaced the old domain name with the new one, those are the affected lines and their new content.
Chrome had to be restarted, to pick that change and indeed I had the same duplicate experience as @renancouto, did work for me even without unchecking the old domain name.

But we got fix now, so it's just a matter of time, even if this doesn't work for you :)