search

festelo / h3_dart

The package provides Dart version of the H3 Core library, a hexagon-based geographic grid system
https://pub.dev/packages/h3_flutter
Apache License 2.0
18 stars 7 forks source link

is this package maintained anymore? #28

Open paapu88 opened 1 month ago

paapu88 commented 1 month ago

Hei, It seems last update for this package is 15 months old, and h3 4.x is not implemented. Additionally I get with flutter run and connected android phone the following, which to my understanding comes from new google-requirements this package does not fullfill.

So is this package dead? Terveisin, Markus

flutter run
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':h3_flutter'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 3s
Running Gradle task 'assembleDebug'...                              4.0s
Error: Gradle task assembleDebug failed with exit code 1
paapu88 commented 1 month ago

There is no answer here, so I assume it confirms my observation that this package is obsolete and should not be used anymore.

I go around the problem by writing geojson on with python h3 library and reading geojson in flutter. Terveisin, Markus

festelo commented 1 month ago

Hi, You're right, there's no active development for this project and it's pretty much abandoned. Unfortunately, I don't use this package anymore and currently have no time to develop it further. I do, however, have some drafts for 4.x and hope to finish them at some point, but I wouldn't make any promises.

At this point, If you can avoid this package, i would suggest doing so, or maybe creating a fork (PRs are welcome, too).

As for the problem you mentioned - it looks like something simple to fix, so I'll try to look into this more these/next weekends, thank you for reporting it.

I would keep this issue open, if you don't mind, because I think it's important for the project.

paapu88 commented 1 month ago

Thanks! I managed get around with just geojson, but I think many people would benefit from your voluntary work. Terveisin, Markus