-
Notifications
You must be signed in to change notification settings - Fork 16
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
Cannot use this app on non-Google Android phones because of Google services #12
Comments
Yes, exactly the same problem here. Running GrapheneOS on Google Pixel 4 (no Google services). I have seen many Bitcoiners who use GrapheneOS (and other privacy focused degoogled Android phones), so it would be nice if this could be solved. |
Link to further discussion: bisq-network/bisq#2441 |
Threema just implemented push notifications on Android without FCM. |
I agree that a non-Google notification alternative would be a substantial improvement to this app. Using Unified Push like @geekley suggested also appears to me like the most promising solution. ntfy for instance could be, from what I understand, configured as a drop-in replacement for Google's Firebase Cloud Messaging (the standard Google notification system). For lazy users, notifications would be routed via ntfy's servers - and more advanced users could self-host ntfy to be completely independent. |
Due to the reliance on Google services, this app cannot be used on non-Google Android devices.
I procured the SDK for my Android LineageOS phone (via Aurora Store, F-Droid) but upon open the Pair button is greyed out, and a few seconds later the following popup message appears:
Note: I did not press the Pair button at any point.
My device is connected to the internet, and I can press the Learn More button to prove this.
It's worth noting that this issue would not be that important except for the presumption that Bisq has a relatively significant number of users who own non-Google Android phones due to its nature as an anonymous and decentralised method of exchanging Bitcoin and other cryptos.
The text was updated successfully, but these errors were encountered: