Jafar Abedi
Jafar Abedi

Reputation: 133

Error "Status{statusCode=PLACES_API_INVALID_APP, resolution=null}" when using google places api in android

I am using google maps in my android app and map successfully loaded in my app. I initialize google map in my app with this code :

mGoogleApiClient = new GoogleApiClient.Builder(this)
                .addConnectionCallbacks(this)
                .addOnConnectionFailedListener(this)
                .addApi(Places.GEO_DATA_API)
                .addApi(Places.PLACE_DETECTION_API)
                .addApi(LocationServices.API)
                .enableAutoManage(this, this)
                .build();

And google places api was worked for me very well, but today an error occurred when using place auto complete! this is first time that this error is occurred :

Status{statusCode=PLACES_API_INVALID_APP, resolution=null}

I using the correct api key and all of my code is correct because it worked until today. But suddenly this error occurred. Please help me :) thanks in advance

Upvotes: 5

Views: 8335

Answers (5)

Jirawut Chayapong
Jirawut Chayapong

Reputation: 11

if you have issue on publish app on Google play console.

Release mangement > app signing > App signing certificate SHA1

Your app public certificate was changed to new one.

Lets check at here first.

Upvotes: 1

nicolas asinovich
nicolas asinovich

Reputation: 3511

If all that is listed here does not help - try set to no restrictions in google api console, it helped me

Upvotes: 0

Jorge Casariego
Jorge Casariego

Reputation: 22212

In my case the error was because I put

<meta-data
      android:name="com.google.android.geo.API_KEY"
      android:value="{MY_KEY}"/>

outside Application tag. After adding inside Application tag all began to work

Upvotes: 2

Harish
Harish

Reputation: 141

If you have changed your system after generating the api key then you have to update the current system SHA key in the google api console.

Upvotes: 1

iagreen
iagreen

Reputation: 32016

That error indicates something is wrong with you API setup - either the package name or signature is wrong. If you didn't change your code, the mostly likely thing that is wrong is you signed the app with a different key. If you --

1) Changed from debug to release mode, or

2) Are compiling on a different computer or install of AS in debug mode

Then it is likely that you have to add another SHA-1 fingerprint to your API key. Follow the instructions on getting your SHA-1 fingerprints here -- https://developers.google.com/places/android-api/signup. Check in the API console to make sure you've added all the necessary keys.

Upvotes: 4

Related Questions