Sign in to the simulator

Some apps only make sense signed in: a store listing, an entitlement check, a leaderboard. Meta Spatial Simulator can sign in to your account, so you can test those paths without a physical device.

On the same Account row, select Log out.

Signing out closes any app that required an account, and the simulator confirms with Signed out and the message Apps that require login were closed. Closing them stops an app retaining state from the previous account, so the next sign-in starts clean.

Meta VR CLI drives the same account:

metavr ssim auth login
metavr ssim auth status
metavr ssim auth logout

All three take -s/--serial to name a target when more than one simulator is running. For the full flag set, see Set up your environment and tools.

If you are already signed in to Meta VR CLI, metavr ssim start signs the simulator in to the same account, so a fresh simulator starts signed in. Launching the simulator from the Android Studio plugin does the same. A simulator that is already signed in keeps the account it has, so sign out inside the simulator before switching to a different one.

If a sign-in panel is already open when you sign in from the command line, the panel closes automatically. When the panel was blocking an app that requires an account, such as Store, that app opens after sign-in completes.

The Store stops blocking on a login dialog. Signed out, launching Store puts a login dialog in front of you before you can browse. Signed in, it opens straight to the storefront. It is the one built-in app that behaves this way. See Built-in apps.

Platform SDK behavior changes. Signed in, a set of Platform SDK APIs call the real backend rather than returning sample data. This covers parts of Achievements, Group Presence, IAP, Leaderboards, Rate and Review, User Age Category, and Users. Signed out, those same APIs return an authentication error rather than falling back to sample data, so an app that assumed sample data surfaces a failure instead. Platform SDK APIs outside that set read local test data and behave the same either way.

Plan for both states. If your app calls one of these APIs on a path a signed-out user can reach, handle the error rather than assuming a response. For which APIs behave which way, see Test with Platform SDK.

Note: Launching an app that requires an account from the command line skips the sign-in prompt, and the app opens to an error state such as a blank panel. Launch it from the home screen to get the login prompt instead.