MacOS App In Zip Instead Of Installer

PointsWell

As a Mac user I have to say this is probably the most disappointing development with AIM.

Previously the installer would (inconsistently) maintain config files (such as BASServer.props). This route of zip files now makes an already not great upgrade experience worse by reintroducing overheads that had slowly been taken away.

BLOMASKY

And, what about our CUSTOM folder that has all the stuff that Aware does NOT touch?????

Bruce

BLOMASKY

I have a MUCH better idea. Lets get rid of the Windows version of Aware! That way, if we all use the Mac Version, it will start to get the TLC that it deserves.

On a lighter (maybe) note. Wonder if anyone has worked with the SQL EDGE version of SQL server. Says its designed for IOT but I have started to use it on my shiny new MBP with the Apple silicon and using Docker with SQLEdge.

On an even lighter note. I am using SQL grease (about 90 bucks a month, but has a free version) for helping me identify SQL performance issues. The price is right and it works!

Bruce

aware_support

We understand your frustration and apologize. For the moment keep your custom stuff separate before updating.

The problem is that the new version of Mac OS refuses to create an application by the Installation program and says that it cannot register it with the Gatekeeper. After spending days on this we gave up. Probably requires us to go through the painful process of publishing the app in the Apple AppStore.

PointsWell

aware_support wrote
Probably requires us to go through the painful process of publishing the app in the Apple AppStore.

It requires the installer to be notarised. I raised this as a Feature Request in 2019 when it was a voluntary step, but likely to become more annoying. It is now at the annoying stage it seems.

https://www.awareim.com/forum/d/11401

https://support.apple.com/en-us/HT202491

aware_support

Yes, I guess, we'll have to go through this pain.

On a more positive note, the new build will fix a Mac-specific bug where the Standard View of rules was always the first to open even if you last worked with the Textual View

chris__29

On a more positive note, the new build will fix a Mac-specific bug where the Standard View of rules was always the first to open even if you last worked with the Textual View

YAY!!

PointsWell

aware_support wrote
On a more positive note, the new build will fix a Mac-specific bug where the Standard View of rules was always the first to open even if you last worked with the Textual View

That's good.