Manual human steps to publish LibreMail to the Samsung Galaxy Store. Signing prerequisites are shared with Google Play — see the "Release signing keystore + CI publishing secrets" ticket. (The general compliance audit is tracked by #15.)
Steps (human)
Register a Samsung Galaxy Store seller/developer account; complete seller profile (and commercial-seller / tax info if charging — LibreMail is free).
Create the app + listing; set content/age rating and category.
Signing: produce a release AAB/APK signed with the release key (see the signing/secrets ticket); confirm Galaxy Store's version-code policy (monotonic increasing per upload).
Store assets — icon, screenshots, feature graphic, short/full description (reuse the drafts/fastlane metadata prepared for Play where the formats allow).
Address Samsung-specific review items — permission rationale (READ_CONTACTS, POST_NOTIFICATIONS, FOREGROUND_SERVICE_DATA_SYNC; reuse docs/play-permissions.md), background-service justification, and any Knox/DeX considerations.
Submit for review; respond to Galaxy Store reviewer feedback until accepted.
Relates to #25: Samsung exposes a default-email association on some devices, so "default mail app where supported" can be offered here.
(Optional automation) If Galaxy Store's developer API is usable, add its credentials to CI secrets for #19's workflow; otherwise document the manual upload as the Galaxy path.
Acceptance criteria
App accepted through Galaxy Store review with a complete listing.
## Context
Manual **human** steps to publish LibreMail to the Samsung Galaxy Store. Signing prerequisites are shared with Google Play — see the "Release signing keystore + CI publishing secrets" ticket. (The general compliance audit is tracked by #15.)
## Steps (human)
- [ ] Register a **Samsung Galaxy Store seller/developer** account; complete seller profile (and commercial-seller / tax info if charging — LibreMail is free).
- [ ] Create the app + listing; set **content/age rating** and category.
- [ ] **Signing**: produce a release AAB/APK signed with the release key (see the signing/secrets ticket); confirm Galaxy Store's **version-code policy** (monotonic increasing per upload).
- [ ] **Store assets** — icon, screenshots, feature graphic, short/full description (reuse the drafts/fastlane metadata prepared for Play where the formats allow).
- [ ] Address **Samsung-specific review items** — permission rationale (`READ_CONTACTS`, `POST_NOTIFICATIONS`, `FOREGROUND_SERVICE_DATA_SYNC`; reuse `docs/play-permissions.md`), background-service justification, and any **Knox/DeX** considerations.
- [ ] Submit for review; respond to Galaxy Store reviewer feedback until accepted.
- [ ] Relates to #25: Samsung exposes a default-email association on some devices, so "default mail app where supported" can be offered here.
- [ ] (Optional automation) If Galaxy Store's developer API is usable, add its credentials to CI secrets for #19's workflow; otherwise document the manual upload as the Galaxy path.
## Acceptance criteria
- App accepted through Galaxy Store review with a complete listing.
## Dependencies
Signing/secrets ticket; #19 (publish automation); #25 (default app on Samsung); #15 (audit).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
Manual human steps to publish LibreMail to the Samsung Galaxy Store. Signing prerequisites are shared with Google Play — see the "Release signing keystore + CI publishing secrets" ticket. (The general compliance audit is tracked by #15.)
Steps (human)
READ_CONTACTS,POST_NOTIFICATIONS,FOREGROUND_SERVICE_DATA_SYNC; reusedocs/play-permissions.md), background-service justification, and any Knox/DeX considerations.Acceptance criteria
Dependencies
Signing/secrets ticket; #19 (publish automation); #25 (default app on Samsung); #15 (audit).