Android: automatically choose debug/release Maps v2 api key?

Solution 1:

Using build.gradle

buildTypes {

    debug {
        buildConfigField("String", "map_api_key", "\"your debug map api key here\"")
    }
    release {
        buildConfigField("String", "map_api_key", "\"your release map api key here\"")
    }
}

I solved this issue using this steps:

In Google Developer API Console

1. Click on Create New Android key...
2. In cmd.exe/Terminal: keytool -list -v -keystore mystore.keystore
3. Password: android
4. Now enter SHA1 key;package name for debug and press enter
5. Enter SHA1 key;package name for release
6. Click on Create

Now use this API key your project

<meta-data
    android:name="com.google.android.maps.v2.API_KEY"
    android:value="@string/common_map_api_key"/>

Solution 2:

One of the Best way to use build.gradle file in latest Android 5.0 and Android 6.0, Android 9+ (API 20, 21,22,23, 24, 25,26, 27 28, 29)

Well you can use them simply without creating product flavors in gradle. This is another example we can achieve via Gradle. You can achieve it with two simple steps.

• Add custom value to manifestplaceholders build.gradle file.

See below

buildTypes {
    debug {
        manifestPlaceholders = [ mapApiKeyValue:"GHjaSyAjlyp3O831lgaonHMXsd-_DpQ3002x3S4"]
    }

    release {
        manifestPlaceholders = [ mapApiKeyValue:"AIzaSyAuMGDLr2HeuRed4JA0CrdYYdZRjeC3EA"]
    }
}

• Edit manifest file like below.

part of my manifest file

  <meta-data
        android:name="com.google.android.maps.v2.API_KEY"
        android:value="${mapApiKeyValue}" />

This solution works for the latest Android 5.0 and Android 6.0 (API 20, 21,22,23)

Updated on 5/3/2018 for Xamarin Form and Xamarin Native Apps

Open AssemblyInfo.cs in Android Project and addd the following code

#if DEBUG
   [assembly: MetaData("com.google.android.maps.v2.API_KEY", Value = "DebugKey123123123")]
#else
   [assembly: MetaData("com.google.android.maps.v2.API_KEY", Value = "ReleaseKey123123123")]
#endif

To Check the AndroidManifest file, goto obj/Debug/android folder and open the manifest file and check the meta info,

<meta-data
        android:name="com.google.android.maps.v2.API_KEY"
        android:value="DebugKey123123123" />

Solution 3:

For organizations that need to maintain separate keys, you can place them in separate directories in Android Studio. Make sure the subdirectory of src you use matches a flavor or buildType

From Building Your Project with Gradle:

To build each version of your app, the build system combines source code and resources from:

src/main/ - the main source directory (common to all variants)
src/<buildType>/ - the build type source directory
src/<flavorName>/ - the flavor source directory

In projectroot/yourapp/build.gradle:

buildTypes {
    debug {
        runProguard false
        debuggable true

    }
    release {
        runProguard true
        debuggable false
        ...
    }

In projectroot/yourapp/src/main/AndroidManifest.xml:

...
<application
    android:name=".MyApplication"
    android:theme="@style/Theme">
<!-- Don't put your key here -->
...

In projectroot/yourapp/src/debug/AndroidManifest.xml, fully qualify the name of the app.

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <application android:name="com.hipmunk.android.HipmunkApplication">
        <meta-data
            android:name="com.google.android.maps.v2.API_KEY"
            android:value="yourdebugkey" />
    </application>
</manifest>

In projectroot/yourapp/src/release/AndroidManifest.xml:

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <application android:name="com.hipmunk.android.HipmunkApplication">
        <meta-data
            android:name="com.google.android.maps.v2.API_KEY"
            android:value="release key" />
    </application>
</manifest>