search

indrora / Atomic

Atomic: an IRC client from the ashes of yaaic
https://indrora.github.io/Atomic/
GNU General Public License v3.0
123 stars 29 forks source link

Client will only connect to the same server once. (with bip proxy) #4

Closed ghost closed 10 years ago

ghost commented 10 years ago

I'm attempting to use this client to connect to the same server several times. It's BIP proxy that I've used for years and with many other clients.

It will only connect to the first server in the list that is the same as the others. (I tested and attempted to connect to a subsequent server after a reboot, but it failed as expected.) Connecting to the first server works normally.

I am using:

I turned on debugging and attempted to glean something though logcat, but nothing of relevance appeared.

I will be happy to test any pre-release versions but I currently don't have a build system setup to test the current trunk.

I'd like to take this opportunity to thank you for taking the time to fork yaaic and 'scratch your itch,' as it fulfilled the same expectations I've had for a mobile IRC client (current bug notwithstanding). I'd also like to thank you for supplying APK files on F-Droid and on github, making it easier for users like myself who don't use google services on their android devices.

indrora commented 10 years ago

How are you adding the server multiple times? I regularly add my znc bouncer several (4...5) times. The only requirement is they are unique in display name.

ghost commented 10 years ago

I've triple-checked passwords and hostnames, and I have tested connecting to an unrelated server. For example, oftc.net worked.

cap201404221053

cap201404221044 cap201404221045 cap2014042210251 cap201404221023 cap201404221024 cap201404221025

indrora commented 10 years ago

I'm not able to reproduce this on ZNC with 2 servers (I use the ident authentication mechanism for ZNC however)

Turn on "Log IRC Traffic" under Settings > Misc and check logcat. All IRC traffic will be logged. Later versions will have a better reason for "couldn't connect" (read: the next one).

indrora commented 10 years ago

Until I can get some reasonable debugging, I'm closing this ticket.