v1.4beta2

ChangeLog.md

@@ -1,5 +1,19 @@
 #  Setup Manager - Change Log
 
+## 1.4beta2
+
+(2025-11-24)
+
+Same as [the previous beta](https://github.com/jamf/Setup-Manager/releases/tag/v1.4beta) with these additional changes:
+
+- Localization:
+  - added UK English (en-GB) localization
+  - various localization fixes (#171)
+- fixed Network Info font color (#166)
+- `waitForUserEntry` action correctly runs a recon/Update Inventory (#168)
+- `accentColor` affects all items and controls (#170)
+- UI adjustments (#169)
+
 ## v1.4beta
 (2025-10-28)
 

ConfigurationProfile.md

@@ -447,10 +447,12 @@ The label is used as the name of the action in display.
 
 (String, optional, localized, dark mode)
 
-The [icon source](#icon-sources) used for the display of the label. Different types of actions will have different default icons, which are used when no `icon` key is present. The icons will be scaled to fit 64x64 pixels (or 128x128 @2x).
+The [icon source](#icon-sources) used for the display of the label. Different types of actions will have different default icons, which are used when no `icon` key is present. The icons will be scaled to fit 120x120 pixels.
 
 There are several different types of actions, and these are defined by additional keys. These keys will be on the same level as the keys above.
 
+**Note on icon margins:** when you use a path to an app for the icon, or when you use an icon generated by copying the icon from an app in Finder or by a tools such as the [SAP Icon Generator](https://github.com/SAP/macOS-icon-generator), there will be a margin around the icon. Since these are very common ways of getting icons, the layout of the icons in the action tile is designed around the assumption that there will be a margin. Icons without such a margin will look quite big fill most of the space available in the tile.
+
 #### `tileColor`
 
 (String, optional, dark mode, v1.4)
@@ -1150,11 +1152,12 @@ The following keys can be localized:
 
 - `label`
 
-Use these two-letter codes for these languages:
+Use these codes for these languages:
 
 | Language           | two-letter code |
 |--------------------|-----------------|
 | English            | en (default)    |
+| English (UK)       | en-GB           |
 | Dutch (Nederlands) | nl              |
 | French             | fr              |
 | German             | de              |

Docs/Extras.md

@@ -31,7 +31,11 @@ The custom schema does not contain all keys and options available in the [config
 
 When you reach the limits of the custom schema, use the XML it generates as a starting to building a custom XML.
 
-Note that the custom schema can become confused when you switch between enrollment action types and you will need to clean up extra empty fields.
+Note that the custom schema can become confused when you switch between enrollment action types and you will need to clean up extra empty fields. It is best to delete the action type you don't need any more and create a new action of the desired type.
+
+## iMazing Profile Editor
+
+There is also a manifest for Setup Manager in [iMazing Profile Editor](https://imazing.com/profile-editor).
 
 ## Quit
 

Docs/FAQ.md

@@ -8,20 +8,23 @@
 
 Yes, use the top-level `background` key and point it to a local image file or a http URL to an image file. If you don't want custom branding, you can set `background` to `/System/Library/CoreServices/DefaultDesktop.heic` for the default image.
 
-## Setup Manager is not launching after enrollment
+## Setup Manager is not launching after enrollment?
 
-There can be many causes for this. A few common causes are:
+There can be many causes for this.
+
+First, check whether the Setup Manager.app exists at `/Applications/Utilities/Setup Manager.app` and a Setup Manager log file gets created at `/Library/Logs/Setup Manager.log`. When the app and the log file exist, read the log file for errors and messages which should give you a hint as to what is going on. When you have no user account to log in, you can boot to Recovery to check on these files.
+
+If neither of those files exist, then the download and/or installation of Setup Manager is failing or not occurring in the first place. A few common causes are:
  
-- when running at 'enrollment,' you need at least one of the 'Setup Assistant Options' in the Prestage to be set to _not_ skip. 'Location Services' or 'Terms & Conditions' are a good choice that you generally want to leave up the user anyway. Otherwise, Setup Assistant may quit before Setup Manager can launch and do its actions.
-- when using a distribution point other than Jamf Cloud Distribution Point, you need [to provide a manifest](https://appleshare.it/posts/use-manifest-file/)
 - Jamf Pro:
-    - check that Setup Manager is added to your Prestage and the package does not have the label "Availability pending" in Settings> Packages
+    - when using a distribution point other than Jamf Cloud Distribution Point, you need [to provide a manifest](https://appleshare.it/posts/use-manifest-file/)
-    - in Prestage > Enrollment Packages verify that the Distribution Point is set correctly (it resets to "none" when you remove the last enrollment package, so this is easy to miss)
+    - check that Setup Manager is added to your Prestage and the package does **not** have the label "Availability pending" in Settings> Packages. Pending packages will not install during prestage. Wait a few minutes to see if the pending label updates
-    - you can try deleting the Setup Manager pkg from Packages and re-uploading it
+    - in Prestage > Enrollment Packages verify that the Package is added and the Distribution Point is set correctly (the DP resets to "none" when you remove the last enrollment package from Prestage, so this is easy to miss)
-    - verify that the pkg is not installed during Prestage by checking for the presence of `Setup Manager.app` in `/Applications/Utilities`, if the app does not exist, the Prestage is not installing Setup Manager
+    - you can try deleting the Setup Manager pkg from Packages, re-uploading the package and re-adding it to the Prestage. (and verify that the Distribution Point is set correctly in the Prestage)
-    - when the above steps do not remedy the issue, please engage Jamf Support.
+- when the above steps do not remedy the issue, please engage Jamf Support.
+- when running at 'enrollment,' Setup Manager requires Setup Assistant to be running in the background. When you are using standard macOS user account creation, Setup Assistant will be showing that pane "behind" Setup Manager, so you should be fine. But if you are using Jamf Connect Login or a similar tool for account creation, you need at least one of the 'Setup Assistant Options' in the Prestage to be set to _not_ skip. 'Location Services' or 'Terms & Conditions' are a good choice that you generally want to leave up the user anyway. Otherwise, Setup Assistant may quit before Setup Manager can launch and do its actions.
 
-## Does Setup Manager require Jamf Connect
+## Does Setup Manager require Jamf Connect?
 
 No.
 

Docs/JamfPro-QuickStart.md

@@ -51,7 +51,7 @@ You can add more actions here. There are more types of actions available, you ca
 - create a new Prestage or duplicate an existing one
 - add the Setup Manager pkg and the configuration profile to the Prestage
 - when installing and using Jamf Connect Login, ensure you have the latest version
-- ensure that 'Automatically advance through Setup Assitant' is _disabled_
+- ensure that 'Automatically advance through Setup Assistant' is _disabled_
 - have at least one Setup Assistant option which shows before user creation _disabled_ (so that _is_ displayed), we recommend the Location Services or Terms and Conditions pane
 - ensure your test Mac(s) is (are) assigned to the Prestage
 

Docs/LaunchTracking.md

@@ -24,4 +24,4 @@ No signals are sent when `DEBUG` is set to `true`. The signal is sent to `nom.te
 
 We use this data to determine the usage of Setup Manager and where to focus future development, so we appreciate when you let us gather this data.
 
-You can suppress the tracking signal by setting the `PLEASE_DO_NOT_TRACK' boolean key to `true` in the configuration profile.
+You can suppress the tracking signal by setting the `PLEASE_DO_NOT_TRACK` boolean key to `true` in the configuration profile.