If you are having any problems connecting to servers or have experienced other issues. Post them in the comments below. I am aware of at least one case where someone wasn't able to connect to a jabber server using "old style SSL" i am looking into that. Everything else, comment away.
This comment has been removed by the author.
ReplyDeleteI was saying that for me the program doesn't even come up. I get a black screen and after 5 seconds, back to the icons.
ReplyDeleteThis is with SSL or without.
I'm VPN'd in my job and trying to connect to a Spark Server. Thanks
Feels very sticky, using SSL to talk.google.com. When I tapped on a contact expecting to be able to type a message nothing happens, took me a long time to discover the text input field and > 5 seconds for anything to happen there... and keystrokes accordingly... sloooow.
ReplyDeleteI'd say this is unusable
I havent tested with a spark server. I'll do that.
ReplyDeletei am also experiencing the sticky issue. I am trying to get a fix out asap.
thanks,
This comment has been removed by the author.
ReplyDeleteSorry about the typos...
ReplyDeleteI downloaded the app yesterday. Each time I launch it, it pops up a window saying "Missing Username - please set the username in Settings before using SworIM". I assume this is a reference to the "Status" section. The problem is no matter what I try doing, I *cannot* input/edit the Server, Resource & User fields. I see the labels, but no text-input fields to their right. What am I missing here?
Jay,
ReplyDeleteClick on they ipod/iphone's Settings icon, scroll down you will see sworim there.
Thanks. Not very obvious. It would help if the popup message was something like "please first set SworIM's connection parameters using iPhone's Preferences [icon]".
ReplyDeleteAside from that, I am unable to connect to my company's OpenFire (XMPP) server. The iPhone is currently on the same LAN via port 2222 (thus no firewall issue). With SSL disabled, the app is stuck with message "Logging In...". When SSL is enabled, it immediately reports "Initiation Error - Could not initiate connection. Make sure settings are correct".
I've tried numerous combination of specifying and omitting the domain name from the username and from the Domain fields to no avail.
On Windows and Mac OSX, I've had no problem connecting with the OpenFire server using various clients such as Spark, Pidgin and Adium.
-J
i have an openfire server i've tested this with. I'll poke around a little more to see what is going on. I suspect it might be something to do with the various login methods (i know i dont have code for them all). v1.01 has just been sent to the store for approval. It doesn't address this issue. I'll fix it in 1.02
ReplyDeleteThanks. FYI - the OpenFire server version here is 3.6.4. Port 5222 is OpenFire's "standard" port which supports both encrypted and unencrypted connections. As I previously reported, I am unable to connect using it. However, today I successfully connected using the alternate 5223 port with SSL enabled.
ReplyDeleteHere are OpenFire's description of these two ports (taken from the main admin page):
Port 5222 - The standard port for clients to connect to the server. Connections may or may not be encrypted. You can update the security settings for this port.
Port 5223 - The port used for clients to connect to the server using the old SSL method. The old SSL method is not an XMPP standard method and will be deprecated in the future. You can update the security settings for this port.
---
Perhaps this info will be useful with your troubleshooting efforts...
Jay, thanks, thats really useful.
ReplyDeleteI've just installed your app but unfortunately am unable to get it to work :-(.
ReplyDeleteThis is on iPhoneOS3.0.
The server is ejabberd, using a CACert SSL certificate.
I've installed both CACert certificates on the iPhone using Safari...
The xmpp server is running on both std ports, 5222 and 5223 (old-style ssl + starttls).
I've tried the following:
user: login@jabberserver.tld / login
server jabberserver.tld
port: 5222 / 5223
ssl: on / off
And all combinations of them. None worked.
The server works fine though on my computer, using both SSL and StartTLS (5222, 5223).
I'd be glad to help debug this if you need any help :-)
Thanks for your effort !
simon I have used it with ejabberd (on jabber.org) with SSL,
ReplyDeleteusername just the part before @
domain part after @
port 5223
@Anu I've tried that too.
ReplyDeleteThe difference between jabber.org and the server I am using probably is that the former uses some official SSL certificate whereas the one I'm using is using one from CACert.
Hence I suspect the problem to be that SSL warnings/errors on connection are not ignored...like for example "self signed ssl certificate" error.
Hi.
ReplyDeleteI'm having problems connecting to a jabberd server running on Debian etch using version 1.0 of your program. I'm connecting to port 5222 with SSL off.
Hi,
ReplyDeleteI am also having problems with a work Jabber server that I can connect to using Adium when "Old style SSL" is checked. Thanks so much for this app.
My initial development was geared more towards getting google talk to work (it was my motivation for writing this). I am testing more with other jabber servers to make sure they work. Thanks for the feedback everyone.
ReplyDeleteI love that someone's trying to write an app that connects directly to IM servers without being proxied. Unfortunately I can not get this app to work. It freezes then exits within a couple of seconds of connecting to GTalk. This happens on both WiFi and 3G. I have a 3GS running 3.01.
ReplyDeleteThis seems very similar to the issue posted about by Tanuj Malhotra on the "Approved" post on this blog.
I tried it on our company Jabber server and could not get it to work. Originally it would get stuck in the "logging in" screen. I then realized that even though I switched "Use SSL" to off in the settings, the Port remained 5223. Anyway, after changing the port to 5222 I can get past the "Logging in" screen but after that, the app hangs and eventually I am booted out.
ReplyDeleteBtw, another observation is that in the Status tab of the app, the "Secure" field is turned on even though SSL is off in the settings. Is this correct?
Just as a follow up. I forgot to mention I am using the app on a Touch on our network. No VPN in use as my Touch has certs for the network. The OS is 3.0.
ReplyDeleteI am also having trouble connecting to an Openfire server. Is there any chance you can provide a guide with what information should go where. I think I got it right but want to make sure.
ReplyDeleteThe server doesn't have a offical SSL could that be the problem?
I concur that I cannot connect to Openfire 3.6.0 server using either non-SSL or SSL connections. I can see through tcpdump that it connects but the application either gives a connection error or simply closes without any error at all.
ReplyDeleteI am one of those trying to use this app with Gtalk. Having the same problem, the app freezes at the loaded contacts and exits
ReplyDeleteI was wishing some one would write this kind of app where I need not store the password on some weird 3rd party server.
Has anyone been able to get this app working with the Defense Connect Online (DCO) jabber account and servers? I tried all troubleshooting I could manage (different ports, etc) and suspect its the login type. The app hangs on trying to login. I believe DCO needs a secure login type of capability? Anyone know for certain?
ReplyDelete