Balena and mac catalina not working

baleina not working w/mac catalina
says my iso is corrupt
i tried multiple iso with same problem

Hi and welcome to the forums,
Can you paste here the logs from the application? You can check them by opening the DevTools Console with cmd + opt + i, this will let us check if there’s any error that we can use as a starting point.
You could also try with another image or if it’s an archive, extract it first.

I have MacOS 10.15 Catalina and Etcher 1.5.59
Before I updated to Catalina, I had the same problem as ubiquity with several different confirmed iso’s
After I updated to Catalina, I get a new message. Here is the screen shot:
17%20AM
Also of note: Catalina only allows 64-bit executables.

For issues with macOS Catalina, check https://github.com/balena-io/etcher/issues/2833 and https://github.com/balena-io/etcher/issues/2911 for some temporary workarounds. We’re working on a PR that you can check here that will solve the new OS issues.
As for the ISO, as mentioned we would need the console logs to investigate further. If it’s zipped, try extracting it if you want to give it another try as there are some ISOs that might not be correctly recognized when inside an archive.

I used the work-around in 2911 and it worked as far as getting Etcher to run. Now it’s back to rejecting anything I try. I extracted a .xz file to an .img file, but as before, no files are accepted.

If you need console logs, please give a detailed procedure to get them. I didn’t see anything right off with cmd + opt + i

I hit my ‘reply’ limit, so here is what I got:
sudo -s
cd /Applications/balenaEtcher.app/Contents/MacOS
./balenaEtcher
2019-10-21 10:37:57.836 balenaEtcher[28671:2401890] *** WARNING: Textured window <AtomNSWindow: 0x7f8bd0de4780> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow’s -titlebarAppearsTransparent=YES instead.
Checking for update
ready-to-show: 7693.695ms
Generated new staging user ID: 39b5251a-4e3d-5d43-9582-97c07daeb39c
Staging percentage: 0, percentage: 0.4909469849641777, user id: 39b5251a-4e3d-5d43-9582-97c07daeb39c
Update for version 1.5.59 is not available (latest version: 1.5.60, downgrade is disallowed).
2019-10-21 10:38:27.871 balenaEtcher[28671:2402394] Persistent UI failed to open file file:///var/root/Library/Saved%20Application%20State/io.balena.etcher.savedState/window_2.data: No such file or directory (2)
Checking for update
Staging percentage: 0, percentage: 0.4909469849641777, user id: 39b5251a-4e3d-5d43-9582-97c07daeb39c
Update for version 1.5.59 is not available (latest version: 1.5.60, downgrade is disallowed).
bash-3.2#

It worked, but you got some interesting errors about upgrades.

Then I think you should try running Etcher with sudo as suggested in 2833 because even though the application runs, unfortunately it needs some more permissions for Catalina.
To gather logs: you can open the DevTools with cmd + opt + i: it should open a new window where you can switch to the Console tab; there you’ll see a bunch of logs with timestamps and events, one of them should be the error that just happened.
If you don’t see anything valuable at a first glance, you can just copy whatever you see there and paste it here

I just downloaded the balena app for the first time and a fresh copy of raspbian buster lite on my macOS 10.15 Catalina imac. I hade the exact same error as ‘duggabe’.

I then downloaded the same on my second mac which is still running macOS Mojave, 10.14.6.

Now I had no issues flashing the device.

Clearly there is something with the Catalina OS that’s not compatible and causing issues.

@keimps You will need to run Etcher as sudo as mentioned in this issue on GitHub and previously in this thread.
This is a temporary workaround while we work on the notarization of the application, which needs to be done for the newest macOS Catalina for which we have a PR up in the repo

Thanks for your answer. I already worked around it myself, just wanted to add my findings, in case that helps the investigation.

Hi there! This should be fixed in version v1.5.61 more info