Yeah, that’s the old Henny Youngman line: “I said to the doctor (raising arm or something), ‘It hurts when I do that’–he said, ‘don’t do that’.” 
1 Like
If Xojo is loading all the plugins and then resolving later it is presumably loading using RTLD_LAZY?
I did find this when I looked a while back to see if anyone else is having issues:
https://developer.apple.com/forums/thread/689991
That was a year ago, mind. However, it does point to only some uses of dlopen causing issues.
No symbols in plugins do not work like that.
There is only one symbol per see which is the Entry point.
Rest is all handed over by calling the entry point. And that is the part that is done later after order stopped to matter.
Yes, but surely one plugin that uses another must resolve the entry point. If not that’s fine, I just saw it and thought it could be helpful. I’ve never built a plugin at all.
No even that is not done directly. Its all done through callbacks into the Xojo engine.
Fair enough.
News?
This week is thanks giving in the USA.
All developers at Apple seem to be on vacation.
Don’t expect something before mid next week.
That’s weird. Support teams of big techs are supposed to work 24/7. Only less people active on holidays but some teams are always active.
Poor Apple. Don’t have enough money to pay extra bonus for teams covering holidays and keeping the company running, I hope they never have a 0-day flaw occurring while the company is empty. 
I’m sure they have a skeleton crew working for important stuff. I mean, my company is pretty much shut down for ThanksGiving too but we have people still working and taking care of priority items. But we aren’t fully-staffed by any means so that’s the sort of message we give out to customers too.
1 Like
Here lies the difference. Big techs MUST BE fully-staffed and non-stop.
I’m not aware of a similar stop by Microsoft, for example.
If USA goes for a holiday I bet a skeleton crew + some remote Asian team will keep it going.
I don’t believe that for a second. They are just not advertising the fact. This is a 2 week period where a LOT of people around the world take time off - it’s not just the USA. My international calendar is full of holidays for our staff in the various countries we operate. And come the last 2 weeks of December it’ll be the same thing.
And I’m sure it is. The entire South America and Asia is working non-stop right now, unless some company have ONLY business with US companies. That’s kind of less than 0,001% of the companies?
But yes, the last 2 weeks of December we will slowdown, but not close.
While I dislike having the dlopen function crash for me and my users, I must be honest enough to admit, that on Apple’s scale, this is not an important thing to fix for them.
MacOS 13.0 still has probably a couple of bigger issues on the plate, but I do hope, they will look into this in December. And then, if we are lucky, maybe get a fix in an update for early 2023.
or they just tell me to change an option for linking and that may help.
It’s sad to say clients I can’t release a Ventura compatible app this year because Apple has a bug that makes my compiler unstable and my apps probably will crash randomly.
What does stop you from building your app on macOS Monterey?
And what does your app stop from running on Ventura? Does your app load 500 dylibs?
1 Like
As a developer we probably all here know that a new OS version has it‘s bugs as any other software. So don’t update your/all development machines asap. Why should you?
1 Like
Nothing. But the unstable resulting app made anywhere else but installed under Ventura is the real problem. I can’t say it has support and must say DON’T TRY to install Xojo apps on Ventura because right now it has known unstable and random issues.
Nope. But as we know, there are reports that loading like 4 causes crashes too.