• Truncate fields for API payloads to prevent 400 errors due to size limits defined by OpenAPI specifications

• Fix an issue preventing DataDomeInterceptor to propagate error responses to the caller catch block

Breaking changes

DataDomeInterceptornow propagates errors when the request fails with a status code other than401 or 403 after retrying.

Previously, such errors were silently ignored, preventing them from reaching the caller’s catch block.

Impact:

• Requests that previously appeared as resolved may now reject.
• Downstream code using the interceptor must handle potential rejections via .catch() or try/catch.

• Fix DioException not propagated after retrying blocked requests
• Upgrade compileSdkVersion to 36
• Update Kotlin version to 2.2.0
• Upgrade gradle to 8.13.0 and gradle plugin to 8.1.3

Breaking changes

• Match exclusion and inclusion patterns with complete URLs instead of only paths

• Fix parsing of long GraphQL queries from request body
• Disable follow mode for redirects on Bot Protect API responses to forward them to clients

• Add safe handling for nullable WebResourceRequest.requestHeaders in WebViewClient.shouldInterceptRequest to prevent crashes
• Fix missing requestId in manual integration when invoking onComplete(requestId) after challenge resolution

• Add support for account update events DataDomeAccountUpdateEvent
• Add support for password update events DataDomePasswordUpdateEvent
• Add optional session, user, and authentication to the login and registration events
• Add display_name, description, external_urls, picture_urls, payment_method_updated to the user model

Breaking changes

• Remove GraphQL and JS Tag injection features
• Remove responseProvider function
• Restore onClientRequest and onClientResponse functions
• Remove EW_DD_CLIENT_SIDE_KEY, EW_DD_JS_URL and EW_DD_JS_OPTIONS variables

Other changes

• Map enriched headers into user-defined variables through the property manager

• Add handlers optional parameter to allow overriding fields in payloads sent to the Bot Protect API
• Exclude empty fields from payloads sent to the Bot Protect API

• Allow parsing of GraphQL queries when the Content-Type header contains additional directives like charset and is not strictly equal to application/json
• Disable follow mode for redirects on Bot Protect API responses to forward them to clients