ScopeCheckResult
Indicates the outcome of an ExperienceAuthService scope-authorization
request.
Items 8
| History | Name | Value | Description | |
|---|---|---|---|---|
| 563 | ConsentAccepted | 0 | The player accepted the authorization prompt and a valid token was issued for the requested scopes. | |
| 563 | InvalidScopes | 1 | The requested scopes are not recognized or are not permitted for the calling context. | |
| 563 | Timeout | 2 | The scope-check request exceeded the configured timeout period before the player responded. | |
| 563 | NoUserInput | 3 | The authorization prompt was dismissed without any explicit player action, such as when the player disconnects or the UI is closed without a response. | |
| 563 | BackendError | 4 | The Roblox backend returned an error or unexpected HTTP status when exchanging the consent grant for an authorization token. | |
| 563 | UnexpectedError | 5 | An unexpected error occurred that is not covered by a more specific result code. | |
| 563 | InvalidArgument | 6 | One or more arguments passed to the scope-check call were invalid, such as an empty scope list, a null player instance, or a player who is no longer in the experience. | |
| 566 | ConsentDenied | 7 | The player explicitly declined the authorization prompt. |
Description
Returned by an ExperienceAuthService scope-authorization callback to
indicate whether the player granted, denied, or failed to complete a
permission-consent flow. Callers such as AssetService and
AvatarCreationService inspect this value to decide whether to proceed
with the authorized action or surface an appropriate error to the developer.
History 9
- 566 Add ConsentDenied
- 563 Add UnexpectedError
- 563 Add Timeout
- 563 Add NoUserInput
- 563 Add InvalidScopes
- 563 Add InvalidArgument
- 563 Add ConsentAccepted
- 563 Add BackendError
- 550 Add ScopeCheckResult