You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think user issue was not adressed and i meet the same behaviour.
I know how to set up application id and SHA1 as i have set up others API keys in my current project.
It appears that with this package linked to Direction API, when we set up an Android or iOS restriction we got a
get route Exception: Unable to get route: Response ---> REQUEST_DENIED
If we use same Android/iOS restricted keys for Google map, for geocoding and for Direction API, it works for the first 2 but not for Direction API.
Below the screen shot API interface which cannot be set up with Android/iOS restrictions so i have to set up to 'none' which is not too secure
The text was updated successfully, but these errors were encountered:
Hi,
I have seen previous issue.
#23
I think user issue was not adressed and i meet the same behaviour.
I know how to set up application id and SHA1 as i have set up others API keys in my current project.
It appears that with this package linked to Direction API, when we set up an Android or iOS restriction we got a
If we use same Android/iOS restricted keys for Google map, for geocoding and for Direction API, it works for the first 2 but not for Direction API.
Below the screen shot API interface which cannot be set up with Android/iOS restrictions so i have to set up to 'none' which is not too secure
The text was updated successfully, but these errors were encountered: