You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Downloading notification token...
Are you connected to the internet?
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:
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.
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: