Skip to content
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

Closed
samuraikid0 opened this issue Apr 28, 2023 · 7 comments · May be fixed by #3642
Closed

UnifiedPush not working on tusky 22 #3591

samuraikid0 opened this issue Apr 28, 2023 · 7 comments · May be fixed by #3642

Comments

@samuraikid0
Copy link

samuraikid0 commented Apr 28, 2023

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.

@SteveDinn
Copy link

Not sure if this is an issue or not, but each time I reboot my phone, I get a new entry in the UP-FCM app.

Screenshot_20230429-220920

@samuraikid0
Copy link
Author

Not sure if this is an issue or not, but each time I reboot my phone, I get a new entry in the UP-FCM app.

Screenshot_20230429-220920

Im using nextpush not UP-FCM, sorry for not mention it

@Lakoja
Copy link
Collaborator

Lakoja commented Apr 30, 2023

(Slightly?) related #3468

@Lakoja
Copy link
Collaborator

Lakoja commented Apr 30, 2023

@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)?
I have been looking in the code and see one problem: One cannot change the provider (distributor) at the moment. Tusky cannot recognize that and the server then happily tries to use a wrong url (the endpoint of the old one).

If you want to you can try to wipe all Tusky data and/or uninstall completely.
(Which will also delete everything else local: e. g. drafts, login, tab configuration)

@samuraikid0
Copy link
Author

@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)? I have been looking in the code and see one problem: One cannot change the provider (distributor) at the moment. Tusky cannot recognize that and the server then happily tries to use a wrong url (the endpoint of the old one).

If you want to you can try to wipe all Tusky data and/or uninstall completely. (Which will also delete everything else local: e. g. drafts, login, tab configuration)

All the above

Jami notifications via nextpush work, Up-Example test app sends the notification test

Tusky doesn't send any notification at all

@SteveDinn
Copy link

@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

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! :)

@samuraikid0
Copy link
Author

solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants