Skip to content

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

Description

@supervacuus

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: #996

This relates slightly to #997 regarding where to introduce the check and how to run it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Nativeplatform labelTasktasks like repository maintenance, dependencies, e.t.c.

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions