You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2025. It is now read-only.
Suddenly for the past week more repro APKs can't be verified.
eg. https://github.com/Futsch1/medTimer/releases/tag/v1.8.10 has unsigned and signed
They have in common a thing, they get built by the Github CI, eg. signed here with apksigner from build-tools 35: https://github.com/Futsch1/medTimer/actions/runs/9750431791/job/26909848960#step:16:5
CI recipes use
ubuntu-latesteg. https://github.com/Futsch1/medTimer/blob/v1.8.10/.github/workflows/android.yml#L14 so maybe the Github image got updated to build-tools 35 and now CI's just end up using it by defaultapksigcopier can't cope with whatever apksigner 35 does?