It looks to be logging in, and has started to download the roster then it just crashes and goes back to the home screen.  If I quickly tell it to put me offline, I can keep the app running, but as soon as I connect again it will crash.

I have a very large roster, but that didn’t seem to bother previous versions of OneTeam.  I have also turned downloading of the roster to manual and it still crashes.

Any ideas?

Oh, and I have been clicking “yes” when it asks if I want to submit the crash to you guys to help debug.  Not sure if that does anything, but I figured it may not hurt.

Eric

Ok, more info… I believe it is getting the full roster just fine, it is when it is trying to update everyones status is when it crashes.  I have re-installed the app just to make sure nothing there was messed up. 

Any ideas?

Eric

Wow, 58 views and no responses?  Has anyone else had this issue since the update?

We apologize for the problems, we are working on this issue and will have an updated version soon. Thanks for notifying us.

I am seeing the same issue (just bought the app today)... When I open the app and the auth credentials are correct, I see it show ‘Connecting’ then it indicates ‘Unknown Error’ then fails back to the screen showing “Warning: Invalid Jabber-ID or password. Please enter a valid Jabber-ID and password.”. At this point, the application crashes back to the home screen.

The credentials are correct from what I can see, when I had the wrong username/password it would just fail at this point and let me change the username/password.

Let me know how I can assist (packet captures etc.) The server I am connecting to requires TLS and I can see in captures that the TLS negotiation is working OK.

Update: I have tried uninstalling 3.1.0 and re-installing 3.1.0 without any benefit.

Update: If I switch my status to Offline before it crashes then the application will stay open. As soon as I move to another state (Away/Busy) the app crashes the same as noted above… ‘Unknown Error’

We think we have found and fix the problem that could occur sometimes on roster update.
We have submitted OneTeam 3.1.1 to Apple.

Sorry about the problem. You should have a fix quite fast, right after Apple validation.

Thanks Mickaël. I will keep you posted once I see the update.

Any idea when the fix will be approved?  Do they have an emergency system to get patches for big issues such as this?  I’m really missing oneteam and my ability to do groupchats.

Eric

It has been submitted on sunday, more than one week ago. It should arrive soon as usually it takes 5 days.

At last, the app has been approved.

Could you please upgrade and let us know if it helps ?

Hi!
I´ve just installed 3.1.1 but when I join a crowded group chat it crashes. And the background service does not exist at all?

//S

An app cannot go in background on iPhone at all.
You have to use push system. This require a compliant server. You can either create an account on oneteam.im from the app or deploy our commercial ejabberd module on your server.

Regarding the crash: which chat room do you join ?

I know that a application can not run in the background on the iPhone, I thought that It would use Apple background-notification system like QuickSilver or AIM.
I use a locally installed ejabberd and have created a channel. It feels like it crashes when there is a lot of history in the channel to be displayed.

I have sent a few crash-reports I guess :)

//S

Mickaël, I just upgraded to the newly release 3.1.1 after first uninstalling OneTem 3.1.0. Unfortunately it still crashes with the same symptoms… Starts to log in, displays the ‘Unknown Error’ message, and then indicate an incorrect Username/Password and then crashes.

In this case we need to reproduce your problem. Can we have a test account that show the problem on your server ?