Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error parsing Info.plist at launch

See original GitHub issue

Etcher version: v1.0.0-beta.18
Operating system and architecture: macOS 10.12.3 Beta (16D30a)

The following error appears at launch:

Error: 2017-01-17 09:27:25.354 diskutil[12682:4102330] There was an error parsing the Info.plist for the bundle at URL <0x7fb6d4c09800>: NSCocoaErrorDomain - 3840
2017-01-17 09:27:25.508 diskutil[12719:4102412] There was an error parsing the Info.plist for the bundle at URL <0x7fb0781010b0>: NSCocoaErrorDomain - 3840
2017-01-17 09:27:25.683 diskutil[12758:4102505] There was an error parsing the Info.plist for the bundle at URL <0x7fb9d4c037c0>: NSCocoaErrorDomain - 3840
2017-01-17 09:27:25.806 diskutil[12799:4102581] There was an error parsing the Info.plist for the bundle at URL <0x7fa011413e60>: NSCocoaErrorDomain - 3840
2017-01-17 09:27:25.928 diskutil[12836:4102642] There was an error parsing the Info.plist for the bundle at URL <0x7ff683c033b0>: NSCocoaErrorDomain - 3840

    at childProcess.execFile (/Applications/Etcher.app/Contents/Resources/app.asar/node_modules/drivelist/lib/scripts.js:90:23)
    at ChildProcess.exithandler (child_process.js:209:7)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:493:12)

I’d be happy to help debug the problem. I’m not sure if it’s related to the beta OS I am running.

Issue Analytics

State:
Created 7 years ago
Comments:22 (14 by maintainers)

Top GitHub Comments

2reactions

jviotticommented, Jan 30, 2017

Done: https://github.com/resin-io-modules/drivelist/pull/137. I’m using the https://github.com/visionmedia/debug module to print the scripts stderr to (the parent process) stderr if debug mode is enabled. I’ll enable this on Etcher once that PR gets merged and we will see stderr in DevTools.

1reaction

jviotticommented, Jan 18, 2017

Thanks a lot for the investigations @jspencer. While this is definitely an OS bug, invalid YAML pairs (e.g: the output you see in the middle of diskutil output) should already be ignored by default (see https://github.com/resin-io-modules/drivelist/pull/99), so this issue shouldn’t happen anyway. We’ll investigate!