Installer profiles New - Profiles can use your own installers instead of a license page: choose "Your own installers" on License and Installers, add FileMaker Pro .dmg and .exe files with Add Installers or by dropping them on the window (the version is read from the file itself, so renamed files work too: from the app on the .dmg, or the .exe's file properties; it can be corrected by hand) and choose your .fmcert certificate. The files are used where they are, never copied or changed. - Built installers: a trash button beside Reveal moves an installer to the Trash (macOS) or Recycle Bin (Windows), from where it can be put back. - Installer profiles: separate setups for different licenses, settings or customers. The menu at the top of the sidebar shows the open profile and switches between them; New Profile, Duplicate, Rename, Use as Default and Remove are in the same menu. Each profile has its own license page, Assisted Install and Configure Installers settings, built installers and build logs; downloaded installers are shared by all profiles. The window title shows the open profile when you have more than one. Changed - Your current setup becomes a profile called "Default" automatically, with its built installers and logs (a copy of the old settings is kept as settings.json.bak). - On Windows, macOS installers on the license page are greyed out: they can't be built there, so they can't be ticked or downloaded. - The colour scheme, Max downloads and a skipped update version are now this computer's preferences, the same in every profile. - Clean up all removes the downloaded installers (shared by all profiles) and the open profile's saved license page. When other profiles use those installers, it asks whether to delete them too; deleting a single downloaded installer that another profile uses asks first. Fixed - The Settings gear at the bottom of the sidebar turns green on hover, like the version number beside it. - Notarization tries again (up to twice) when Apple's notary service can't be reached, instead of failing the build on a single timeout. If it still fails, a system notification lets you know and you're asked whether to keep the signed package; a kept one is listed with a "Not notarized" badge, and the build log notes the failure and your choice. - If the window reloads while a build is running, it picks the build back up instead of saying "A build is already running".