Unexpected string in JSON at position 262
See original GitHub issueI’m getting the following error during auth flow.
[DEBUG] SyntaxError: Unexpected string in JSON at position 262
at JSON.parse (<anonymous>)
at https://browser.blockstack.org/static/js/vendors.1b38d2faab448e4b154f.chunk.js:23:238823
I tried to run my app in Incognito mode… I got the same error, but was prompted to create/restore an account, and that process worked, but I was redirected to Blockstack Browser, instead of back to my app.
In Incognito mode, after restoring my account, and attempting to log in, I got the “Failed to fetch information about the app requesting authentication…” error.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
fixing SyntaxError: Unexpected string/token in JSON at position
Use this syntax highlighter. If using Chrome, paste the offending JSON here to find the relevant offending line (data is kept locally in...
Read more >Unexpected string in JSON at position 608 while parsing
I faced similar issue and my json was valid and structured. This issue was due to invalid package-lock.
Read more >Unexpected string in JSON at position 262 #1858 - GitHub
I'm getting the following error during auth flow. [DEBUG] SyntaxError: Unexpected string in JSON at position 262 at JSON.parse (<anonymous>) at ...
Read more >SyntaxError: JSON.parse: bad parsing - JavaScript | MDN
JSON.parse() parses a string as JSON. This string has to be valid JSON and will throw this error if incorrect syntax was encountered....
Read more >syntaxerror: unexpected string in json at position - You.com
There are two common causes for this. The first is that you may be referencing a non-existent property (or even a non-existent variable...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FFS. Spent over an hour reconfiguring my cors with different servers trying to recreate and it turns out I was missing a comma between icons.src and icons.sizes properties in manifest.json. EBKAC. smh.
The most puzzling bugs are always right in front of you 🙃