When installing a DeviceOwner MDM application on Meta Quest devices, the installation process requires that any accounts added to the device are first removed - this step allows the MDM to set itself as DeviceOwner.
There are a number of default Meta apps that require the existence of a Meta account on the device in order to function. Our efforts to reapply Meta accounts via the Accounts Center fail, as the AC application fails to open. We've noticed this on at least v62+ of Quest firmware.
03-08 09:59:59.826 18997 18997 D [SUI] SettingsPanelApp: Received deeplink; uri: /accounts_center
03-08 09:59:59.828 2362 2376 E LibraryStorage: Attempting to edit app that is not entitled
03-08 09:59:59.848 18997 18997 D [SUI] PanelAppBase: Acquiring viewModel AndroidSettingsViewModel refCount: 1
03-08 09:59:59.851 18997 18997 D [SUI] ReauthGatedSettingsHelper: Session revoked
03-08 09:59:59.851 18997 18997 D [SUI] PanelAppBase: Acquiring viewModel AndroidSettingsViewModel refCount: 2
03-08 09:59:59.857 18997 18997 I [SUI] ConsumerConfiguration: Setting SystemUX Configuration and Policy Settings.
03-08 09:59:59.857 18997 18997 D [SUI] SettingsSectionUtil: Should Show Voice Commands Section SystemUXConfig is Voice Command UI Enabled: false
03-08 09:59:59.862 18997 18997 I [SUI] ConsumerConfiguration: Setting SystemUX Configuration and Policy Settings.
03-08 09:59:59.873 18997 18997 I [SUI] ConsumerConfiguration: Setting SystemUX Configuration and Policy Settings.
03-08 09:59:59.874 18997 18997 D [SUI] MultiUserManagerHelper: Is Multiuser Enabled SystemUXConfig is MultiUser Enabled: true, OculusManager is MultiUser Enabled: false
03-08 09:59:59.884 18997 18997 D [SUI] SettingsProvider: SettingsService getInstance
03-08 09:59:59.884 18997 18997 D [SUI] SettingsProvider: connectToService with callback with total client count: 2
03-08 09:59:59.886 18997 18997 E ArvrUnexpectedEventBuilder: Inaccessible section: /accounts_center
