Hey everyone!
I’m currently hitting a bit of a brick wall trying to integrate Hexnode into our CI/CD pipeline, and I’m wondering if anyone else has cracked this.
We are building an internal Android app—let’s call it Project AeroTrack—which is a custom Flutter app used by our warehouse staff on their rugged scanners. Since it’s strictly internal, it’s not published on the Google Play Store.
Right now, our manual workflow is tedious:
- A developer pushes a commit to GitHub.
- GitHub Actions builds the release APK.
- Someone manually downloads the artifact, logs into the Hexnode portal (Apps → Apps Inventory → Add App → Enterprise → Upload File), uploads it, and pushes it to our device groups.
I’m trying to fully automate this via the Hexnode API so GitHub Actions can just push the APK directly. However, when I call POST with the payload, the API rejects it outright.
I’ve thrown every other string I can think of at it, but they all return as invalid choices. The manual UI upload handles enterprise APKs flawlessly, so I’m really confused why the public API is blocking it. Has anyone managed to successfully automate their in-house APK deployments over the API?
Thanks in advance!
13 Views
