We're making some changes to the Google Fit APIs. Learn about how these changes might affect your app. Read our new policy.

Google, unlike Facebook, has not been quick to comply with the new App Store privacy labels. Of its many apps, Gmail and Google Drive include labels, as do YouTube and YouTube Music. Getting an ID for your app requires several steps. These steps are outlined below. Find your app's certificate information. Create or modify a project in the Google API Console. Request an OAuth 2.0 client ID. Find your app's certificate information. The API key is based on a short form of your app's digital certificate, known as its SHA-1. Build fast, beautiful user experiences for iOS 14 and Android 11 from one codebase. Flutter 1.22 comes with i18n and l10n support, Google Maps and WebView plugins ready for production, a new App Size tool, and more.

Overview

MacosApp

To use the Google Fit for Android, you need an OAuth 2.0 client ID forAndroid applications.

All Android apps are signed with a digital certificate for which you hold theprivate key. Refer to the Android guide to signing your applicationsfor more information about digital certificates.

Android OAuth client IDs are linked to specific certificate/package pairs. Youonly need one ID for each certificate, no matter how many users you have forthe app.

Google Home App For Macos

Getting an ID for your app requires several steps. These steps are outlinedbelow.

Google Home App For Macos Sierra

  1. Find your app's certificate information.
  2. Create or modify a project in the Google API Console.
  3. Request an OAuth 2.0 client ID.

Find your app's certificate information

The API key is based on a short form of your app's digital certificate, known as its SHA-1 fingerprint. To display the SHA-1 fingerprint for your certificate, first ensure that you are using the right certificate. You may have two certificates:

  • A debug certificate: The Android SDK tools generate this certificate automatically when you do a debug build. Only use this certificate with apps that you're testing. Do not attempt to publish an app that's signed with a debug certificate. The debug certificate is described in more detail in Signing in Debug Mode in the Android Developer Documentation.
  • A release certificate: The Android SDK tools generate this certificate when you do a release build. You can also generate this certificate using the keytool program. Use this certificate when you are ready to release your app to the world.

Follow the steps below to display a certificate's SHA-1 fingerprint using the keytool program with the -v parameter. For more information about Keytool, see the Oracle documentation.

Displaying the debug certificate fingerprint

  1. Locate your debug keystore file. The file name is debug.keystore, and is created the first time you build your project. By default, it is stored in the same directory as your Android Virtual Device (AVD) files:

    • macOS and Linux: ~/.android/
    • Windows Vista and Windows 7: C:Usersyour_user_name.android
  2. List the SHA-1 fingerprint:

    • For Linux or macOS, open a terminal window and enter the following:

    • For Windows Vista and Windows 7, run:

Google Home Chromecast App For Mac

You should see output similar to this: