New bug in BeejiveIM?

[226896]

So in the recent update to BeejiveIM, it seems that sometimes the quick chat switch bar thing (you know when you tap the top bar and you can tap on your buddy's icon to quickly switch to their chat), is completely unresponsive. As in, I can bring up the bar, but none of the buddy icons will respond to a tap. The only way to switch chats now is to click the chats tab at the bottom of the screen and select my buddy's chat from there.

Beejive don't appear to have updated their known issues page either, so I'm just wondering if this is a bug known within the community here? It's damn annoying...

 

[bbplayer5]

I cant duplicate your issue.

 

[tweeg]

I have this also, and reported it

 

[xsecretfiles]

Also, am I the only one that can't get NEW friend requests "notifications" for my yahoo messenger?

 

[nyfinest32]

So in the recent update to BeejiveIM, it seems that sometimes the quick chat switch bar thing (you know when you tap the top bar and you can tap on your buddy's icon to quickly switch to their chat), is completely unresponsive. As in, I can bring up the bar, but none of the buddy icons will respond to a tap. The only way to switch chats now is to click the chats tab at the bottom of the screen and select my buddy's chat from there.

Beejive don't appear to have updated their known issues page either, so I'm just wondering if this is a bug known within the community here? It's damn annoying...

Mine works fine. Try reinstalling the app?

 

[kyububba]

So in the recent update to BeejiveIM, it seems that sometimes the quick chat switch bar thing (you know when you tap the top bar and you can tap on your buddy's icon to quickly switch to their chat), is completely unresponsive. As in, I can bring up the bar, but none of the buddy icons will respond to a tap. The only way to switch chats now is to click the chats tab at the bottom of the screen and select my buddy's chat from there.

Beejive don't appear to have updated their known issues page either, so I'm just wondering if this is a bug known within the community here? It's damn annoying...

We have had a couple of people reporting this problem, and are looking into it.