Posts

Post not yet marked as solved
1 Replies
1.6k Views
In iTunes COnnect, I have one iOS app that we removed from sale. At the top of the screen I see a red banner with "unresolved iOS issue"."Your app has an unresolved issue and has been removed from the App Store."How can I remove this warning as the app is effectively discontinued?
Posted Last updated
.
Post not yet marked as solved
0 Replies
467 Views
In the past (10.11 to 10.14), to debug a System Pref Pane, you could make a copy of System Preferences and self-sign it, then use this copy as the debug target. This method bypassed the System Integrity Protection restrictions.With Catalina, all third party prefPanes are now loaded in a system process called "legacyLoader". Self-signing a copy of legacyLoader is no longer possible. Although you can obviously still make a copy and self-sign it, there is no way to force System Preferences to use the modified self-signed copy as it will always launch the built-in, Apple-signed legacyLoader.The only way I can see on 10.15 to debug a prefPane is to disable SIP system-wide. Not a great solution.Does anyone know a way to debug something in legacyLoader without disabling SIP?
Posted Last updated
.
Post not yet marked as solved
5 Replies
958 Views
I have a System Preference Pane that contains various helper apps. It is delivered in an Installer App (in the /Contents/PlugIns folder) and when the Installer runs, it simply launches the prefPane to let the system copy it into System Preferences. The Installer notarizes properly, but when I look at the embedded prefPane in /Contents/PlugIns I get:spctl -a -v my.prefPane> My.prefPane: rejected (the code is valid but does not seem to be an app)xcrun stapler validate --verbose my.prefPane> My.prefPane does not have a ticket stapled to it.If I notarize the prefPane directly I get:spctl -a -v my.prefPane> My.prefPane: rejected (the code is valid but does not seem to be an app)xcrun stapler validate --verbose my.prefPane>The validate action worked!I need it to work when delivered as an embedded plugin in my Installer App. How can I make this work so that when the Installer copies the embedded prefPane to System Preferences, the prefPane is still treated as having been notarized?
Posted Last updated
.
Post not yet marked as solved
17 Replies
5.1k Views
In the latest (2nd) release of 10.15 beta, the Feedback Assistant is not working. It will not let me create a new issue. Also, the feedback assistant on the website will not accept a bug report either. I need to report a bug in 10.14.5 and without the Apple Bug Reporter, there is no way to do it.I miss the old Apple that was around during System 7 and OS X 10.6.8. 😟
Posted Last updated
.
Post not yet marked as solved
0 Replies
305 Views
On 10.14 in Light Mode, my NSPredicateEditor looks weird when presented in a sheet. The NSTextFields (both static and editable) have dark grey backgrounds. How can I fix this?
Posted Last updated
.
Post not yet marked as solved
6 Replies
2.1k Views
My product is a System Pref Pane which contains multiple embedded apps/tools to do its job, including:A background-only renderer.An app to handle a Menu Status Item.An app to check for updates since System Preferences might not be running.A unix executable relaunch tool to handle loading into System Preferences during an update. This one seems impossible to staple a notarization to.I also have an installer (.app) that simply copies the System Pref Pane into place (needed because of a code-signing bug that prevents direct distribution of the prefPane).The structure for my DMG looks like:Installer.app- PrefPane (in the Installer.app Resources folder)-- Renderer.app (in the PrefPane Resources folder)-- MenuStatusItem.app (in the PrefPane Resources folder)-- Updater.app (in the PrefPane Resources folder)-- Relaunch Tool (unix executable) (in the PrefPane Resources folder)I have a nice script in Xcode that packages all this together. With Notarization, will I now need to notarize each of these individually starting at the deepest point? That sounds like a total hassle since automating it is difficult with the delay/polling required at Apple.Will just Notarizing the outter-most container be enough?I'm looking for suggestions from others that have multiple executables in a single app package as to dealing with Notarization.
Posted Last updated
.