Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish app to F-droid #21

Open
haroldadmin opened this issue Dec 17, 2019 · 5 comments
Open

Publish app to F-droid #21

haroldadmin opened this issue Dec 17, 2019 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed huge Time consuming and large in scope

Comments

@haroldadmin
Copy link
Owner

  • Replace Firebase Crashlytics in that module with ACRA
  • Evaluate and setup the Acrarium backend to receive crash reports
  • Publish the completed module to F-droid
@haroldadmin haroldadmin added enhancement New feature or request huge Time consuming and large in scope labels Dec 17, 2019
@haroldadmin
Copy link
Owner Author

A few problems to consider with this issue:

  • Firebase Crashlytics is great. The crash reports are exhaustive, and even though the analytics are simple, they are still valuable.
  • There is no compelling free service to host a backend server for ACRA. Using email for crash reporting is alternative, but it really does not seem like a good idea.
  • To create an F-droid specific module, the dynamic feature modules will have to conditionally depend on one of the base app modules: the one published to the play store, and the one published to f-droid. I can maybe accomplish this using product flavours, but I am not sure how I would do it.

If someone else wants to help out with this issue, you're welcome to. Adding the help wanted label.

@haroldadmin haroldadmin changed the title Create an F-Droid specific module and publish it Publish app to F-droid Dec 22, 2019
@haroldadmin haroldadmin added the help wanted Extra attention is needed label Dec 22, 2019
@haroldadmin haroldadmin pinned this issue Dec 24, 2019
@subbramanil
Copy link

Hey @haroldadmin, I have prior experience with ACRA in one of my work products. We used a combination of firebase along with ACRA. I'm a bit hazy on the details of the backend server. I can help setting up a rudimentary solution, can't promise a lot as it's been a while. That is if this is still relevant.

I haven't published any apps to F-droid; it would be a learning curve.

@haroldadmin
Copy link
Owner Author

@subbramanil Thank you for your interest in this issue. I think it would be better to split the ACRA task from this issue, since publishing to F-Droid and changing the crash reporting service are two separate tasks.

We can first focus on moving to ACRA, and look at publishing to F-Droid after that.

@haroldadmin
Copy link
Owner Author

Here's the ACRA issue: #32
Let's continue the discussion there.

@subbramanil
Copy link

@subbramanil Thank you for your interest in this issue. I think it would be better to split the ACRA task from this issue, since publishing to F-Droid and changing the crash reporting service are two separate tasks.

We can first focus on moving to ACRA, and look at publishing to F-Droid after that.

It makes more sense. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed huge Time consuming and large in scope
Projects
None yet
Development

No branches or pull requests

2 participants