When an auth call is made asking to swap the refresh token for an access token with a path that points to a non-existent Realm, ROS will create an empty Realm before returning the token. This has been a source of confusion for users because, if they use the wrong URL for a sync configuration, they'll see the Realm in studio, but no data will ever be synced, see https://github.com/realm/realm-dotnet/issues/1654.
When an auth call is made asking to swap the refresh token for an access token with a path that points to a non-existent Realm, ROS will create an empty Realm before returning the token. This has been a source of confusion for users because, if they use the wrong URL for a sync configuration, they'll see the Realm in studio, but no data will ever be synced, see https://github.com/realm/realm-dotnet/issues/1654.