[macOS arm64 / Jamf Pro] Sign-in fails with System.NullReferenceException in RuntimeBroker in v1.44.0 - worked in v1.43
After upgrading from Storage Explorer v1.43 to v1.44.0, sign-in with a Microsoft account fails completely on macOS (Apple Silicon / arm64) with Jamf Pro MDM management. Downgrading back to v1.43 resolves the issue immediately, confirming this is a regression introduced in v1.44.0.
Environment
| Property |
Value |
| Storage Explorer version |
1.44.0 (build 20260626.6) |
| AzCopy version |
10.27.2 |
| Platform |
macOS |
| Architecture |
arm64 (Apple Silicon) |
| MDM |
Jamf Pro (ur.jamfcloud.com) |
| MDM enrollment |
Yes (User Approved) |
| .NET runtimes installed |
6.0, 7.0, 8.0, 10.0 |
| Support-ID |
88e127c3-8b6f-4371-856b-a8199ec79e4d |
Steps to Reproduce
- Use macOS arm64 device managed by Jamf Pro
- Install or upgrade to Storage Explorer v1.44.0
- Launch the application
- Attempt to sign in with a Microsoft account
- Sign-in fails immediately with error message:
{
"message": "\"Object reference not set to an instance of an object.\""
}
**Expected Behavior**
Sign-in should complete successfully, as it did in v1.43.
**Actual Behavior**
Sign-in fails with a System.NullReferenceException in RuntimeBroker..ctor.
**Log Output**
[2026-07-02T11:46:15.920Z] (main:84004) <ERRO> Failed to addAccount, authFlowType: authBroker, authResult: {"Account":null,"UserCancelled":false,"UserName":null,"Errors":[{"Message":"Object reference not set to an instance of an object.","ExceptionType":"System.NullReferenceException","HResult":-2147467261,"ExceptionString":"System.NullReferenceException: Object reference not set to an instance of an object.\n at Microsoft.Identity.Client.Platforms.Features.RuntimeBroker.RuntimeBroker..ctor(CoreUIParent uiParent, ApplicationConfiguration appConfig, ILoggerAdapter logger)\n at Microsoft.Identity.Client.Broker.BrokerExtension.<>c.<AddRuntimeSupport>b__3_0(CoreUIParent uiParent, ApplicationConfiguration appConfig, ILoggerAdapter logger)\n at Microsoft.Identity.Client.PlatformsCommon.Shared.AbstractPlatformProxy.CreateBroker(ApplicationConfiguration appConfig, CoreUIParent uiParent)\n at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.FetchTokensFromBrokerAsync(String brokerInstallUrl, CancellationToken cancellationToken)\n at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.GetTokenResponseAsync(CancellationToken cancellationToken)"}]}
**Additional Notes**
The settings.json file already contained "application.auth.loginType": "deviceCode" but the application still attempted to use authBroker
Clearing all cache files in ~/Library/Application Support/StorageExplorer/ did not resolve the issue
Installing additional .NET runtimes (8.0) did not resolve the issue
Downgrading to v1.43 resolves the issue immediately
The device is enrolled in MDM via Jamf Pro but this configuration was unchanged between versions
Workaround
Downgrade to Storage Explorer v1.43.
[macOS arm64 / Jamf Pro] Sign-in fails with System.NullReferenceException in RuntimeBroker in v1.44.0 - worked in v1.43
After upgrading from Storage Explorer v1.43 to v1.44.0, sign-in with a Microsoft account fails completely on macOS (Apple Silicon / arm64) with Jamf Pro MDM management. Downgrading back to v1.43 resolves the issue immediately, confirming this is a regression introduced in v1.44.0.
Environment
Steps to Reproduce
{ "message": "\"Object reference not set to an instance of an object.\"" } **Expected Behavior** Sign-in should complete successfully, as it did in v1.43. **Actual Behavior** Sign-in fails with a System.NullReferenceException in RuntimeBroker..ctor. **Log Output** [2026-07-02T11:46:15.920Z] (main:84004) <ERRO> Failed to addAccount, authFlowType: authBroker, authResult: {"Account":null,"UserCancelled":false,"UserName":null,"Errors":[{"Message":"Object reference not set to an instance of an object.","ExceptionType":"System.NullReferenceException","HResult":-2147467261,"ExceptionString":"System.NullReferenceException: Object reference not set to an instance of an object.\n at Microsoft.Identity.Client.Platforms.Features.RuntimeBroker.RuntimeBroker..ctor(CoreUIParent uiParent, ApplicationConfiguration appConfig, ILoggerAdapter logger)\n at Microsoft.Identity.Client.Broker.BrokerExtension.<>c.<AddRuntimeSupport>b__3_0(CoreUIParent uiParent, ApplicationConfiguration appConfig, ILoggerAdapter logger)\n at Microsoft.Identity.Client.PlatformsCommon.Shared.AbstractPlatformProxy.CreateBroker(ApplicationConfiguration appConfig, CoreUIParent uiParent)\n at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.FetchTokensFromBrokerAsync(String brokerInstallUrl, CancellationToken cancellationToken)\n at Microsoft.Identity.Client.Internal.Requests.InteractiveRequest.GetTokenResponseAsync(CancellationToken cancellationToken)"}]} **Additional Notes** The settings.json file already contained "application.auth.loginType": "deviceCode" but the application still attempted to use authBroker Clearing all cache files in ~/Library/Application Support/StorageExplorer/ did not resolve the issue Installing additional .NET runtimes (8.0) did not resolve the issue Downgrading to v1.43 resolves the issue immediately The device is enrolled in MDM via Jamf Pro but this configuration was unchanged between versions Workaround Downgrade to Storage Explorer v1.43.