Page MenuHomePhabricator

Get Wikipedia app on f-droid
Closed, ResolvedPublic


F-Droid is a FOSS App Store available for Android, and has hosted our apps in the past. Should get the app on it at some point.

This is going to be fairly difficult since they apparently no longer accept build processes that require remote repositories. Since the Android app uses both Maven Central and our own remote repo (and there is no intention of changing that anytime soon), this is going to be a fairly difficult task.

I think for now people without access to the play store should just get the APKs from Leaving this bug open to see if things change.

Version: Android (alpha)
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 3:21 AM
bzimport set Reference to bz65460.
bzimport added a subscriber: Unknown Object (MLST).

We could theoretically upload the java-mwapi jar to jcentral. Needs some investigation. I don't think they allow snapshot versions. I think it best to depend on a release version anyways when we release the app.

Do we have an idea of the theoretical user base that we would gain by putting the app on f-droid?

I don't see download numbers or statistics on the app page:

Deskana claimed this task.

This bug lacks sufficient information for us to know what we need to do to resolve it. If you can provide such information, please do provide that information and reopen the bug.

From the maintainer notes, it looks like the issues are:

  • Use of custom Maven repo --> T105235
  • Time stamp in versionName --> T105230
  • "rework updatechecks". I guess this refers to the AlphaUpdate of our Alpha flavor.
    • We should mention the F-droid maintainer that we are using Gradle and Gradle flavors now. Any other flavor than alpha will not use this functionality.

A custom fdroid release apk can be built using:

$ ./gradlew -q clean assembleCustomRelease -PcustomChannel=fdroid
Output: wikipedia/build/outputs/apk/wikipedia-custom-release.apk

From mvdan's comments on IRC in mobile channel today it looks like the main blocker is the custom Maven repo. The other things are optional. We should ping him again, once the repo situation has been solved.

We've removed the one blocker T105235.

Once we publish a new stable release (and it gets tagged in Git) then the f-droid project should be able to build the apk using a command line similar to in my previous comment.

We've published a couple of production releases since then. Ready for F-droid to pick this up again. Going to ping mvdan on #fdroid IRC channel.

Minor update to the build instructions. The output will be now in a slightly different location since we renamed the wikipedia folder to app.

So, the instructions are:

$ ./gradlew -q clean assembleCustomRelease -PcustomChannel=fdroid
Output: app/build/outputs/apk/app-custom-release.apk

Feel free to rename it to whatever filename you want afterwards.

We've also updated the ~/.sign/ file since the last stable release. So, in the future this would need to be adjusted. See for the diffs and app/build.gradle for the signing code.

FYI, We've tagged a new release on Friday: r/2.0.109-r-2015-08-21

Great news: mvdan from F-droid updated the config:

[server] mvdan pushed to master: Add support for gradle properties via gradleprops -
[data] mvdan pushed 2 commits to master -

The fdroid app should be built tomorrow at midnight UTC. We just missed it by a couple of minutes.

The version number will be 2.0.109-fdroid. He highly encourages us to drop the date in versionName for production and beta app builds. (T105230)

We should update the app description on

Never mind. Mvdan helped us out again. :)

I have the latest version on my phone now. We should keep track of automating newer builds. Thanks all