OAuth consent screen verification with Google Fit API Scope

[semen_sequenia]

I've sent OAuth consent screen with scope from Google Fit API. After a while, I received the email with the next content:

We are writing to notify you that the Fit APIs for both Android and web are being deprecated, and your submission for <project_id> is impacted by this change. Please refer to this blog post announcement for more information.

As of May 1, 2024, we are no longer processing OAuth verification requests for Fit scopes.

What do I need to know?
- Existing access to Fit scopes for this project will not be immediately impacted.
- You may continue to test Fit APIs in a staging environment.
- We are no longer processing OAuth verification requests for Fit scopes and will close this submission.

Anyone, please, help me to understand that.. Do I have any chances to complete verification, or I should migrate my code from Google Fit API to Android Health?

[maricarp]

Hello @semen_sequenia ,

As stated here in the Android Developers Blog, it is encouraged that Fit REST API users migrate to Android Health APIs to ensure uninterrupted service for your users. 

Here are the advantages of Android health APIs over the Google Fit APIs for Android:

1. Recording steps, distance, and calories: In the near future, Android Health will provide the Recording API on mobile, which doesn’t require a Google user account or the need for you to request access to API scopes. And it is more battery-efficient than using Android SensorManager (ASM). The Recording API will launch with steps, and soon support distance and calories.
2. Accessing recorded data: The Recording API on mobile will enable developers to access up to 10 days of recorded data.
3. Storing and sharing data between apps: By integrating with Health Connect, your Android app can access data from a growing ecosystem of apps with just one connection. Plus, data is stored on-device, ensuring the user is in full control of their data.

New sign-ups for the Google Fit APIs will no longer be accepted from May 1, 2024. So, to get started with the migration process, please see this comprehensive migration guide. This guide will walk you through the steps needed to transition your app from Google Fit APIs to Android Health products, primarily Health Connect, to ensure a smooth experience for both you and your users.

Hope this helps.