Suite 1.5.5 - New Mac DMG is Corrupt (ZIP is OK)

[spoke2570]

The dreaded Error -36....

The Finder can’t complete the operation because some data in “Ethos Suite.app” can’t be read or written. (Error code -36)

Both of the last 2 images work fine, but this one is not so good. Standard drag and drop using the shortcut in the mounted image, and manual drag and drop.

[Nicholas-Luoyi]

Sorry. I cannot understand this one

[mgsanna]

Same here on MacBook Pro intel, the .dmg is corrupted,

same error of @spoke2570

But the zipped ethos suite works... installed manually....

[kramgrand]

Hello Just for info, I usually install the latest using the .dmg download option rather than update. I loaded from the .dmg early yesterday morning without any issues. MacBook Air M2 Regards Mark.

[LeoCheung123]

Same problem here. Error -36. MacBook Pro 2023 running Sonoma 14.4.1

It also removes the existing version of Ethos Suite (v.1.5.0 which was functioning fine). Which is a little inconvenient.

[kramgrand]

Just for the shear hell of it, I downloaded it again to reinstall over the top of the existing. It's broken...

[kramgrand]

Thought you might be interested. I restored my original download of the .dmg via Apple TimeMachine and it worked without error. Could the copy on the server somehow become corrupted?

[spoke2570]

The zipped version works perfect. Restore is working. It takes a while for Suite to recognize the drives after the OS has them, but its working well.

[dap35]

I ran into the same issue with downloading the dmg file and attempting to install. The zip file is fine.

[tysonfromcanada]

same here, m2 air

[Vermaarp]

same issue in my mac m1

[Nicholas-Luoyi]

It may be a package issue. Would you please try the latest one?

[spoke2570]

The new package works. Manual authorization of the app was not necessary. Backup and Restore functions work correctly. Model images seem to resize for the different window sizes better. So far about 10 openings and closings with no weird "quit unexpectedly" warnings after the app has been closed using best practices. -> The install was a little notchy requiring to manually quit Suite, transfer the package to the Apps folder, open the app. (see image)

-> It took a seriously long time for the package to move the package from the mounted disk image to the app folder. (several minutes)

Conclude: 1.5.6 seems to work correctly, but the best Suite Update experience still was going from 1.5.0 to 1.5.1. The update was announced by the app at open and the update was seamless with no manual operations required except to initiate the update from the alert window within the Suite app.

I would love to see suites basic operation be a marriage of the solid operation that I have seen with Suite 1.5.6, the update speed of most previous versions, and the seamless update operation from the 1.5.0 to 1.5.1 update.

I consider this issue closed, but I will let Nicholas close this thread.

[Nicholas-Luoyi]

Thanks for keeping testing and contacting! It seems that everyone has his/her preference. Because for me, I do like the update notification won't disturb me. So I think the best choice is to leave the choice to the user. I will add selection like "auto install / manual install"

[spoke2570]

The pictured result is sort of the worst of both worlds. I pressed the "install update" button and the downloaded image mounted, opened. Suite is still open behind this. So choosing the most obvious path of dropping the app on the provided shortcut results in failure because the Suite is still open. Ya I would close Suite first, but that is not what the screen is implying.

It was nice not to manually approve the app.

I feel like the 3 options should be to download the package or install the package or cancel the operation. That way there is clear expectation of what happens when a user hits the button.