Project is Dead? (only supported)

[reslear]

The company has shown no activity here for the past four months, aside from some community PR efforts. Is it fair to assume the project is dead?

Update Aug 2024 - Last week, the project was updated to Capacitor 6 #33, but there’s no sign of active development or new features at the moment.

Hi team, I was wondering if there are any updates or plans for new features, particularly #14. Would you be able to share your priorities or the timeline for reviewing current PRs? Thank you!

[reslear]

To get the latest changes by @ae1ns:

Details

1. Compilation Plugin

1. Download the repo https://github.com/AE1NS/capacitor-google-maps/tree/custom-4 and open it in an editor (first window).
2. Open the terminal and run pnpm i && pnpm build.

2. Patch Plugin

If you don't have pnpm, use https://www.npmjs.com/package/patch-package.

1. Go to your project, open it in an editor (second window), and run pnpm patch @capacitor/google-maps.
2. Open the temp folder in a new window (third window):

➜ pnpm patch @capacitor/google-maps
Patch: You can now edit the package at:

  /private/var/folders/r5/0wg5rcy547dcpq9l0s47ylhr0000gn/T/dbd378357f0642dbc8d9a8c131d6852a

1. Copy and override the files/folders from the compile step to the temp folder:

• android/src/main/
• dist/
• ios/Plugin/
• package.json

1. Run the patch command printed above:

To commit your changes, run:

  pnpm patch-commit '/private/var/folders/r5/0wg5rcy547dcpq9l0s47ylhr0000gn/T/dbd378357f0642dbc8d9a8c131d6852a'

You can close the first and third windows.

3. App

1. Add to your app's package.json:

  "pnpm": {
    "overrides": {
      "@googlemaps/js-api-loader": "^1.16.2"
    }
  }

1. Run pnpm install && pnpm cap sync.

2. Enjoy! Thanks @ae1ns.

Patch file: @capacitor__google-maps@6.0.0-rc.0.patch

[AE1NS]

https://www.npmjs.com/package/@capacitor-a1/google-maps

Includes

PRs

• feat(google-maps): Refactored options and added feature to update the map options #26
• feat: Implemented map feature functions (i.e. GeoJSON support) #19
• feat: Optimize @googlemaps/js-api-loader to use importLibrary method #21
• fix(ios): fixed getTargetContainer calculation #24

Additional features

• Feature to add marker as base64

Additional bugfixes

• touchstart outside map and touchend on map caused scroll issue in application after ionic backdrops appeared
• Refactored .removeFirst() method to .removeAt(0)
  • Using Kotlin's removeFirst() and removeLast() extension functions on MutableList can lead to runtime crashes when your app is compiled with compileSdk 35 (Android 15) and run on devices with Android 14 or lower. This issue arises because Android 15 introduces new removeFirst() and removeLast() methods in the Java List interface. Consequently, when you compile against API level 35, the Kotlin compiler binds calls like list.removeFirst() to the new Java methods. On devices running Android 14 or lower, these methods don't exist, resulting in a NoSuchMethodError at runtime.

[AE1NS]

Updated to 7.2.0-a1.1
https://www.npmjs.com/package/@capacitor-a1/google-maps

Includes

PRs

• feat: Use functional API of @googlemaps/js-api-loader #148
• feat(google-maps): Refactored options and added feature to update the map options #26
• feat: Implemented map feature functions (i.e. GeoJSON support) #19

Additional features

• Feature to add marker as base64

Additional bugfixes

• touchstart outside map and touchend on map caused scroll issue in application after ionic backdrops appeared
• Removed fallback for mapId to allow custom styles

[wahibimoh]

Updated to 7.2.0-a1.1 https://www.npmjs.com/package/@capacitor-a1/google-maps

Includes

PRs

• feat: Use functional API of @googlemaps/js-api-loader #148
• feat(google-maps): Refactored options and added feature to update the map options #26
• feat: Implemented map feature functions (i.e. GeoJSON support) #19

Additional features

• Feature to add marker as base64

Additional bugfixes

• touchstart outside map and touchend on map caused scroll issue in application after ionic backdrops appeared
• Removed fallback for mapId to allow custom styles

Hi, I used version 7.2.0-a1.1 in order to be able to style the map, however, whenever I add a marker, I am getting this error:
The map is initialized without a valid Map ID, which will prevent use of Advanced Markers.

I am not sure how to make a marker as a legacy marker?

Thanks,,

[AE1NS]

Hey,

first of all, you should use the latest 8.0.0-a1.0. I rebased on the main branch and didnt recognize, that the plugin was already prepared for capacitor 8. (And 7.0.0-a1.1 has a bug with iOS.)

I made the mapId optional, so it must be set manually like this:

const newMap = await GoogleMap.create({
    mapId: 'YOUR_MAP_ID',
    ...
});

I removed the "fallback" from the code (random generated id), to be able to use local stylings in my map.

I didnt check it yet, but if markers were completely refactored to advanced markers, you are right, then it seems not to be possible to add legacy markers... then you can only set a mapId to get it run.

[AE1NS]

Updated to 8.0.1-a1.0
https://www.npmjs.com/package/@capacitor-a1/google-maps

Includes

PRs

• feat(google-maps): Refactored options and added feature to update the map options #26
• feat: Implemented map feature functions (i.e. GeoJSON support) #19

Features

• Feature to add marker as base64

Bugfixes

• touchstart outside map and touchend on map caused scroll issue in application after ionic backdrops appeared

[AE1NS]

Updated to 8.0.1-a1.3
https://www.npmjs.com/package/@capacitor-a1/google-maps

Includes

PRs

• feat(google-maps): Refactored options and added feature to update the map options #26
• feat: Implemented map feature functions (i.e. GeoJSON support) #19
• feat(android): Set mapColorScheme to MapColorScheme.FOLLOW_SYSTEM #170

Features

• Feature to add marker as base64

Bugfixes

• touchstart outside map and touchend on map caused scroll issue in application after ionic backdrops appeared