-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
UnifiedPush not working on tusky 22 #3591
Comments
(Slightly?) related #3468 |
@SteveDinn Does this really happen on every reboot? I have also three entries there but that is because I have three accounts configured in Tusky. @samuraikid0 Did you "change" something to do with unified push lately (weeks/months)? If you want to you can try to wipe all Tusky data and/or uninstall completely. |
All the above Jami notifications via nextpush work, Up-Example test app sends the notification test Tusky doesn't send any notification at all |
That is entirely possible. I also have 3 accounts, but I also rebooted 3 times. It's more likely that it's due to the accounts, but I didn't think of that! :) |
solved |
Running lineageOs with Up-Example app I'm able to receive the test notification, on tusky I don't receive any notification
By the way Im running 0 google services
Any clue or it's tusky broken ?
Thanks !
Tusky Version: 22 beta, 21
Android Version: 13
Android Device: samsung
[ x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
The text was updated successfully, but these errors were encountered: