timusus
Submit to F-Droid
I don't know what's involved here. I'd like to do this, but it would be great if I could get some help, as I have even more on my plate than usual having just released Shuttle as an open source app.
https://f-droid.org/contribute/
See https://f-droid.org/wiki/page/Inclusion_Policy.
This would require adding a build flavor without Crashlytics, firebase and play services.
Meanwhile, attaching the .apk to releases/ (and dropping me a note) could bring it into my repository (F-Droid compatible) immediately, see Creating Releases for details on how to achieve that (pretty easy, no much time spent on it).
Also infos why for example services like play services are needed would be nice.
@Thaodan seeing vending.CHECK_LICENSE being requested, one of the reasons in the free version might be upgrading to Shuttle+ via IAP – which should not hurt being removed from the FOSS version. I'd still be interested for what a music player might need GCM, though :wink:
Shuttle uses Play Services for Firebase integration (analytics). GCM != Play Services.
I'm working towards automating apk deployment, firstly to the releases section of Github. Once that's done, I'll create an F-droid branch of the project which removes Crashlytics/Firebase.
@IzzySoft it's not F-droid ready yet. Still need to create a version without Play-Services/Crash lyrics.
As for AppBrain, I'm not sure why it's getting a false-positive for GCM.. Maybe something to do with Firebase..
Understood, @timusus – still, if you include my repo with your F-Droid client, it now is available by that, including updates whenever you create a new tag and attach an .apk to it. Just follow the link to see for yourself :smiley_cat: But yes, for the official repo it would need that special version.
As someone who only get apps from F-droid it would be lovely if you could make it compatible with the official branch 👍
Just joining my voice here, thank you for open sourcing it !
