That has happened to me when I've forgotten to change the OS targets for (1) all the xibs and (2) the project itself. But it sounds like you've got all that covered... -Carl

Can anyone explain this? I’m getting the following warning in my build: But when I look at the file info for that .xib file: And the deployment target in the target as a whole: Am I missing

I have an iOS app (iOS 12.4+) which did work on iOS 12.4 … iOS 13.2 when build with Xcode 11.1. Now I have upgraded to Xcode 11.2 and the app no longer works on iOS 13.2 devices. When I

On Mon, Nov 4, 2019 at 03:52 AM, Sak Wathanasin wrote: That and the dozen or so pop-ups asking for permission that appear as soon as our app launches - all it does is condition the user to press

Yup; in our manually-signed app, we just set it to "none" from the pop-up Completely agree - we use a python script, but whatever works for you I've spent days, if not weeks to get our CI build to

I have an app that can launch apps and scripts. A script might target any app, so I can't use com.apple.security.temporary-exception.apple-events and add an app identifier for every possible app in

I don't have an answer to your particular situation, sadly, but man do I understand your pain! I can only mention two things: -As far as I understand, provisional profiles are not required for Mac

This isn’t, by any chance, one of those “ancient” apps that use an app ID whose prefix ISN’T your developer team ID? If so, that might have something to do with why it doesn’t work.

I checked that, and it’s turned on in the build settings. There’s another oddity, which is probably the real cause. In “signing and capabilities”, I have it set for Xcode to manage

I had no problem in Xcode 10, but in the one project where I turned the hardened runtime on for the first time in Xcode 11, I had to make sure it was on in Build Settings as well as in the Signing &

I'd love to know too: I discovered it "emprically", as they say; i.e. much hair-pulling, swearing and cursing was involved. Lock/unlockfocus was the recommended way of doing things and our legacy app

Thanks, that was it. Just for the peace of my mind ... why? ---markus---

Try removing the lockfocus/unlockficus - I had to remove them from all my custom widgets to get them to work in 10.14. Regards Sak

There are a lot of things that need to be done to do drawing right, and any drawing should be done from within a view’s drawRect: method or eventually called by it. Once a view’s drawRect: method

I have written a small Cocoa program that works in High Sierra but stopped working in Mojave. The program loads a graphics file from disk and displays it full screen. At the bottom it should write the

The Notarization process is recursive, in that it works its way down the application structure and checks each part as it goes. If you have applications embedded in your app it will check those, and

I misspoke - I’m not using Sparkle. I’m using Devmate - I thought that used Sparkle internally, but I’m not sure. Anyway my other app that uses Devmate notarizes with no issues. I cannot see any

Yes ,this is what it says, which is what I said in my original message here 2019-11-01 03:54:51 +0000 Distribution items ineligible: Error Domain=IDEDistributionMethodDeveloperIDErrorDomain Code=1

Have you checked the Notarization report? That will tell you exactly why it failed. Jack

Yes, have you turned on hardened runtime for the AutoUpdate app? Are you building Sparkle from source within the app project, or building it as a separate framework? What's different between the two