Please add to this thread if you have any useful tips for using Catalina with your Xojo projects.
Here are a few to get started:
Quality: I find catalina (as of beta 3) to be very rough and would not recommend it for a production mac. A surpising amount of bugs considering apple has made this beta public. Recommend you use it on a separate mac for testing.
Screen Sharing: My main mac is 10.14, and I wanted to remotely control my Catalina mac using Screen Sharing. However, the catalina mac doesn’t show up in the finder in the “Locations” sidebar. However, if you click Finder/Locations/Network, then the catalina mac does show up, and you can double-click it, at which point you’ll get the “Share Screen” button, which does work.
Catalina is requiring notarization for Apps & DMGs, but only those created after 1 June 2019. Also, this notarization requirement only applies to files that are quarrantined (e.g. files received via download, iMessage, as an email attachment, etc.) See https://forum.xojo.com/54329-dmg-notarising-and-future-macos
I realize that, and that was the point I tried to make… Nobody should ever even consider using BETA software for a production project. I personally never even look at “Betas”… I don’t have the temperment to do what needs to be done, and yet spend time doing QA.
Plus any “tips” would just be workarounds to situations which hopefully would be solved by the time the first Release appears
This did not come true with Mojave. I reported bugs early that Apple did not fix. The knowledge that (A) the bugs had been reported (by me) and (B) Apple was making no efforts to fix them as the betas went along, was important to my planning; the workarounds became the solution by necessity.
It’s possible to install Catalina beta on a separate volume on your mac - apparently with APFS it’s much easier since you don’t have to pre-reserve any space. As always, this is dangerous, so backup first. See https://support.apple.com/en-us/HT208891
Michel, can you ask your customer to re-test with Catalina beta 5 (just released) when it goes Pubic beta and see if it’s working now? Indications are that they may have fixed all of this. (same question for your own testing).
One thing that’s still not clear to me is whether notarization is required at this point, as long as your developer certificates for application and installer signing haven’t yet expired. Somewhere else, I’d read that the absolute requirement for notarization doesn’t kick in until you need to create new certificates (or, for certificates that were created after June 1).
Another way of putting it: the way I’ve understood it is: as long as your certificates are valid; and they were issued prior to June 1; then you can sign with them as usual but you’re not required to notarize.
@Dave Miller: I haven’t gotten any warnings of the type “your app can’t be checked for malicious code” in Mojave. In Catalina I got those for instance for the MBS plugins. So you really want to get your notarization sorted out before Catalina. IMO this is the most stupid warning from Apple I have ever seen.
[quote=448286:@Michel Bujardet]OK. Just tried, f.launch with apps is still broken for apps generated with 2019R1.1 and below.
Guess we will have to wait for R2.[/quote]
This is still strange, for me. I don’t have a Catalina bootable set up to test at the moment, but I did, briefly, with Catalina Beta 3. At that time, I was testing some existing applications that launch others, and I didn’t run into problems getting them to work. I don’t think I’m remembering this incorrectly. There are 2 places in an application suite where one launches another with FolderItem.Launch and I’m 99% sure they worked.