/reconnectMpcUserToMobileApp

reconnectMpcUserToMobileApp Calling this request can be used to reconnect an MPC user to the mobile app while MPC driven is enabled by setting a new mobile app public key.

For completing the reconnect, the mobile should call "registerMpcUser" after this session is approved.

  **Request Example:**

  .. code-block::

      reconnectMpcUserToMobileApp(
          user_id="[email protected]",
          public_key="0x123",
          signature_type=0,
          request_extra_data={
            "message_number": 5,
            "session_id": "3478593863424051983840947"
          }
      )

  ----

  **Response Example:**


  .. code-block::

      {
          "FunctionData": {
                  StatusCode=0
                  StatusCodeDescription="Reconnection completed successfully"
          },
          "Meta": {
              "AccessToken": "2911...9a7",
              "Destination": "04bc...9e2",
              "Source": "3dcf...ba4",
              "Time": "2025-05-22 17:00:44.605"
          }
      }


  ### Error Responses

  | Error Type       | Http Code | GK8 error code | Reason / Description                  | Example Response |
  |------------------|-----------|----------------|---------------------------------------|------------------|
  | Backend Response | 200       | 0              | Reconnection completed successfully   | "StatusCode": 0  |
  | Backend Response | 400       | 1              | Unknown user                          | "StatusCode": 1  |
  | Backend Response | 400       | 2              | Invalid public key                    | "StatusCode": 2  |
  | Backend Response | 400       | 3              | Public key already in use             | "StatusCode": 3  |
  | Backend Response | 400       | 4              | Unknown signature type                | "StatusCode": 4  |
  | Backend Response | 400       | 5              | Unable to reconnect cold created user | "StatusCode": 5  |

  ----