t {code: 1001, name: ‘API_NOT_AVAILABLE’, sourceIdentifier: undefined, message: ‘Cannot use the player.getAvailableAudio API: the player has already been destroyed.’, data: undefined, …}
code: 1001
data: undefined
message: “Cannot use the player.getAvailableAudio API: the player has already been destroyed.”
name: “API_NOT_AVAILABLE”
sourceIdentifier: undefined
stack: "API_NOT_AVAILABLE: Cannot use the player.getAvailableAudio API: the player has already been destroyed.\n at r
As you can read in the link above, another common cause is if the UI tries to access the player after it has crashed or has been destroyed. In this case, recommendation would be:
In general, please ensure you listen to the PlayerEvent.Destroy event/callback and don’t access the player API after such event has been thrown in order to avoid this error.