channel windows not being shown when using ZNC bnc on ZTE Blade device

[commander-keen]

When using a znc bouncer YAAIC does not show any channels on my Orange San Francisco mobile phone (aka. ZTE Blade internationally), just the status-window and optionally the window informing about new messages will show up. There's no difference between channels which are already handled by the bnc and new ones I try to enter via YAAIC after connecting. I end up being in the channels, I get the welcome message in the status window and I can even part them by /part #channelname. When connecting to the network (Quakenet) without BNC the channels show up fine.

I verified with two Phones of the same kind. I tested by deleting all data of YAAIC in the application management of Android and reentering everything from scratch.

A friend of mine (providing the znc for me) can use YAAIC on his SonyEricsson x10mini pro Phone (ndroid 2.2) with znc just fine. (both using v0.9 of YAAIC) I can use that znc with the AndChat irc client for android without experiencing this issue.

My Phone is runnung CyanogenMod7.1.x (Android 2.3.5), znc is being used with SSL enabled.

[pocmo]

Oh, commander keen. I loved the game :)

Back on topic: That's a hell of a bug. So you both use the same znc server but different phones and it does only work for one phone? Maybe it's a timing problem.

[commander-keen]

hehe, yes, that was a great game. :-)

You are correct, it's the same server and each of us has an own user-account, according to him. We have different phones and slightly different android-versions (2.3.5 vs. 2.2 as noted above), I don't know which of those facts is more important, I'm not a professional in these things. ;-)

[lstarnes1024]

I can also confirm that this issue also occurs on my Galaxy Nexus. ZNC joins the channels when it starts but Yaaic fails to see the channels when it connects to the bouncer. Using /join also does not make Yaaic see the channel.

Interestingly, Yaaic does add a new channel when the client is forcejoined by an oper using /sajoin.

[thor]

I'm experiencing a similar thing; but only with one network, freenode. At first one channel appeared, but no other (on a list of 10).

This doesn't happen on any of my other three networks. A: 4.0.4, Yaaic: v1.0

[pocmo]

I tried to get this error yesterday again:

• Yaaic 1.0
• Android 4 Emulator
• Running ZNC 1.0-alpha1 (via fedora's yum) on my local machine
• Connected to Epd-Me (irc.epd-me.net) and Freenode (irc.freenode.net)

It always joined the channels. Hmmmmm.

[llawwehttam]

I'm getting the same problem here on freenode but without using ZNC.

Running CM7 on a ZTE blade if that makes a difference.

It's a shame because yaaic looks like the best irc client I've come across but this makes it unusable for me.

[pocmo]

@llawwehttam: Without using ZNC? Any other bouncer? Is it possible to log the IRC traffic? (Maybe I should add a debug option to log the traffic to the verbose log)

[urbels]

I`m using znc and never seen smth like this but i saw smth similar. New irc tab appears i can see it but cant swype to it, then turn device vertically and i can, after turn back horizontally and can access too.

[llawwehttam]

I should have made that clear, when I said without ZNC I meant without a bouncer at all. I haven't been able to log any traffic through yaaic. From another client I can see the following:

14:07:38 --> | LIpsum-Droid (~LIps@unaffiliated/lipsum) has joined #archlinux-offtopic 14:08:00 <-- | Lpsum-Droid (~LIps@unaffiliated/lipsum) has quit (Client Quit)

I can leave the channel from yaaic by running /close #channelname or by closing yaaic.

EDIT: I've tried the above idea of changing the screen orientation but it made no difference, but in my case I don't see the channel window at all.

[pocmo]

I added a debug setting to the development version of Yaaic. If it is enabled Yaaic will write all IRC traffic to the device's (verbose) log. We can use these logs to simulate these bugs (unit tests) and fix them.

[llawwehttam]

I've never done any android dev before. I've set up eclipse and installed the sdk tools etc... What API should I be using. I want to test on my phone running 2.3.7 but if I try the 2.3 android I get errors from Sherlock asking for android-15.

EDIT: Never mind. I've come across so many problems with Eclipse (juno) I'm going to spend some time getting a working dev environment working before trying to test.

[pocmo]

There are two answers describing how to import the Yaaic project: http://stackoverflow.com/questions/11181403/importing-a-clone-from-github-into-eclipse-and-build-path-errors

[jantman]

For everyone else seeing this, are you running the Away_Nick module in ZNC? I believe this is really a bug in YAAIC not being able to deal with an IRC server (or in this case bouncer) that thinks your nick is different from what YAAIC is configured with (i.e. when you reconnect to ZNC and your nick is nick_away or nick_offline).

[thor]

I do not use away_nick, no. However, I never configure ny nick in YAAIC to match with my nick on the mentioned network I'm bouncing to.... Which could support your thesis. Den 28. aug. 2013 00:50 skrev "Jason Antman" notifications@github.com følgende:

For everyone else seeing this, are you running the Away_Nick module in ZNC? I believe this is really a bug in YAAIC not being able to deal with an IRC server (or in this case bouncer) that thinks your nick is different from what YAAIC is configured with (i.e. when you reconnect to ZNC and your nick is nick_away or nick_offline).

— Reply to this email directly or view it on GitHubhttps://github.com/pocmo/Yaaic/issues/91#issuecomment-23377709 .

[Niluge-KiWi]

I confirm the bug in yaaic: I use znc to connect to efnet, and with yaaic I only get the server view and the /znc command correcly opens a new view, but not the channels znc is connected to.

Efnet truncate the nickname to 9 characters, whereas I configured mu full nickname with more than 9 characters in yaaic. When configuring in yaaic the real nickname (truncated to 9 chars), then everything work great!

So the workaround works, and the bug is confirmed.