Whilst a user (who is sharing their presence with you) is connecting to a team create or team test instance, the presence API will fail to provide a universeId and returns an inconsistent lastLocation (“studio -” appended at the start) in its response
This bug is more noticeable on big place files.
API: https://presence.roblox.com/v1/presence/users POST
Example payload:
{"userIds": [51787703]}
Example response body
{
"userPresences": [
{
"userPresenceType": 3,
"lastLocation": "Studio - terrain replacement",
"placeId": 76234588566463,
"rootPlaceId": 76234588566463,
"gameId": null,
"universeId": null,
"userId": 51787703
}
]
}
Expected response body
{
"userPresences": [
{
"userPresenceType": 3,
"lastLocation": "terrain replacement",
"placeId": 76234588566463,
"rootPlaceId": 76234588566463,
"gameId": null,
"universeId": 6928319305,
"userId": 51787703
}
]
}
Attached repo place along with the reproduction steps for that place in the private note
Expected behavior
I expect universeId to not be null and the lastLocation to stay consistent (no “studio -”)
A private message is associated with this bug report