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

dc_get_push_state() returns wrong value since recent update #6320

Closed
r10s opened this issue Dec 8, 2024 · 1 comment · Fixed by #6322
Closed

dc_get_push_state() returns wrong value since recent update #6320

r10s opened this issue Dec 8, 2024 · 1 comment · Fixed by #6322
Assignees
Labels
bug Something is not working

Comments

@r10s
Copy link
Member

r10s commented Dec 8, 2024

on iOS, dc_get_push_state() returns DC_PUSH_HEARTBEAT (1) even though chatmail is used and push notifications are working (just tested)

expected return value in this case is DC_PUSH_CONNECTED (2)

i do not know exactly when this but was introduced, i've noticed the connectivity warning some days ago, but investigated just now.

to be clear: the functionality seems okay, but the status is reported wrong. still, the correct status is important for debugging; that area is pretty sensible :)

this is how the connectivity looks like - the "yellow warning dot" should be a "green ok dot" on chatmail:

maybe related to recent changes in that area, #6239

@r10s r10s added the bug Something is not working label Dec 8, 2024
@r10s
Copy link
Member Author

r10s commented Dec 8, 2024

ftr, it works on non-sandbox atm (just switched to ios1.50.1 from apple store)

EDIT: reading the fix, on next push-token-set, we would subscribe to both again, resulting in DC_PUSH_HEARTBEAT being reported again

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

Successfully merging a pull request may close this issue.

2 participants