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

Push inactive due to "No Used Tokens" #773

Open
ossguy opened this issue May 19, 2017 · 3 comments
Open

Push inactive due to "No Used Tokens" #773

ossguy opened this issue May 19, 2017 · 3 comments

Comments

@ossguy
Copy link

ossguy commented May 19, 2017

Upon first installing ChatSecure a few days ago, I was using an XMPP account whose server (Prosody) did not support Push (XEP-0357). Since then, the server administrator has added mod_cloud_notify but I still can't get Push enabled in ChatSecure. In particular, I see the following:

chatsecure-no_used_tokens

When I click Reset, I get the same screen back again. When I go to the URL mentioned in the above image, I get the following:

chatsecure-api_description

I suspect that's just the API documentation that I shouldn't need to see (since mod_cloud_notify should be implementing that already). Or is there extra implementation needed beyond what mod_cloud_notify would provide?

Note that pressing the information ("i") button does not provide further details as far as I can tell. So I'm not sure what next steps to take to enable Push in ChatSecure for this server.

@chrisballinger
Copy link
Member

It looks like push mostly works (server is advertising support), but it can't register with the server's push module for whatever reason. There have been reports of issues of newer versions of Prosody and mod_cloud_notify, but I haven't tested against them yet. What happens if you manually log out / log in, or restart the app?

@ossguy
Copy link
Author

ossguy commented May 21, 2017

I re-opened the app about a day later and found that it had indeed registered (1 used token, with green check). However, later in the day today I noticed that it had somehow unregistered and showed "XMPP server incompatible", but before I could take a screenshot, it had registered again and had the green check (with 5 used tokens).

I'll keep watching it, but I'm a bit concerned generally about it randomly unregistering, as it seems fairly common so far, and a pretty bad thing for a notification-centered app to be doing. I'm not as aware of general mod_cloud_notify interaction issues - if that's the case I guess some coordination with the Prosody (and/or mod_cloud_notify) people would be in order.

Overall it appears that ChatSecure has never stayed in the MUC that I've had it join for more than 7 minutes, and usually for less than 1 minute. To me this makes it feel like push isn't working properly/at all.

Are there particular open-registration servers supporting XEP-0357 that you've found that work well with ChatSecure? Maybe jabjab.de or others listed on https://jmp.chat/suggested_servers.html ? I haven't tried any of those yet, but would be happy to if one or more seem likely to work.

@aHVzY2g
Copy link

aHVzY2g commented May 26, 2017

+1

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

No branches or pull requests

3 participants