|
Artur Hefczyc opened 10 years ago
|
|
|
It seems to be working OK under Chrome browser. |
|
After quick check it looks like Safari specific issue which closes BOSH connection without returning specific error (returns connection broken). As I checked WebSocket connection when used works fine. I will investigate more to find why Safari decided that connection is broken. At first glance it looks like beta version at http://beta.sure.im/ which is not fully finished works fine on Safari. I suppose that we could fix issue by updating version on sure.im after small changes to UI look in version available at http://beta.sure.im |
|
|
As I mentioned above I was only able to replicate this issue on stable version of sure.im project which is now deployed on sure.im site. New version (beta at http://beta.sure.im) is free from this issue. When I checked logs I found issues with following entries: I know that follwing issue was appearing in older version of Jaxmpp2 and is already fixed. I think that best would be to take beta version which is more or less stable right now and fix icons in new styling to make it more visible and deploy this new version on sure.im site as we will need to upgrade site to new version at some point. |
|
|
Ok, I agree, let's update the stable with what we have on the beta now. |
|
|
I checked last version of Sure.IM which was deployed on http://beta.sure.im/ and as it was working fine, I deployed latest Sure.IM project on http://sure.im/ |
|
|
Yes, it works now, both websites. However, there is a minor glitch. When I enter my login details and press ENTER the "Authenticate" button changes to gray for a few seconds and then goes blue again. Then when I click on the button using mouse, it quickly logins to the service. By the way, I think "authenticate" button should be changed to "Login", but it's really minor. minor thing. |
| Type |
Bug
|
| Priority |
Critical
|
| Assignee | |
| RedmineID |
2445
|
I use Safari on Mac and go to address: http://tigase.im
Provide login details. If login details are incorrect, the client correctly reports login failure. If I provide correct login details, the client goes for a second to the client (like a successful login) and then jumps back to login screen.