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

Yes, I have Sparkle and some 3rd party frameworks. I’ve checked the box that permits these to be loaded even though they’re signed by another developer. I have another app with much the same

Have you got any helper applications (including those embedded in Sparkle or other frameworks)? Chances are it's actually complaining about one of those. - Jon

Hardened Runtime is not currently a requirement for Notarization, but it appears that you have to submit the app using the command-line tool for notarization to happen properly. All my attempts at

I have an app I’d like to notarize for distribution outside the app store. To do this, it requires the hardened runtime entitlement. I have added that in the project settings. When I try and submit

Then check the certificates and profiles in the signed package(s). I use a cery and profile inspector that someone wrote for Spotlight and is on Github.

Maybe this helps: Code to decode mobileprovisions https://github.com/below/cgjprofile Von meinem iPhone gesendet

Alternatively, run this on the command line to strip the security message container and signing from the contained plist: ``` security cms -D -i path-to.mobileprovision ``` I did some research into

Find …/Your iOS.app/embedded.mobileprovision, open in some editor and delete the first 62 bytes, so that it starts with: “<?xml version="1.0" encoding="UTF-8”?>” Save as:

In our case, these apps are just for internal development purposes, such as student projects and the like. It's nice to be able to showcase them each semester, but the iPad apps always expire, and

There are some signing options where if you are part of a TestFlight team, your install will last for a certain time. There are other install options where if you have an Enterprise cert installed

Seems like it’s a custom signed IPA.

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a