bot
Called when the user solved the challenge but the SDK could not finalize the pass. The reason is HSBotDefenderChallengeFailureReason.NETWORK_ERROR when startup is incomplete, or the post-solve token refresh times out or throws (including mixed-environment / incomplete token set; e.g. connectivity, SSL, pinning).
A default empty implementation is provided so existing host apps that only implement botDefenderChallengeSolved / botDefenderChallengeCancelled keep compiling. When this method is implemented, botDefenderChallengeSolved still fires afterward for the same outcome (legacy fold), unless this method throws — both callbacks run inside one try block. One challenge — do not retry twice. The automatic interceptor still delivers this delegate. The legacy callback is folded to HSBotDefenderChallengeResult.SOLVED. Delayed interceptor modes fold the synthetic body to HSBotDefenderErrorType.CHALLENGE_WAS_SOLVED; non-delayed INTERCEPT still returns HSBotDefenderErrorType.REQUEST_WAS_BLOCKED.
Parameters
The classification of the failure.
The AppID that is related to the event.