New app: Resonance

AlanHuangrequested to merge
lahuangao/fdroiddata:resonance into master

Required

  • The app complies with the inclusion criteria
  • The original app author has been notified (and does not oppose the inclusion). I am the author.
  • All related fdroiddata and RFP issues have been referenced in this merge request. There is no RFP issue; I am submitting directly as the upstream author.
  • Builds with fdroid build and all pipelines pass. On my fork, fdroid build, check apk, lint, schema, and the format checks all pass; the only failing job is the unrelated weblate merge conflict one, which fails while rebasing the translation branch (a known fork-only quirk, not related to this app).
  • There is an issue tracker and contact info of the author so that we can report bugs and contact the author.

Strongly Recommended

  • The upstream app source code repo contains the app metadata (summary/description/images/changelog) in a Fastlane folder structure
  • Releases are tagged and auto update is enabled

Suggested

  • External repos are added as git submodules instead of srclibs
  • Enable Reproducible Builds — No, I do not want this. The build does not byte-reproduce across environments (confirmed on CI), so the APK should be signed with the F-Droid key.
  • Multiple apks for native code

Merge request reports