No-ft error: bloks_payload has no ft — gs entries contain error details directly
(e.g. CAA_REG_CONTACTPOINT_PHONE:error_message = "Mobile number required.")
With-ft error: bloks_payload has ft, but the action executable sets
should_show_error to true via a global state mutation. The error message
is also set in the executable (e.g. "That code isn't valid.").
Challenge/spam markers are detected via string literals in the executables.
Parameters
appId: string
The full Bloks app_id (e.g. com.bloks.www.bloks.caa.reg.send_confirmation.async)
Check a Bloks registration response for errors.
Detection logic (two error types):
No-ft error: bloks_payload has no
ft— gs entries contain error details directly (e.g.CAA_REG_CONTACTPOINT_PHONE:error_message = "Mobile number required.")With-ft error: bloks_payload has
ft, but theactionexecutable setsshould_show_errortotruevia a global state mutation. The error message is also set in the executable (e.g."That code isn't valid.").Challenge/spam markers are detected via string literals in the executables.