I finally got 3.7 running on my old 2012 MacMini.
I used OpenCore to modify the Mac to support and install Mac OS 15 Sonoma.
Since I will not use this Mac fr any other use - it may solve my problem. I'll be testing with KStars as soon as I get it all reconfigured with all my gear.

Peter

Ok, KStars 3.7 is working well under Sonoma on a modified old Mac.
However, as of right now I am unable to get the USB/SERIAL adapter to work which is needed to control my AAG Cloudwatcher weather monitor.

I *think* I've fixed the indi-canon driver causing Kstars-Mac- 3.7 to crash. In checking the other drivers in the Mac OS directory they all got an Apple error as bad, and needed to be 'trashed.' So i finally 'believed' the warning from Apple.

I presume problems in the INDI drivers (links?) in Mac OS Directory, came from the 3.6.9 beta version when this problem seems to have started and the INDI contents were simply copied into the install of 3.7 and not replaced.

I deleted the entire directory and re-installed Kstars 3.7 (putting it on the desktop instead of the App directory) and Kstars now connects to my Canon 6D and operates the shutter normally w/o crashing 3.7. Won't be able to check the plate solving problem I had on an older version until dark, but *it should* work...

One thing to note is that on starting EKOs connections a 'new' message box appears asking if you would allow server connections? But the msg. box appears behind the INDI and EKOS windows, so if you don't know its popped up you won't clik yes to allow the (I presume INDI) server connection. This happens with several other 'warnings' and messages, like do you really want to goto the Sun if solar observing? Mount won't move until you find that msg. and hit yes. And of course the mount control box always is hidden until you move other open windows and clik on it. Always been a real annoyance to have to go 'looking for' for them!

Just tried out Kstars 3.7 w/ re-loaded Mac OS Inidi driver directory, per previos post, but this time in my observatory with mount and focuser also connected.. Disgusted to say, it again is crashes 3.7 immediately when the Canon M50 is fired in the camera module. It opens fine, connects to mount and M50 in INDI, window but does not recognized in the Camera module and when the 'shutter' is fired Kstars crashes. Running on an M1 Macbook Air with Sonoma. Apparently something is very wrong in EKOS with communicating w/ the
INDI drivers.

Useful thread, thanks to all for the posts: I have similar issue here - Kstars 3.7 crashes (never really starts that is) on a Mac Mini M1 (OS12.7 Monterey) but 3.6.6 runs fine. A New Macbook air M3 (OS 14.3 Sonoma) runs 3.7 fine and 3.6.6 fine... hope that info is useful to someone. I'm somewhat reluctant to upgrade the Mini to Sonoma but I might bite the bullet and hope it doesn't do anything untoward!

Hi
The same thing happens to me on my MacBook Air with OS12.7 Monterey, unfortunately I had to switch to one with Windows to be able to use Kstars/Ekos 3.7
Best regards

Same here... KStars 3.7.0 crashes and does not even start-up on Intel-iMac with Ventura 13.6.6.

This is what is in the crash log:

Yes, as indicated prior to this, unfortunately there was a craft (KDE Craft) issue when I built the DMG for the last version. The issue appeared to be that some code needed for KStars, specifically related to Qt Quick, was compiled on the Craft binary server in a way that it could only work on macOS Sonoma. It certainly would not be my intent to have KStars just work on Sonoma and I hope that we can resolve this, but after I returned from the Eclipse, when I tried to rebuild KStars and hopefully fix the issue, I found that the Craft binary cache had fully switched over to QT6, so to build with QT5 is now much more difficult. KStars has not updated to using QT6 yet, so when I tried to build a new DMG it took very very long and there was a problem. I did not have time to look into it at the time. I haven't had time to try again since then, sorry, so it might take some time to get a new DMG that will hopefully work on older versions of MacOS again. We might have to update everything to Qt6 before we can release another one, I am not sure yet.

Sorry about the delay. The good news is that a new recipe is in the works and daily builds will hopefully start up again soon, but we might have to resolve this QT6 issue before that happens.

As an 'interim' workaround, would it be possible to put up an older pre-3.6.9 and 3.7 version that we could download and reinstall so that we have 'something' that works? thanks.

Absolutely! All previous kstars versions are always available hosted on the indi website going back for a decent number of Versions.

www.indilib.org/jdownloads/kstars/kstars-3.7.0.dmg

You can just edit the numbers at the end of this download link and you should get the older versions. I am not sure if Jasem has a list somewhere. I do have a bunch of the dmg files that I built over the years archived if one or more are no longer hosted there, but the last time I checked, a bunch were there.

Thank you, for figuring out and acknowledging the issue. There is bad weather here now anyway .

I can confirm, KStars 3.7.0 runs just fine on my MBP - M1Pro - Sonoma 14.4.1, but not on my older Intel-iMac with Ventura 13.6.6.

I will try to go back to the previous version using TimeMachine.

While being on the KStars macOS subject. I have an Avalon StarGO2 mount. Avalon Instruments recently release the new "INDI 3rd party AvalonUD" driver for INDI 2.0.x. I noticed these drivers are not installed on macOS with KStars, although they are part of the INDI repository. They can be installed on LINUX-based systems like StellaMate or via a local compilation script. Is there an easy way to get these with KStars?
I can use the remote drivers on the StarGO2 RPi4, but it would be good to have them installed as well locally on macOS.

Hello Rob my name is Ettore.
I had the astrofilo66 account now banned and I don't know the reason, I wrote an email to Jasem two weeks ago without getting a response. I have a Mac with Sonoma but Kstars 3.7.0 doesn't start, it says corrupt file