-
Notifications
You must be signed in to change notification settings - Fork 103
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
Access to sessionPresent after automatic reconnect #43
Comments
Hmm, is there a call |
The My workaround at the moment is to disable automatic Reconnect. And to reestablish the connection after 3secs |
Note: The first connection made through |
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you! |
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you! |
Thanks for this fork and the maintenance.
I am testing a persistent connection between app and broker:
I am using the sessionPresent flag after a successul connection to decide if a new subscription is necessary: If server acknowlegdes the connection and set the sessionPresent=true, the app wont need new subscriptions.
But I can't access the sessionPresent flag after a automatic reconnect, because the
onSuccess
-callback of myIMqttActionListener
is not called. Only the IMqttActionListeneronSuccess
-callback contains the token for that flagAm I wrong with my concept of connection and subscription - or might it be useful to implement some sort of access to that sessionPresent flag during the reconnection?
The text was updated successfully, but these errors were encountered: