Seems to be working good. What I discovered so far:

Dialog boxes for covering the shutter are popping up behind the Ekos tab and Fits Viewer (when open).

The Mount Control popup, that can be opened with the Mount Control button in the mount tab, is too narrow and needs to be resized everytime it gets opened.

So I don't think there is anything we can really do about this. This issue has been there since I first ported KStars to Mac in 2016. Basically, on Linux, there is a concept of parent and child windows and that works very nicely where the child windows will be on top of their parent windows so that the KStars skymap will pretty much always be in the background and the other things will appear in front of it. But on Mac, windows are pretty much independent of one another unless they are like modal dialog boxes requesting user feedback. So, when I first got KStars building on my Mac, I found it very annoying that many windows would go behind the skymap when I would click on the skymap. The best solution that I found was to make all the other windows "always on top" and for the most part this works well. The unfortunate side effect of that is that sometimes a few dialogs will end up behind those windows. But I think that is much better than them disappearing behind the whole skymap which is usually a much larger window, so thats why I did it that way. Its not perfect, but I think it is the best option

Is this a Mac specific issue? I don't think it is related to the Mac build, or related to my build script, this seems to be a more general issue. I can bring it to the attention of others, certainly.

Hy & Rob,
I've done some further guide testing with KStars 351 and KStars 352.
Rob : I added the missing library libASICamera2.dylib to KStars 351 for the ZWO compatibility
Hy : I used both guide algorithms Smart and SEP Multi Star : this is not the origin of the guiding bug. No difference.
Result : you will find the logs at dl.free.fr/mVWNquxeq
- KStars 351 : guiding is no problem
- KStars 352 : guiding is not possible : see the screenshot "scope cannot reach the start point after 21 iterations"

Hy & Rob,
I've done some further guide testing with KStars 351 and KStars 352.
Rob : I added the missing library libASICamera2.dylib to KStars 351 for the ZWO compatibility
Hy : I used both guide algorithms Smart and SEP Multi Star : this is not the origin of the guiding bug. No difference.
Result : you will find the logs at dl.free.fr/mVWNquxeq
- KStars 351 : guiding is no problem
- KStars 352 : guiding is not possible : see the screenshot "scope cannot reach the start point after 21 iterations"

No issues at all - it worked flawlessly. I did notice the filter window being in the background and the narrow mount control dialog as mentioned by other users, but these are very minor issues in my view. Thanks for all the hard work.

Thanks for doing the testing!

That means that whatever caused your problem, it was introduced pretty recently.

It has been introduced between 3.5.1 and 3.5.2.
I thought you did the changes to solve the ZWO issue ?

So the only issue with ZWO was that the single library file that you copied into 3.5.1 was missing so that ZWO didn’t work. I didn’t really do anything to fix the problem, I just made sure to delete the broken link from my build folder when I built 3.5.2.

So I was saying that if you confirmed that 3.5.1 guides fine with the library copied into the app, then whatever is causing your issue must have been introduced between those 2 versions. It should not be StellarSolver or ZWO driver related since those 2 things didn’t change between those versions, so it must be a change somebody made to the guiding code in KStars in the last couple of weeks.

Please tell me how I could help !

At the moment I am not sure since I haven't made any changes since 3.5.1 myself. I will try to let some people know and we will see what they say.