cordova-plugin-googlemaps: Reopen #1919 & #2291: Bottom part of ionic tabs is not clickable

I’m submitting a … (check one with “x”)

  • question
  • any problem or bug report

OS: (check one with “x”)

  • Android
  • iOS
  • Browser

cordova information: (run $> cordova plugin list)

com.googlemaps.ios 2.7.0 "Google Maps SDK for iOS"
cordova-plugin-device 2.0.2 "Device"
cordova-plugin-googlemaps 2.4.1 "cordova-plugin-googlemaps"
cordova-plugin-ionic-keyboard 2.1.2 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 2.1.0 "cordova-plugin-ionic-webview"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-whitelist 1.3.3 "Whitelist"

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)

@ionic-native/core : 4.12.0
@ionic-native/google-maps : 4.12.0

Current behavior: Bottom part of Ionic tabs are not clickable when Cordova Google Maps is installed. Same issue as described in #1919 and #2291, seems still not fixed. When Cordova Google Maps is installed the tabs are only clickable in the upper two thirds, as it can be seen in the following video.

Expected behavior: Bottom part of Ionic tabs clickable. For testing I completely removed the Cordova Google Maps Plugin. Afterwards the tabs are clickable everywhere, just as expected. See the second video below.

Repository: Repository with non working example

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 19 (19 by maintainers)

Commits related to this issue

Most upvoted comments

Merged. Thanks.

I just checked with Ionic Starters Tabs and it’s currently only in a half working state. They are calling methods of the cordova-plugin-statusbar but don’t completely install it. I filed an issue with them to confirm if they plan to keep this plugin as default (https://github.com/ionic-team/starters/issues/430).

I will try looking into the hitTest myself. Would be awesome if you also have a shot at my new demo and confirm that we actually have a bug/problem when using both plugins together. Thank you very much again!