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.
| Version | Status | First release | Last release | Deprecation | Shut down |
|---|---|---|---|---|---|
| 18.7 | Supported | Oct 10, 2024 | Jan 29, 2025 | Q2 2026 | Q2 2028 |
| 18.6 | Supported | Jun 19, 2024 | Sep 10, 2024 | Q4 2025 | Q1 2028 |
| 18.5 | Deprecated | Feb 21, 2024 | May 29, 2024 | Q2 2025 | Q2 2027 |
| 18.4 | Deprecated | Nov 13, 2023 | Feb 21, 2024 | Q1 2025 | Q1 2027 |
| 18.3 | Deprecated | Aug 16, 2023 | Aug 16, 2023 | Q1 2024 | Q3 2026 |
| 18.2 | Deprecated | May 01, 2023 | Jul 05, 2023 | Q1 2024 | Q3 2026 |
| 18.1 | Deprecated | Feb 01, 2023 | Apr 06, 2023 | Q1 2024 | Q2 2026 |
| 18.0 | Deprecated | Oct 31, 2022 | Nov 30, 2022 | Q1 2024 | Q1 2026 |
| 17.1 | Deprecated | May 29, 2024 | May 29, 2024 | Q3 2024 | Q2 2026 |
| 17.0 | Deprecated | Dec 09, 2021 | May 18, 2022 | Q3 2024 | Q2 2026 |
| 16.1 | Deprecated | Jun 01, 2021 | Jun 01, 2021 | Q3 2024 | Q2 2026 |
| 16.0 | Deprecated | Apr 15, 2020 | Jun 16, 2021 | Q3 2024 | Q2 2026 |
| SafetyNet reCAPTCHA | Deprecated | Jan 05, 2022 | Q3 2024 | Q3 2025 |
Visual challenges
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.