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.

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

[gui error report] SyntaxError: Unexpected end of JSON input: #2059

Closed
danielb2 opened this issue Mar 23, 2022 · 2 comments
Closed

[gui error report] SyntaxError: Unexpected end of JSON input: #2059

danielb2 opened this issue Mar 23, 2022 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@danielb2
Copy link

👉️ Please describe what you were doing when this error happened.

Specifications

  • OS: darwin
  • IPFS Desktop Version: 0.20.2
  • Electron Version: 17.1.0
  • Chrome Version: 98.0.4758.102

Error

SyntaxError: Unexpected end of JSON input: 
    at JSON.parse (<anonymous>)
    at Daemon._getConfig (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/node_modules/ipfsd-ctl/src/ipfsd-daemon.js:368:21)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Daemon.init (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/node_modules/ipfsd-ctl/src/ipfsd-daemon.js:158:9)
    at async spawn (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:54:3)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:169:31)
    at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:46:17)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:114:3)
    at async run (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/index.js:83:5)
@danielb2 danielb2 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Mar 23, 2022
@welcome
Copy link

welcome bot commented Mar 23, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@lidel
Copy link
Member

lidel commented Mar 23, 2022

Duplicate of #2050

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

2 participants