Introduce CI checks for binaries in our NDK release AAR - Githubissues

getsentry / sentry-native

Sentry SDK for C, C++ and native applications.

MIT License

395 stars 166 forks source link

Introduce CI checks for binaries in our NDK release AAR #998

Open supervacuus opened 4 months ago

supervacuus commented 4 months ago

Since we now have a binary release channel, we should introduce checks regarding exported symbol stability (we have a linker-script for libsentry.so but not for libsentry-android.so, etc.) and similar issues that could break usage.

These should run on any push to ensure changes to build scripts are immediately (i.e., in the PR and not during release/publish) highlighted as breaking.

The trigger for this is unexpected binaries that the prefab build seemingly adds to the release artifact: https://github.com/getsentry/sentry-native/pull/996

This relates slightly to https://github.com/getsentry/sentry-native/issues/997 regarding where to introduce the check and how to run it.