librepods-org / librepods-org/librepods
Use a different application ID for FOSS builds
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi there.
I installed the FOSS APK from GitHub Releases, but Google Play started recognizing it and now offers an update to the Play Store version.
I assume this happens because both builds use the same application ID ("me.kavishdevar.librepods").
Would it make sense to use a separate ID for FOSS builds, e.g. "me.kavishdevar.librepods.foss" (possibly via "applicationIdSuffix")?
This would prevent Google Play from offering Play Store updates for FOSS installations.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Android Gradle configuration for the FOSS APK and review how its application ID is set. Verify the resulting FOSS package can be installed alongside the Play Store version and that Google Play no longer offers it as an update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100