Thomas Eizinger
Thomas Eizinger
That is not the issue. We were already building against NDK 27.0.12077973. The problem is that we can only ever build against one NDK version and the latest image update...
> > Instead of removing the old NDK, can you first **add** the new NDK to an image release? That would give us time to migrate to the new version....
> > The issue is that you can only build an Android App against a single, specific NDK version. Your rollout seems to be incremental, which makes sense. But it...
I can do that yeah. I am not sure what the point of the pre-installed NDK is then if your advice is to install a separate version?
> We will announce major version removals in advance. Android only allows to build against a specific NDK, thus even a change to a patch version of the NDK is...
Yey, it is broken again :tada: :tada: :tada: https://github.com/firezone/firezone/actions/runs/11450062859/job/31856868142?pr=7103
@tamird Fixed!
The CI error seems unrelated to my change :(
I am actually planning to collect metrics from Clients and Gateways to a centralised collector, see #7419. Just haven't had the time to implement it yet! I'll look at this...
> Oh, that would be great to have. My opinion would be to keep a standard protocol (like OTLP and not things like sentry, posthog) to allow self-hosted admins and...