Check the artifact before opening it

Use the download from macprofiles.com and compare the supplied SHA-256 checksum when verifying a transferred copy. Keep the version and build number with your test notes. New internal builds use a stable team certificate rather than an ad-hoc identity; this is still not Developer ID signing or Apple notarization. A stable identity helps preserve Keychain permissions across updates, although upgrading from an old ad-hoc build can still require initial authorization. Do not interpret a matching checksum as Apple’s approval of the application.

Install one copy of the application

Open the DMG and copy Mac Profiles to Applications. Run the installed copy rather than leaving several development copies active from different disk images or build folders. Before replacing a beta, close profile windows normally and wait for saves to complete. Updating the application should not involve deleting its profile-data directory.

Handle a macOS prompt per application

Apple documents an Open Anyway route in Privacy & Security for an application you have deliberately chosen to trust after attempting to open it. Read the exact warning and follow that per-application flow only when appropriate. This installation does not require disabling Gatekeeper or System Integrity Protection. Your macOS version can affect the wording and available controls.

Check browser compatibility separately

The application targets macOS 14 or later on Apple silicon, while the protected proxy path currently has a much narrower tested compatibility check: macOS 26.5 build 25F71 and WebKit 21624.2.5.11.4. Unsupported protected startup is blocked. Being able to open the app is not proof that every browser capability is supported on that operating-system build.

Use a recoverable first test

Create a noncritical profile and exercise navigation, normal close, reopening and the intended connection. Record errors without attaching credentials or real cookie values. Keep important work in its existing browser until your required workflow succeeds in the beta. If a download is temporarily unavailable during release checks, wait for the download card to identify the next approved test artifact.