@lhk wrote:
Hi,
I would like to add some native code to my app.
As a starting point, I worked through the capacitor plugin guide which sets up a project with:npx @capacitor/cli plugin:generateBased on this template, I implemented the functionality and a small app that tests it (it’s really minimal).
By the way: It’s really a pleasure to work with capacitor. The plugin system works like a charm.Now I need to port the functionality over to my actual project. Since it is not published to npm or anything, I would just like to copy over the Java/Kotlin code.
This brings up a problem: The gradle build systems that are created for a plugin project and for a “normal” ionic project with
ionic cap add androidseem very different.
For example, the project that was created for my plugin relies ongoogle-services 4.3.3and brings in an androidX dependency. While the project that is set up withionic cap androidonly needsgoogle-services 4.2.0and no androidX. The file structure is very different, too. The plugin build system extracts lots of variables out to separate files, etc.So far there was no custom android code in my project. So I deleted
android/andbuild/, updated all npm packages, both local and global, then recreated the android code.
It’s still the same: old google services, no androidX.I think it should be straightforward to configure gradle to bring in the dependencies that my plugin code needs.
But to be honest, gradle is a bit scary to me. In my experience it’s super unstable and tends to go haywire when you misconfigure something.
So if possible, I would like to avoid reconfiguring the gradle buildchain.
Is there a way to set upionic cap androidto generate the same basis as for plugin development?And what is the correct way to version control this?
Usually, I always add gradle to git. But then again, here it is created automatically. So that would be a good reason to keep it out of the repository. How do you deal with this?
Posts: 1
Participants: 1