Cordova GoogleMaps plugin for Android, iOS and Browser v2.6.2, Download, Build test (master branch), ----------, ---------------------------,
,
, This plugin displays Google Maps in your application.
This plugin uses these libraries for each platforms:
- Android : Google Maps Android API
- iOS : Google Maps SDK for iOS
- Browser : Google Maps JavaScript API v3
Both PhoneGap and Apache Cordova are supported.
Guides
Quick install
-
Stable version(npm)
$> cordova plugin add cordova-plugin-googlemaps
-
Development version(beta version)
$> cordova plugin add https://github.com/mapsplugin/cordova-plugin-googlemaps#multiple_maps
PhoneGap Build settings
<widget ...>
<!--
You need to specify cli-7.1.0 or greater version.
https://build.phonegap.com/current-support
-->
<preference name="phonegap-version" value="cli-8.1.1" />
</widget>
Install optional variables
-
PLAY_SERVICES_VERSION = (15.0.1)
The Google Play Services SDK version.
You need to specify the same version number with all other plugins.
Check out the latest version here. -
ANDROID_SUPPORT_V4_VERSION = (27.1.1)
This plugin requires the Android support library v4.
The minimum version is 24.1.0.
Check out the latest version here. -
LOCATION_WHEN_IN_USE_DESCRIPTION
This message is displayed when your application requests LOCATION PERMISSION for only necessary times. -
LOCATION_ALWAYS_USAGE_DESCRIPTION
This message is displayed when your application requests LOCATION PERMISSION for always.
Browser platform
We support browser platform now!
You can develop your application with browser, then run it!
At the end of development, you can upload the html files to your server, or run it on Android or iOS devices.
$> cordova run browser
If you use ionic framework, it supports live-reload
.
$> ionic cordova run browser -l
If you want to use live-reload
, but you don't want to use other framework or without framework,
cordova-plugin-browsersync is useful.
$> cordova plugin add cordova-plugin-browsersync
$> cordova run (browser/android/ios) -- --live-reload
API key (Android and iOS platforms)
As of v2.6.0, you need to specify your API keys in config.xml
file instead of --variable
.
This allows you to change your API keys for anytime without reinstallation.
Please pay attention the variable names are changed.
<widget ...>
<preference name="GOOGLE_MAPS_ANDROID_API_KEY" value="(api key)" />
<preference name="GOOGLE_MAPS_IOS_API_KEY" value="(api key)" />
</widget>
API key (Browser platform)
In the browser platform, the maps plugin uses Google Maps JavaScript API v3
You need to set two API keys for Google Maps JavaScript API v3.
// If your app runs this program on browser,
// you need to set `API_KEY_FOR_BROWSER_RELEASE` and `API_KEY_FOR_BROWSER_DEBUG`
// before `plugin.google.maps.Map.getMap()`
//
// API_KEY_FOR_BROWSER_RELEASE for `https:` protocol
// API_KEY_FOR_BROWSER_DEBUG for `http:` protocol
//
plugin.google.maps.environment.setEnv({
'API_KEY_FOR_BROWSER_RELEASE': '(YOUR_API_KEY_IS_HERE)',
'API_KEY_FOR_BROWSER_DEBUG': ''
});
// Create a Google Maps native view under the map_canvas div.
var map = plugin.google.maps.Map.getMap(div);
Why two API keys?
JavaScript
code is text code
. Even if you do obfuscation, it's still readable finally.
In order to protect your API key, you need to set Key restriction
for these keys.
If you don't set API key, the maps plugin still work with development mode
.
plugin.google.maps.environment.setEnv({
'API_KEY_FOR_BROWSER_RELEASE': '(YOUR_API_KEY_IS_HERE)',
'API_KEY_FOR_BROWSER_DEBUG': '' // If key is empty or unset,
// the maps plugin runs under the development mode.
});
Which browser supported?
Modern browsers should work without any problem.
Internet Explorer 11 might work. We don't confirm all features, but basic features work.
Behavior differences
Google Maps JavaScript API v3
is completely different ecosystem with Google Maps Android API
and Google Maps SDK for iOS
.
Google Maps JavaScript API v3
:
- can't draw 3D building,
- does't work if offline,
- can't map rotation,
- etc...
In the browser platform, the maps plugin works almost the same behaviors as native platforms(Android, and iOS),
but not exactly the same behaviors.
So don't expect too much.
Touch mechanism difference
As you may know, this plugin displays native Google Maps view under the browser in Android and iOS.
However this plugin displays as normal HTML element
in browser platform.
Because of this, touch behavior is different.
The maps plugin does not hook the touch position, do not set background: transparent
, ... etc.
But if you use this plugin as normal behavior, you don't need to consider about this.
Please support this plugin activity.
In order to keep this plugin as free, please consider to donate little amount for this project.
Release Notes
-
v2.6.1
- Fix: (Android) build error
-
v2.6.1
- Fix: (Android) Conflicting with
OneSignal-Cordova-SDK
- Fix: (iOS) App crashes when marker url isn't valid.
- Fix: (Android) Conflicting with
-
v2.6.0
- Fix: Can not install to Cordova 9.0 project
- Fix: (Android)
ConcurrentModificationException
error atonStop
- Fix: (Android) Polygon becomes visible when you run
setPoints()
to invisible polygon - Fix: (Android/iOS) TileOverlay does not work when your app runs on
file:
protocol with ionic. - Update: (iOS) Specify the Google Maps SDK version as
=> 3.1.0
. Please usecordova-ios@5.0.0
or above, otherwise modifyplatform/ios/Podfile
. - Add: (Android/iOS) API Key mechanism
Demos
Documentation
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.3.0/README.md
Quick examples
What is the difference between this plugin and Google Maps JavaScript API v3?
Google Maps JavaScript API v3 works on any platforms,
but it does not work if device is offline.
This plugin uses three different APIs:
- Android : Google Maps Android API
- iOS : Google Maps SDK for iOS
- Browser : Google Maps JavaScript API v3
In Android and iOS applications, this plugin displays native Google Maps views, which is faster than Google Maps JavaScript API v3.
And it even works if the device is offline.
In Browser platform, this plugin displays JS map views (Google Maps JavaScript API v3).
It should work as PWA (progressive web application), but the device has to be online.
In order to work for all platforms, this plugin provides own API instead of each original APIs.
You can write your code similar to
the Google Maps JavaScript API v3.
Feature comparison table, Google Maps JavaScript API v3, Cordova-Plugin-GoogleMaps(Android,iOS), Cordova-Plugin-GoogleMaps(Browser), ----------------, -----------------------------------, ---------------------------------------, ---------------------------------------, Rendering system, JavaScript + HTML, JavaScript + Native API's, JavaScript, Offline map, Not possible, Possible (only your displayed area), Not possible, 3D View, Not possible, Possible, Not possible, Platform, All browsers, Android and iOS applications only, All browsers, Tile image, Bitmap, Vector, Bitmap, Class comparison table, Google Maps JavaScript API v3, Cordova-Plugin-GoogleMaps, -----------------------------------, ---------------------------------------, google.maps.Map, Map, google.maps.Marker, Marker, google.maps.InfoWindow, Default InfoWindow, and HtmlInfoWindow, google.maps.Circle, Circle, google.maps.Rectangle, Polygon, google.maps.Polyline, Polyline, google.maps.Polygon, Polygon, google.maps.GroundOverlay, GroundOverlay, google.maps.ImageMapType, TileOverlay, google.maps.MVCObject, BaseClass, google.maps.MVCArray, BaseArrayClass, google.maps.Geocoder, plugin.google.maps.geocoder, google.maps.geometry.spherical, plugin.google.maps.geometry.spherical, google.maps.geometry.encoding, plugin.google.maps.geometry.encoding, google.maps.geometry.poly, plugin.google.maps.geometry.poly, (not available), MarkerCluster, google.maps.KmlLayer, KmlOverlay, (not available), LocationService, google.maps.StreetView, StreetView :sparkles:, google.maps.Data, (not available), google.maps.DirectionsService, (not available), google.maps.DistanceMatrixService, (not available), google.maps.TransitLayer, (not available), google.maps.places., (not available), google.maps.visualization., (not available), ### How does this plugin work (Android, iOS)?
This plugin generates native map views, and puts them under the browser.
The map views are not HTML elements. This means that they are not a <div>
or anything HTML related.
But you can specify the size and position of the map view using its containing <div>
.
This plugin changes the background to transparent
in your application.
Then the plugin detects your touch position, which is either meant for the native map
or an html element
(which can be on top of your map, or anywhere else on the screen).
The benefit of this plugin is the ability to automatically detect which HTML elements are over the map or not.
For instance, in the image below, say you tap on the header div (which is over the map view).
The plugin will detect whether your tap is for the header div or for the map view and then pass the touch event appropriately.
This means you can use the native Google Maps views similar to HTML elements.
Official Communities
-
Gitter : (managed by @Hirbod)