Stay organized with collections
Save and categorize content based on your preferences.
This page explains the deprecation and shutdown policy, and schedule for
reCAPTCHA Mobile SDK versions.
With the release of a new SDK, earlier versions will be deprecated and given a
shutdown date. When an SDK version is shut down, calls to
projects.assessments.create will start to receive an error message indicating
that this version is no longer usable. Additionally, submissions to the
Google Play Store can be blocked if they contain a shutdown SDK version. The iOS
App Store does not have such a mechanism.
The latest SDKs offer the best protection and highest performance, and they address
bugs that might exist in previous versions. Although Google makes every effort to
enhance the detection offered by previous SDK versions, some capabilities and
enhancements require a new SDK. For information about the enhancements and fixes,
see the release notes.
Definitions
Supported: These SDK versions will continue to function in production for
deployed applications. Due to possible changes in the iOS App Store,
Google Play Store, and other mobile distribution platforms, supported versions
might not be submittable in new versions of an app. This includes changes to
required compilers and privacy or disclosure rules.
Deprecated: These SDKs will continue to function, but they will be shut
down in the future. We recommend upgrading to a new version of the SDK as soon as
possible.
Shut down: When an SDK is shut down, it might return errors in calls to
projects.assessments.create, getClient(), execute(), and other SDK methods.
You should upgrade immediately to a supported version.
Schedule
The following table lists the shutdown date for each version. We recommend that
you migrate to the newest version as soon as possible after its release.
reCAPTCHA SDK versions 16 and higher don't have visual challenges (reCAPTCHA v2)
such as those found in reCAPTCHA SafetyNet. We no longer recommend the use of
visual challenges in mobile applications, but for customers that still want to
enable them we provide
sample code
to use visual challenges in a WebView.
Pricing
Upgrading from v16, v17, or v18 does not affect the pricing. reCAPTCHA SafetyNet was subjected to the quota limit of reCAPTCHA, and there was no option to go beyond that limit. When moving to reCAPTCHA you now have the option to enable billing to go beyond the quota limit.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Deprecation and shutdown policy for mobile SDKs\n\nThis page explains the deprecation and shutdown policy, and schedule for\nreCAPTCHA Mobile SDK versions.\nWith the release of a new SDK, earlier versions will be deprecated and given a\nshutdown date. When an SDK version is shut down, calls to\n`projects.assessments.create` will start to receive an error message indicating\nthat this version is no longer usable. Additionally, submissions to the\nGoogle Play Store can be blocked if they contain a shutdown SDK version. The iOS\nApp Store does not have such a mechanism.\n\nThe latest SDKs offer the best protection and highest performance, and they address\nbugs that might exist in previous versions. Although Google makes every effort to\nenhance the detection offered by previous SDK versions, some capabilities and\nenhancements require a new SDK. For information about the enhancements and fixes,\nsee the [release notes](/recaptcha/docs/release-notes).\n\nDefinitions\n-----------\n\n- **Supported:** These SDK versions will continue to function in production for\n deployed applications. Due to possible changes in the iOS App Store,\n Google Play Store, and other mobile distribution platforms, supported versions\n might not be submittable in new versions of an app. This includes changes to\n required compilers and privacy or disclosure rules.\n\n- **Deprecated:** These SDKs will continue to function, but they will be shut\n down in the future. We recommend upgrading to a new version of the SDK as soon as\n possible.\n\n- **Shut down:** When an SDK is shut down, it might return errors in calls to\n `projects.assessments.create`, `getClient()`, `execute()`, and other SDK methods.\n You should upgrade immediately to a supported version.\n\nSchedule\n--------\n\nThe following table lists the shutdown date for each version. We recommend that\nyou migrate to the newest version as soon as possible after its release.\n\nVisual challenges\n-----------------\n\nreCAPTCHA SDK versions 16 and higher don't have visual challenges (reCAPTCHA v2)\nsuch as those found in reCAPTCHA SafetyNet. We no longer recommend the use of\nvisual challenges in mobile applications, but for customers that still want to\nenable them we provide\n[sample code](https://github.com/GoogleCloudPlatform/recaptcha-enterprise-mobile-sdk/tree/main/examples)\nto use visual challenges in a WebView.\n\nPricing\n-------\n\nUpgrading from v16, v17, or v18 does not affect the pricing. reCAPTCHA SafetyNet was subjected to the [quota limit](https://developers.google.com/recaptcha/docs/faq#are-there-any-qps-or-daily-limits-on-my-use-of-recaptcha) of reCAPTCHA, and there was no option to go beyond that limit. When moving to reCAPTCHA you now have the option to enable billing to go beyond the quota limit."]]
