libretro / libretro/RetroArch

Retroarch Webplayer - SyntaxError: JSON.parse

Open
#10,592 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

When installing RetroArch web player following these instructions and accessing the webplayer URL, these error messages are displayed:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
onreadystatechange https://yuno.dev/retroarch/browserfs.min.js:9
    i https://yuno.dev/retroarch/browserfs.min.js:9
    _requestFileSync https://yuno.dev/retroarch/browserfs.min.js:6
    b https://yuno.dev/retroarch/browserfs.min.js:6
    setupFileSystem https://yuno.dev/retroarch/libretro.js:98
    afs https://yuno.dev/retroarch/libretro.js:44
    b https://yuno.dev/retroarch/browserfs.min.js:5
    e https://yuno.dev/retroarch/browserfs.min.js:5
Error: Unable to find listing at URL: ${listingUrlOrObj}
b https://yuno.dev/retroarch/browserfs.min.js:6
    setupFileSystem https://yuno.dev/retroarch/libretro.js:98
    afs https://yuno.dev/retroarch/libretro.js:44
    b https://yuno.dev/retroarch/browserfs.min.js:5
    e https://yuno.dev/retroarch/browserfs.min.js:5

Retroarch won't start and I cannot start a core

Version/Commit

You can find this information under Information/System Information

Environment information
  • OS: debian 9 Strech
  • web server : nginx
  • Browser : Firefox 76 on Ubuntu 18.04

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Emscripten setup instructions and trace setupFileSystem in libretro.js, including the BrowserFS requests shown in browserfs.min.js. Check the response being passed to JSON.parse and verify that the webplayer loads and can start a core without these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nginx
Domain
devops, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.