Etcher: Error: Path must be a string. Received undefined

[daturach]

Hello

I am running the version you sent me on Friday last week while debugging an issue with MySQL.
Etcher-1.0.0-beta.18+4f621f6-win32-x64-MYSQL-FIX
Windows 7, French

Today, I am not able to burn an img file. I am getting this error message when clicking on "Flash":

Can you help?
Thanks

[jviotti]

Hey there @daturach,

Sorry to hear you're still having issue. The path issue you get is weird. Can you open DevTools (Ctrl+Alt+I), go to the "Console" pane, type require('electron').remote.process.argv, press Enter and report back the results?

[daturach]

Result is:
["D:\test\Etcher\Etcher.exe"]

[jviotti]

OK, cool. Can you try editing the file called resources/app/lib/child-writer/renderer-utils.js on line 46 from:

return path.join(CONSTANTS.PROJECT_ROOT, electron.remote.process.argv[1]);

To:

return path.join(CONSTANTS.PROJECT_ROOT, electron.remote.process.argv[0]);

?

Let me know if that's enough to make it work, otherwise I'll upload a new one for you!

[daturach]

It's enough but I have a new message:

[daturach]

Followed by this one:

[jviotti]

Hi @daturach ,

Can you try the following new build: https://drive.google.com/open?id=0B7tkbonGU-RyTGVHa1B3QjQ0MW8?

[daturach]

Hello jviotti

It's looking pretty good. It's burning at about 10MB/s and just completed the process.
One thing I need to check right now: I have a multi-drive supporting different types of cards but I don't see the drives anymore! I will reboot and report back in a few minutes...

Thanks again for your great help.

[daturach]

Tomorrow, I should receive some hardware to test the image.
However, ejecting the card make all drives unavailable. Only a reboot bring them to life again.

[lurch]

However, ejecting the card make all drives unavailable. Only a reboot bring them to life again.

There's a discussion about that in #750

[jviotti]

Awesome, sorry for the custom build mess @daturach. I don't know what happened, all the custom builds usually just work :)

Regarding the multi-sdcard readers issue, this is something we've heard before as @lurch mentioned. Let's continue the discussion there. @daturach Do you mind linking us to the exact adaptor you're using?

[lurch]

Just out of curiosity @jviotti what was the cause of _this_ particular issue (that you fixed with an updated build) ?

[jviotti]

I released a too custom build for him, almost done by hand, and made various mistakes in the way. The particular issue that this user hit was because I didn't package the code inside the asar, and thus the arguments positions that we expect were different, causing weird stuff in both the child writer execution and elevation stuff.

[lurch]

Ahhhh. So a bug in @jviotti rather than a bug in Etcher then ;-D

[jviotti]

Yeah, you're welcome to send a PR! :P