Choose your implementation method:
This function is part of the Connect Interface.
Delete any existing Device ID access credentials for the current user profile on the local device.
The deletion is permanent and it is not possible to recover lost game data and progression
if the Device ID had not been linked with at least one real external user account.
On Android and iOS devices, uninstalling the application will automatically delete any local
Device ID credentials created by the application.
On Desktop platforms (Linux, macOS, Windows), Device ID credentials are not automatically deleted.
Applications may re-use existing Device ID credentials for the local OS user when the application is
re-installed, or call the DeleteDeviceId API on the first run to ensure a fresh start for the user.
Parameters
EOS_Connect_DeleteDeviceId
Parameter Type And Name
|
Usage Information
|
EOS_HConnect Handle
|
|
const EOS_Connect_DeleteDeviceIdOptions* Options
|
structure containing operation input parameters
|
void* ClientData
|
arbitrary data that is passed back to you in the CompletionDelegate
|
const EOS_Connect_OnDeleteDeviceIdCallback CompletionDelegate
|
a callback that is fired when the delete operation completes, either successfully or in error
|
This function is asynchronous; the EOS SDK guarantees that your callback (the CompletionDelegate
parameter) will run when the operation completes, regardless of whether it succeeds or fails. Use the void*
parameter to pass any contextual information the callback may need in order to react properly. Relevant information can be copied from the EOS SDK's cache while the callback function is running. You do not need to remove the callback function.
Because this function is asynchronous, it employs a callback of type EOS_Connect_OnDeleteDeviceIdCallback to report the results of its operation.
Callback Parameters
EOS_Connect_OnDeleteDeviceIdCallback
This function is part of the Connect Interface.
Delete any existing Device ID access credentials for the current user profile on the local device.
The deletion is permanent and it is not possible to recover lost game data and progression
if the Device ID had not been linked with at least one real external user account.
On Android and iOS devices, uninstalling the application will automatically delete any local
Device ID credentials created by the application.
On Desktop platforms (Linux, macOS, Windows), Device ID credentials are not automatically deleted.
Applications may re-use existing Device ID credentials for the local OS user when the application is
re-installed, or call the DeleteDeviceId API on the first run to ensure a fresh start for the user.
Parameters
Connect.ConnectInterface.DeleteDeviceId
Parameter Type And Name
|
Usage Information
|
DeleteDeviceIdOptions options
|
structure containing operation input parameters
|
object clientData
|
arbitrary data that is passed back to you in the CompletionDelegate
|
OnDeleteDeviceIdCallback completionDelegate
|
a callback that is fired when the delete operation completes, either successfully or in error
|
This function is asynchronous; the EOS SDK guarantees that your callback (the CompletionDelegate
parameter) will run when the operation completes, regardless of whether it succeeds or fails. Use the object
parameter to pass any contextual information the callback may need in order to react properly. Relevant information can be copied from the EOS SDK's cache while the callback function is running. You do not need to remove the callback function.
Because this function is asynchronous, it employs a callback of type Connect.OnDeleteDeviceIdCallback to report the results of its operation.
Callback Parameters
Connect.OnDeleteDeviceIdCallback
Parameter Type And Name
|
Usage Information
|
DeleteDeviceIdCallbackInfo data
|
Output parameters for the {ConnectInterface.DeleteDeviceId} function.
|
Was this document useful?
Thank you for the response!
You’ve marked this document as useful:
yes
You’ve marked this document as not useful:
no