Closed Jaxx7594 closed 10 months ago
Hmmm. That's interesting, it seems to work for other people (including myself), so if you manage to work out how to reproduce it or fix it yourself that would be greatly appreciated.
school just ended, on bus home rn, will be able to try fix it when I get home to my pc in an hour or so
Do you know if theres any problems with portability? I built it on a usb and installed it on a portable browser
I haven't done any testing, but I wouldn't think that it'd be an issue.
Interestingly enough, I just downloaded ungoogled chromium for testing, and it doesn't seem to work at all for me :O
So there'll be a bit of fixing to do!
Are any connections to google services being made? Cause they'll all be blocked
The extension does call: chrome.storage.local.get
, and then we get the error Uncaught (in promise) TypeError: Cannot read property 'then' of undefined
for a start.
I think any local api's work, just doesnt allow transmitting data to google. Has the extension been tested on normal chromium? Might just be a problem with chromium itself rather than the ungoogled version
Srry 4 delay, my parents loaded me up with gardening chores n stuff, only just finished, will probably only try to fix it tomorrow cause im exhausted
@SethBurkart123 enabling cookies fixes the localstorage error, idk why though, ive never made a browser extension before so i'm not very familiar with how it all works. Its still broken though, just diff error
Ok, that's a start! We can work on this.
it seems your latest update fixed the chrome store version, but didnt fix the version built from source. the folder build/interface (the one that the browser tries to access but cant) and everything inside it just isnt created, idk why
also, that error I showed above seems to not affect anything. it happens on the chrome store version too occasionally, but nothing breaks
I tried ungoogled chromium and It is giving me the same error as you got
Hey guys, I thought it might be worth mentioning as I stumbled across this on StackOverflow some days prior, that Ungoogled Chromium's default extension policies (what extensions can and can't access/do) (chrome://policy
) are different to normal Chrome's policies.
Could this be the problem?
It might be messing with the Chrome/Chromium policies in order to remove Google spyware.
It looks like you might need to change some flags in order to get Chrome Webstore Extensions working (?)
See: https://github.com/NeverDecaf/chromium-web-store and https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq
Thanks @Crazypersonalph for reminding me with a notification, completely forgot about this. Seems this issue was caused because of undocumented steps for building (#50). Doesn't seem like browser policies are messing with the extension, but I'll test it on an unmodified ungoogled chromium install in a sec.
Yeah its working just fine now, closing this issue
When I click the settings button, it pops up with the generic file not found error. Would try to fix it now, but I'm in the middle of school.