We ship a signed, notarized product archive (.pkg) built with pkgbuild + productbuild and a custom InstallerPlugins pane (ChoosePlugin.bundle). The payload must always install to the system volume (/). There is no supported alternate directory. customize="never" is set because there is a single component package; the user must not pick packages either. What we already do In Distribution.xml: Introduction ChoosePlugin.bundle Target Install PackageSelection is omitted. customize="never" is set. Observed behavior (current macOS) Destination Select (Target) If Target is kept in SectionOrder, the pane still appears in the wizard (often with a read-only / single-volume UI). That step is unused product-wise: the user cannot choose another location. If Target is removed from SectionOrder, Installer.app hangs on the Installation pane at “Preparing for installation…” (pagecontroller / no selected volume). So Target cannot be dropped if we still use the GUI Installer. Installation Type (PackageSelection) The pane does not run (correct). The sidebar still lists “Installation Type” (and often “Summary”) as grayed items. There is no documented way to hide those labels. There is no public InstallerPlugins API to auto-advance the native Destination Select pane (gotoNextPane only applies to our custom section). Question Is there a supported way (Distribution XML, InstallerSections.plist, productbuild, or otherwise) to: Not show Destination Select at all in Installer.app, while still installing to / and not hanging on Installation; and Not list Installation Type (and unused Summary) in the left-hand wizard list, when customize="never" and PackageSelection is omitted? If this is not supported, please confirm that: Destination Select must remain in SectionOrder for GUI installs even with rootVolumeOnly + domains limited to localSystem; and sidebar entries for unused built-in sections cannot be removed. Environment Product archive via productbuild --distribution --plugins macOS 13+ (tested on current macOS / Apple silicon) Custom plugin is universal (arm64 + x86_64) Silent / MDM path (installer -pkg … -target /) is acceptable for automation; this request is GUI Installer.app only.

Sometimes, when I close the lid using the MacOs version Sequoia 15.2, with the configuration to require a password for 5 seconds, the system does not ask for the password as expected. This happens sometimes even though nothing preventing the system from sleeping when you close and open the lid, but it still seems like a security concern. Is there some known issue related to this problem or a way to avoid it? Result of command pmset -g: Configuration:

We need to do some operations in a login screen, but when the user uses a WPA2-Enterprise network, the authentication to this network is only possible after the login process has already been completed. Is there a way to change the network on login screen or a way to authenticate on the WPA2-Enterprise network before a completed login? STEPS TO REPRODUCE 1 - Use a WPA2-Enterprise 2 - Set WPA2-Enterprise as Auto-Join/Principal 3 - Reboot the Machine 4 - On the logon screen it's impossible to authenticate on the enterprise network even then type the username and password.

I would like to know, if I do an upgrade from my Apple Developer Program account to the Apple Developer Enterprise Program, my current apps published will be affect in some aspect or not. What impact do we have in this apps already existent in Apple store?