You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With v2.0.0, if I run PiBakery from a volume that has spaces in it, I get the following error:
`
Elevation error
Command failed: /Volumes/Samsung T5 900GB/dev/personal/pi/PiBakery2-darwin-x64.app/Contents/MacOS/PiBakery --rootwriter --socketpath /tmp/k5el7.sock --imgpath /Users/.../Desktop/2019-04-08-raspbian-stretch-lite.img --drive '{"device":"/dev/disk2","displayName":"/dev/disk2","description":"SD/MMC/MS PRO","size":15867052032,"mountpoints":[{"path":"/Volumes/Untitled"}],"raw":"/dev/rdisk2","protected":false,"system":false,"name":"Untitled"}' --require /Volumes/Samsung T5 900GB/dev/personal/pi/PiBakery2-darwin-x64.app/Contents/Resources/app/main.js
sudo-prompt-command: line 2: /Volumes/Samsung: No such file or directory
`
You can see from the last line of that error that it's choking on the first space in the volume name. If I remove the spaces from the volume name, it works fine.
The text was updated successfully, but these errors were encountered:
With v2.0.0, if I run PiBakery from a volume that has spaces in it, I get the following error:
`
Elevation error
Command failed: /Volumes/Samsung T5 900GB/dev/personal/pi/PiBakery2-darwin-x64.app/Contents/MacOS/PiBakery --rootwriter --socketpath /tmp/k5el7.sock --imgpath /Users/.../Desktop/2019-04-08-raspbian-stretch-lite.img --drive '{"device":"/dev/disk2","displayName":"/dev/disk2","description":"SD/MMC/MS PRO","size":15867052032,"mountpoints":[{"path":"/Volumes/Untitled"}],"raw":"/dev/rdisk2","protected":false,"system":false,"name":"Untitled"}' --require /Volumes/Samsung T5 900GB/dev/personal/pi/PiBakery2-darwin-x64.app/Contents/Resources/app/main.js
sudo-prompt-command: line 2: /Volumes/Samsung: No such file or directory
`
You can see from the last line of that error that it's choking on the first space in the volume name. If I remove the spaces from the volume name, it works fine.
The text was updated successfully, but these errors were encountered: