Originally created by @thebiblelover7 on GitHub (Dec 12, 2021).
Could the app be added to F-droid? It would be great exposure for the app and for the users. Nowadays, I don't download almost anything from the Play Store and would still like to download the app.
Originally created by @thebiblelover7 on GitHub (Dec 12, 2021).
Could the app be added to F-droid? It would be great exposure for the app and for the users. Nowadays, I don't download almost anything from the Play Store and would still like to download the app.
Thanks ahead of time!
---
*You can check the link below on how to submit the app*
https://f-droid.org/en/contribute/
adam
added the android label 2026-04-24 23:03:58 +02:00
I think the app meets the requirements, but I still need to clean up and trim down the dependencies.
For example, the app is using the google play core library to check for and install in-app updates from the play store. This is not even reliable at the moment so I think it can go.
Both Android Auto and media casting are google libraries, do you know if these are supported in F-Droid apps?
@advplyr commented on GitHub (Dec 12, 2021):
I think the app meets the requirements, but I still need to clean up and trim down the dependencies.
For example, the app is using the google play core library to check for and install in-app updates from the play store. This is not even reliable at the moment so I think it can go.
Both Android Auto and media casting are google libraries, do you know if these are supported in F-Droid apps?
@thebiblelover7 commented on GitHub (Dec 13, 2021):
I think the app meets the requirements, but I still need to clean up and trim down the dependencies.
For example, the app is using the google play core library to check for and install in-app updates from the play store. This is not even reliable at the moment so I think it can go. Both Android Auto and media casting are google libraries, do you know if these are supported in F-Droid apps?
I think they are supported. I just think that it will show a dialog that says that it has non-free dependencies.
@thebiblelover7 commented on GitHub (Dec 13, 2021):
> I think the app meets the requirements, but I still need to clean up and trim down the dependencies.
>
> For example, the app is using the google play core library to check for and install in-app updates from the play store. This is not even reliable at the moment so I think it can go. Both Android Auto and media casting are google libraries, do you know if these are supported in F-Droid apps?
I think they are supported. I just think that it will show a dialog that says that it has non-free dependencies.
@advplyr commented on GitHub (Jan 28, 2022):
For those looking for this in the meantime I have been putting the APK file in the releases. https://github.com/advplyr/audiobookshelf-app/releases
Thanks @advplyr for creating this application and providing compiled Android releases on Github.
Can you share any progress regarding an official release in F-Droid?
@essys commented on GitHub (Mar 1, 2023):
Thanks @advplyr for creating this application and providing compiled Android releases on Github.
Can you share any progress regarding an official release in F-Droid?
There are some third-party F-Droid repos that are less strict than the official one that could also be used to distribute the app for users without Google Play on their devices (even as a stop-gap while waiting to get into the official repo).
I suggested Audiobookshelf to IzzyOnDroid, which is a pretty popular one that doesn't actually build the apps, instead publishing the APKs directly from the application's own Github or Gitlab releases and tags. It does have some requirements that Audiobookshelf doesn't meet currently (the maintainer detailed that in my issue here), but something like this might be a simpler goal post to hit along the road to the official F-Droid repo.
@rudism commented on GitHub (Feb 7, 2024):
There are some third-party F-Droid repos that are less strict than the official one that could also be used to distribute the app for users without Google Play on their devices (even as a stop-gap while waiting to get into the official repo).
I suggested Audiobookshelf to IzzyOnDroid, which is a pretty popular one that doesn't actually build the apps, instead publishing the APKs directly from the application's own Github or Gitlab releases and tags. It does have some requirements that Audiobookshelf doesn't meet currently (the maintainer detailed that in [my issue here](https://gitlab.com/IzzyOnDroid/repo/-/issues/493#note_1756427211)), but something like this might be a simpler goal post to hit along the road to the official F-Droid repo.
The APK will work without google play, that is only for chromecast support which if not available just won't show up in the app.
Last I looked at the f-droid criteria I thought it was met already
@advplyr commented on GitHub (Feb 7, 2024):
The APK will work without google play, that is only for chromecast support which if not available just won't show up in the app.
Last I looked at the f-droid criteria I thought it was met already
I think the requirement (for both F-Droid and IzzyOnDroid) is there needs to be a whole separate build path that can generate an APK without any of the Google libraries in there at all. It's not enough for the app to function without Play Services on the phone, it has to be built without them entirely.
In the case of IzzyOnDroid they would want each release to have a separate APK that was built without the proprietary dependencies, and in the case of F-Droid they expect to be able to build from source themselves without any of those dependencies being linked.
@rudism commented on GitHub (Feb 7, 2024):
I think the requirement (for both F-Droid and IzzyOnDroid) is there needs to be a whole separate build path that can generate an APK without any of the Google libraries in there at all. It's not enough for the app to function without Play Services on the phone, it has to be built without them entirely.
In the case of IzzyOnDroid they would want each release to have a separate APK that was built without the proprietary dependencies, and in the case of F-Droid they expect to be able to build from source themselves without any of those dependencies being linked.
@advplyr I doubt it complies. Copying over from the issue @rudism linked already:
Offending libs:
---------------
* Firebase Data Transport (/com/google/android/datatransport): NonFreeNet
* Google Cast (/com/google/android/gms/cast): NonFreeComp
* Google Mobile Services (/com/google/android/gms): NonFreeComp
* Firebase (/com/google/firebase): NonFreeNet,NonFreeComp
4 offenders.
Dangerous flags:
----------------
* usesCleartextTraffic
SigningBlock blobs:
-------------------
0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)
Everything marked NonFreeComp is a show-stopper at F-Droid: non-free components are not permitted.
@IzzySoft commented on GitHub (Mar 3, 2024):
@advplyr I doubt it complies. Copying over from the issue @rudism linked already:
```
Offending libs:
---------------
* Firebase Data Transport (/com/google/android/datatransport): NonFreeNet
* Google Cast (/com/google/android/gms/cast): NonFreeComp
* Google Mobile Services (/com/google/android/gms): NonFreeComp
* Firebase (/com/google/firebase): NonFreeNet,NonFreeComp
4 offenders.
Dangerous flags:
----------------
* usesCleartextTraffic
SigningBlock blobs:
-------------------
0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)
```
Everything marked `NonFreeComp` is a show-stopper at F-Droid: non-free components are not permitted.
I add an other bit of info: I'm not sure that f-droid version can be compatible with Android Auto. At least, voice from f-droid was not.
I can test with some music player if it can help!
@Ansem93 commented on GitHub (Mar 9, 2024):
I add an other bit of info: I'm not sure that f-droid version can be compatible with Android Auto. At least, voice from f-droid was not.
I can test with some music player if it can help!
Hello, we have been waiting for more than 4 years to see audiobookshelf on FDroid, many here do not use Google Play Store and prefer OpenSource solutions. Please publish AudioBookShelf as soon as possible in FDroid
@miltuss commented on GitHub (Oct 5, 2024):
Hello, we have been waiting for more than 4 years to see audiobookshelf on FDroid, many here do not use Google Play Store and prefer OpenSource solutions. Please publish AudioBookShelf as soon as possible in FDroid
I add an other bit of info: I'm not sure that f-droid version can be compatible with Android Auto. At least, voice from f-droid was not. I can test with some music player if it can help!
Users will not be able to use it with android auto, but if you leave the code in then users will be able to enable allow unknown sources in android auto developer options use it. There are apps on f-droid that do this like auxio and have no anti-features.
@realeatham commented on GitHub (Oct 6, 2024):
> I add an other bit of info: I'm not sure that f-droid version can be compatible with Android Auto. At least, voice from f-droid was not. I can test with some music player if it can help!
Users will not be able to use it with android auto, but if you leave the code in then users will be able to enable allow unknown sources in android auto developer options use it. There are apps on f-droid that do this like auxio and have no anti-features.
You could also put this up on izzyondroid, as that would be your own build. At least that would give us an option that's not google play.
@dessalines commented on GitHub (Nov 7, 2024):
You could also put this up on izzyondroid, as that would be your own build. At least that would give us an option that's not google play.
Can easily be avoided with a minor addition to your build.gradle:
android{dependenciesInfo{// Disables dependency metadata when building APKs.
includeInApk=false// Disables dependency metadata when building Android App Bundles.
includeInBundle=false}}
For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.
Nice to see there are dev instructions in the Readme! Unfortunately, they end with starting Android Studio. Would there be an "alternative ending" building the app at the command line? Ah, found them in github/workflows. So we could try for Reproducible Builds even 😉 "Real releases" (instead of pre-releases only) would help with that, too. But meh, seems that's moot as AudioBookshelf is not reproducible: nuxt produces non-deterministic file names for its *.js files unfortunately 😢
AntiFeatures:NonFreeComp:en-US:The app contains libraries of Google Cast, Google Mobile Services and Firebase.de:Die App enthält Bibliotheken von Google Cast, Google Mobile Services und Firebase.NonFreeNet:en-US:The app potentially connects to Google Servers (Firebase).de:Die App verbindet sich potentiell zu Google Servern (Firebase).
Are those libraries really needed? Maybe a FOSS flavor could be established coming without them?
@IzzySoft commented on GitHub (Nov 7, 2024):
PS: I had to add…
```yaml
AntiFeatures:
NonFreeComp:
en-US: The app contains libraries of Google Cast, Google Mobile Services and Firebase.
de: Die App enthält Bibliotheken von Google Cast, Google Mobile Services und Firebase.
NonFreeNet:
en-US: The app potentially connects to Google Servers (Firebase).
de: Die App verbindet sich potentiell zu Google Servern (Firebase).
```
Are those libraries really needed? Maybe a FOSS flavor could be established coming without them?
@IzzySoft IMO I would add it as it is today, with the known anti-features and dependencies. There is already another app on F-Droid, but would be great to have the official one. I see Firebase as the blocker for today, is there a known alternative? Would you consider using an alternative @advplyr ?
@staticdev commented on GitHub (Sep 30, 2025):
@IzzySoft IMO I would add it as it is today, with the known anti-features and dependencies. There is [already another app](https://github.com/GrakovNe/lissen-android) on F-Droid, but would be great to have the official one. I see Firebase as the blocker for today, is there a known alternative? Would you consider using an alternative @advplyr ?
@staticdev as you ping me: the above shows it is already at IzzyOnDroid "as it is today".
I see Firebase as the blocker for today, is there a known alternative?
Firebase is probably just dragged in as dependency by Cast. As an alternative for Cast, it might be worth taking a look at microG, which according to their wiki at least has partial Cast support. Apart from that, I cannot tell what Firebase might be used here; depending on that, there could be alternatives. If it's for push notifications, I'd recommend UnifiedPush – see e.g. here in our wiki.
@IzzySoft commented on GitHub (Sep 30, 2025):
@staticdev as you ping me: the above shows it is already at IzzyOnDroid "as it is today".
> I see Firebase as the blocker for today, is there a known alternative?
Firebase is probably just dragged in as dependency by Cast. As an alternative for Cast, it _might_ be worth taking a look at microG, which [according to their wiki](https://github.com/microg/GmsCore/wiki/Implementation-Status) at least has partial Cast support. Apart from that, I cannot tell what Firebase might be used here; depending on that, there [could be alternatives](https://gitlab.com/-/snippets/1896503#firebase-per-se). If it's for push notifications, I'd recommend UnifiedPush – see e.g. [here in our wiki](https://gitlab.com/IzzyOnDroid/repo/-/wikis/Developer-Best-Practices/Useful-Links#push-notifications).
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.
Originally created by @thebiblelover7 on GitHub (Dec 12, 2021).
Could the app be added to F-droid? It would be great exposure for the app and for the users. Nowadays, I don't download almost anything from the Play Store and would still like to download the app.
Thanks ahead of time!
You can check the link below on how to submit the app
https://f-droid.org/en/contribute/
@advplyr commented on GitHub (Dec 12, 2021):
I think the app meets the requirements, but I still need to clean up and trim down the dependencies.
For example, the app is using the google play core library to check for and install in-app updates from the play store. This is not even reliable at the moment so I think it can go.
Both Android Auto and media casting are google libraries, do you know if these are supported in F-Droid apps?
@thebiblelover7 commented on GitHub (Dec 13, 2021):
I think they are supported. I just think that it will show a dialog that says that it has non-free dependencies.
@advplyr commented on GitHub (Jan 28, 2022):
For those looking for this in the meantime I have been putting the APK file in the releases. https://github.com/advplyr/audiobookshelf-app/releases
@essys commented on GitHub (Mar 1, 2023):
Thanks @advplyr for creating this application and providing compiled Android releases on Github.
Can you share any progress regarding an official release in F-Droid?
@shuvashish76 commented on GitHub (Oct 2, 2023):
RFP : https://gitlab.com/fdroid/rfp/-/issues/2554
@rudism commented on GitHub (Feb 7, 2024):
There are some third-party F-Droid repos that are less strict than the official one that could also be used to distribute the app for users without Google Play on their devices (even as a stop-gap while waiting to get into the official repo).
I suggested Audiobookshelf to IzzyOnDroid, which is a pretty popular one that doesn't actually build the apps, instead publishing the APKs directly from the application's own Github or Gitlab releases and tags. It does have some requirements that Audiobookshelf doesn't meet currently (the maintainer detailed that in my issue here), but something like this might be a simpler goal post to hit along the road to the official F-Droid repo.
@advplyr commented on GitHub (Feb 7, 2024):
The APK will work without google play, that is only for chromecast support which if not available just won't show up in the app.
Last I looked at the f-droid criteria I thought it was met already
@rudism commented on GitHub (Feb 7, 2024):
I think the requirement (for both F-Droid and IzzyOnDroid) is there needs to be a whole separate build path that can generate an APK without any of the Google libraries in there at all. It's not enough for the app to function without Play Services on the phone, it has to be built without them entirely.
In the case of IzzyOnDroid they would want each release to have a separate APK that was built without the proprietary dependencies, and in the case of F-Droid they expect to be able to build from source themselves without any of those dependencies being linked.
@IzzySoft commented on GitHub (Mar 3, 2024):
@advplyr I doubt it complies. Copying over from the issue @rudism linked already:
Everything marked
NonFreeCompis a show-stopper at F-Droid: non-free components are not permitted.@Ansem93 commented on GitHub (Mar 9, 2024):
I add an other bit of info: I'm not sure that f-droid version can be compatible with Android Auto. At least, voice from f-droid was not.
I can test with some music player if it can help!
@miltuss commented on GitHub (Oct 5, 2024):
Hello, we have been waiting for more than 4 years to see audiobookshelf on FDroid, many here do not use Google Play Store and prefer OpenSource solutions. Please publish AudioBookShelf as soon as possible in FDroid
@realeatham commented on GitHub (Oct 6, 2024):
Users will not be able to use it with android auto, but if you leave the code in then users will be able to enable allow unknown sources in android auto developer options use it. There are apps on f-droid that do this like auxio and have no anti-features.
@dessalines commented on GitHub (Nov 7, 2024):
You could also put this up on izzyondroid, as that would be your own build. At least that would give us an option that's not google play.
@IzzySoft commented on GitHub (Nov 7, 2024):
As @dessalines suggests it… Quick check:
for the self-hosted server in the local network only, right?
Can easily be avoided with a minor addition to your
build.gradle:For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.
Nice to see there are dev instructions in the Readme! Unfortunately, they end with starting Android Studio.
Would there be an "alternative ending" building the app at the command line?Ah, found them ingithub/workflows. So we could try for Reproducible Builds even 😉 "Real releases" (instead of pre-releases only) would help with that, too. But meh, seems that's moot as AudioBookshelf is not reproducible: nuxt produces non-deterministic file names for its*.jsfiles unfortunately 😢APK diff
If you have any ideas there, I gladly try again.
Complete "short output" from the scanners here:
So I guess the storage permission is for accessing audio books stored locally on the device?
Meanwhile, AudioBookshelf should show up here with the next sync around 7 pm UTC. Be welcome to pick a badge to link there e.g. from your Readme 😃
@IzzySoft commented on GitHub (Nov 7, 2024):
PS: I had to add…
Are those libraries really needed? Maybe a FOSS flavor could be established coming without them?
@staticdev commented on GitHub (Sep 30, 2025):
@IzzySoft IMO I would add it as it is today, with the known anti-features and dependencies. There is already another app on F-Droid, but would be great to have the official one. I see Firebase as the blocker for today, is there a known alternative? Would you consider using an alternative @advplyr ?
@IzzySoft commented on GitHub (Sep 30, 2025):
@staticdev as you ping me: the above shows it is already at IzzyOnDroid "as it is today".
Firebase is probably just dragged in as dependency by Cast. As an alternative for Cast, it might be worth taking a look at microG, which according to their wiki at least has partial Cast support. Apart from that, I cannot tell what Firebase might be used here; depending on that, there could be alternatives. If it's for push notifications, I'd recommend UnifiedPush – see e.g. here in our wiki.
@minecraftchest1 commented on GitHub (Oct 1, 2025):
I would personally perferr DLNA support rather then Chromecast support.
@soupy-boy commented on GitHub (Nov 13, 2025):
Has there been any progress on this? Just curious.