This is fine for testing, but might lead to collisions and weird things when dealing with items and user properties in production. Note that, at this time, if you are unable to identify a user, or choose not to, all Metaverse activity within your app will appear to be coming from the account associated with your API key. It writes the user’s identification key to your app’s UserDefaults, and references it when loading subsequent experiences. This method only needs to be invoked once. For instance, if your app requires accounts, you can invoke this method at the time of sign in and provide your user ID as the argument (or, if you require unique usernames, the username or another piece of information like phone number or email address) to create a persistent Metaverse account linked to their user profile within your app. You can identify a user using some unique piece of information known by your application. Identifying users allows you to do things like save and track user properties across experiences, and to give and request items from users’ inventories. If you would like to store persistent user data, use (user: "USER_ID") to associate your app user with the Meta SDK. Extension ViewController: MetaExperienceDelegate
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |