|
Artur Hefczyc opened 7 years ago
|
|
%kobit Are you sure that iOS device was connected when its account received presence subscription request? I'm asking as I was testing it and all was working fine before. Also, you can modify subscription of a contact from the iOS device, just select |
|
|
Thank you for comments. I will retest it to ensure this is really a problem with software not with me. |
|
|
After some additional tests I had some successes and some problems with inconsistent behaviour. However, I do not have any step-by-step instructions to actually confirm specific problem. Maybe, again, this is problem with roster changes population across cluster. Closing for now and will reopen when I have a specific, step-by-step instructions. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
6003
|
| Version |
Version 2.0
|
This might be a problem with either the Tigase server and/or iMessages client.
Description:
Logged into tigase.im account on one iOS device and logged into jabber.today account on another iOS device and on iMessages on my laptop.
Sent presence subscription request from tigase.im account to the jabber.today account
iMessages received request and I pressed accept.
At this point it all looked like one-way subscription only and no way to resent subscription request or authorization
While this might be iMessages error, there are a few issues on our software as well:
The subscription request was delivered only to iMessages, not to iOS client which was online at the same time - this might need some fixes on the server side
There was no way to recover from this "broken" presence subscription situation. It would be good to have some information on the iOS client about subscription state and a way to correct it (resent authorization or subscription request).