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.

Sign up for GitHub

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

Jump to bottom

Google Voice extension stopped working after 55.2 "Invalid JSON string" #1200

Closed
andrewklimek opened this issue Sep 19, 2018 · 2 comments
Closed

Google Voice extension stopped working after 55.2 "Invalid JSON string" #1200

andrewklimek opened this issue Sep 19, 2018 · 2 comments
Labels
closed/invalid

Comments

@andrewklimek
Copy link

Description

Google Voice extension was working in 55.2 but not in 55.3 - 55.5

JS console shows an error:
Uncaught Error: Invalid JSON string: <!doctype html><html lang="en" dir="ltr"><head><base href="https://accounts.google.com/"> etc etc

I doubt many of you use Google Voice, but I rely on this extension for texting so I was very happy to think I could start using Brave.

Steps to Reproduce

  1. Add extension from https://chrome.google.com/webstore/detail/google-voice-by-google/kcnhkahnjcbndmmehfkdnkjomaanaooo?hl=en
  2. Click extension icon
  3. Select "Inbox" tab in extension pop-up. Notice "Loading..."
  4. Right click pop-up to inspect element and notice console error

Actual result:

inbox tab shows "loading" but never loads. Subsequent clicks on the extension take you directly to the voice website (apparently the extension "gives up". You have to uninstall/reinstall to get the loading attempt & error again)

Expected result:

should load text messages and allow texting.

Reproduces how often:

every time

Brave version (chrome://version info)

Brave | 0.55.5 Chromium: 70.0.3538.16 (Official Build) dev (64-bit)
Revision | 16ed95b41bb05e565b11fb66ac33c660b721f778-refs/branch-heads/3538@{#306}
OS | Mac OS X

Reproducible on current release:

Cannot install this extension on stable release

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? No
  • Is the issue reproducible on the latest version of Chrome? No
@bbondy bbondy added this to the 1.x Backlog milestone Sep 22, 2018
@rebron rebron added feature/extensions priority/P4 Planned work. We expect to get to it "soon". labels Sep 28, 2018
@andrewklimek
Copy link
Author

Now that I can set default shields, the problem is solved by allowing all cookies. I can't find a way to only allow cookies for the extension though.

@andrewklimek
Copy link
Author

It's working in Dev Version 0.57.4 Chromium: 71.0.3578.31

@bbondy bbondy modified the milestones: 1.x Backlog, Dupe / Invalid / Not actionable Nov 5, 2018
@kjozwiak kjozwiak added closed/invalid and removed feature/extensions priority/P4 Planned work. We expect to get to it "soon". labels Nov 5, 2018
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed/invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bbondy @kjozwiak @rebron @andrewklimek