Skip to content
This repository has been archived by the owner on Jun 16, 2019. It is now read-only.

triggerClusterClick is not captured when running on Android #143

Open
memphis23 opened this issue Feb 22, 2018 · 5 comments
Open

triggerClusterClick is not captured when running on Android #143

memphis23 opened this issue Feb 22, 2018 · 5 comments

Comments

@memphis23
Copy link

The event triggerClusterClick is not captured when running on Android.
In order to test that you can open https://googlemaps.github.io/js-marker-clusterer/examples/simple_example.html on an Android, and doubleclick on a cluster, it is not captured, therefore it is processed as a doubleclick on the map and a zoom level +1 is applied.

@denis1994
Copy link

The same on iOS since a few days.

@sharecube
Copy link

sharecube commented Feb 23, 2018

  • the same problem with .apk on Ionic 3

@kunal-saini
Copy link

the same problem occurred to me.
I have been able to figure out a temporary fix. I just specified API's version along with key in the script tag. i.e. v=3& between js? and key=... in my <script> tag. this seems to work fine now!

@marzubov
Copy link

marzubov commented Feb 24, 2018

@kunal-saini wow thanks, you saved my day.

As it turns out gmaps broke marker-clusterer tap handler with one of the latest EXPERIMENTAL releases.
Adding v3& loads release version which works fine with marker-clusterer.

From Google Maps docs:

You can indicate which version of the API to load in your application by specifying the v parameter of the Google Maps JavaScript API bootstrap request. The following options are supported:

  • The experimental version, specified with v=3.exp.
  • The release version, specified with v=3.
  • A specific version number. For example v=3.29 or v=3.30.

If you do not explicitly specify a version, you will receive the experimental version by default if you are on the standard plan (this includes customers who do not provide a key). If you're on the premium plan and don't specify a version, you will receive the release version by default.

@memphis23
Copy link
Author

Thank you so much @kunal-saini & @marzubov.
Specifying the release version has solved the problem. I did not know that the experimental version is used by default if you are not using a Premium plan.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants