bug: error.log is empty

[SgtPooki]

The error.log is not populated with log data. We have consistently seen reports where users providing their error.log is just an empty file. This is true on my machine as well

examples where error.log was empty:

• Windows: No app for link "webui" #2545

[Jeevan-Kiran-Lenka]

Hey @SgtPooki I recently used IPFS in one of my Blockchain project and I'm fairly new to Open Source, but I would like to work on this issue, can you please tell me how to replicate the issue ?

[SgtPooki]

@Jeevan-Kiran-Lenka thanks so much for the offer!

The only thing I can think of is starting up a separate Kubo instance before starting up IPFS Desktop so you get a repo.lock error. That error should be populated in the error.log at https://github.com/ipfs/ipfs-desktop#where-are-my-ipfs-configuration-and-log-files, but error.log is almost always empty.

However, when you run ipfs-desktop in development mode via npm run start the log files are placed in the project root, and the error.log does get errors (if there are any). So... it's something.. but emitting more errors to error.log, and the stack traces, would impove how helpful we can be for users.