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: C:\Users\razak\.ipfs\config: Unexpected end of JSON input #2044

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

Comments

@razakyermal
Copy link

👉️ This error occurs when opening IPFS desktop tool

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.20.1
  • Electron Version: 17.1.0
  • Chrome Version: 98.0.4758.102

Error

SyntaxError: C:\Users\razak\.ipfs\config: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Object.readFileSync (G:\IPFS Desktop\resources\app.asar\node_modules\jsonfile\index.js:52:17)
    at readConfigFile (G:\IPFS Desktop\resources\app.asar\src\daemon\config.js:29:13)
    at checkPorts (G:\IPFS Desktop\resources\app.asar\src\daemon\config.js:223:18)
    at module.exports (G:\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:152:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async startIpfs (G:\IPFS Desktop\resources\app.asar\src\daemon\index.js:46:17)
    at async module.exports (G:\IPFS Desktop\resources\app.asar\src\daemon\index.js:114:3)
    at async run (G:\IPFS Desktop\resources\app.asar\src\index.js:83:5)
@razakyermal razakyermal added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Mar 18, 2022
@welcome
Copy link

welcome bot commented Mar 18, 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 21, 2022

Continued in #2050

@lidel lidel closed this as completed Mar 21, 2022
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