Phlo23

I did some tests and noticed something similar. There's no sound for certain pre/postflop actions with bluetooth or wired headphones. With the phone speaker it seems ok, but the sample in this case is approx. 4 min.

Tested on Samsung S7, android 8. 

Bluetooth: missing sounds pre - dana622 + bankomata, on flop boss0072

wired headphones: missing sounds pre - biriklovn

wired headphones: missing sounds on flop - biriklovn

1 hour ago, Livertool said:

Never mind fixing the ticket part, works again 🙂

I think it has something to do with ratholing. In this example I left the table with 50bb+ and tried to come back immediately selecting 50bb. It gave me the "insufficient funds" message.

So, if you return to the table with a smaller amount than the one you left with, you'll receive the message "insufficient funds", if you select a larger or equal amount, everything's ok.

In conclusion, there's a problem with the message. Instead of "insufficient funds" it should show an explicit warning.

It probably works ok now because the cooling off period has passed.

19 minutes ago, Livertool said:

Ok, in that case it didn't do much as i always have had option of autofilling username even if you removed it in your end. What it didn't do anymore was autofilling pw too.

Same here. A few days ago, only the user field was completed with the autofill, the password had to be entered manually.

1 hour ago, Livertool said:

@Phlo23 could you try to time actions like this: tap "you are logged out" immediately when possible, go straight to square to minimize window, when it is minimized wait until window turns from black to white and loading image appears, swipe to close window and open app again. Thou it don't seem to always keep you logged in, following mentioned timing kept me logged in about 4 times of 5.

Yes, I tried this as soon as I saw that it works ok if you wait for the logout screen, but didn't manage to replicate it. There may be different outcomes depending on the OS and phone. On android 8 when the app is minimized you don't have a live preview. 

Hi @EatMoreNaga, the minimum stack for sensei is 50bb. If there's no such stack in the player pool, the status it's not activated.

It seems that it's not the minimization of the app itself and its reopening that generates the bug, but what happens when you do the respective action. More precisely, when you minimize the app, a short disconnection occurs. I run some tests with several disconnections without exiting the app and each time after reconnecting the bug appeared.

It should work now

I played banzai for 45 minutes and the screen froze suddenly, I had 2 tables and I wasn't using another app or any pop-up function.
I tried to force a disconnection by putting the app in the background (this method works for a similar bug where the screen freezes, but in this case it's not effective).
Exactly as @Livertool said above, after the screen froze the only solution was to completely close the app and reopen it.

DATE ISSUE OCCURRED : aprox. 00:26 EEST, 17.04.2024 

STEPS TO REPRODUCE: At this moment I don't know the steps to reproduce the bug.

CLIENT(S) IMPACTED: Android app ver. 3.35

ABOUT DEVICE: Android 8, Samsung Experience version 9.

Managed to reproduce the bug with fast scrolling just like @Rushbie said

@shipallin Can you also upload a screenshot with display tab, please? 

Thanks 😊

i'd love to help you @Dubnjoy000, but I only moved the info above from another post. The OP was @orbit_white, maybe he can answer your question 😊

Can you provide more details?

• What kind of keyboard do you use? (Android keyboard, Gboard, others)
• Have you tried testing this on other devices?

I didn't manage to reproduce the bug, but after I receive more info I'll try again 🙂

Another attempt after 1 hour. 8 tables, same scenario. 
Tables seemed to open, froze, turned white and then the app crashed. 3-4 attmpts to reopen,  as soon as the tables appeared on the screen, they froze, turned white + crash. When there were 3-4 tables left, the app stopped crashing.

When did it happen: 16/03/2024 around 10:00 AM UTC
On what client did it happen: Windows client, dmp + logs ver. 3.34.17
Internet connection when issue occured: mobile hotspot

2 dmps( first crash + 1 attempt to reopen) + logs

Another attempt after 3 hours. This time I tried to open 12 tables. The same thing happened, the tables seemed to open, froze, turned white and then the app crashed. I tried to quickly reopen the app several times, same story. As soon as the tables appeared on the screen, they froze, turned white + crash.

When did it happen: 16/03/2024 around 9:00 AM UTC
On what client did it happen: Windows client, dmp + logs ver. 3.34.17
Internet connection when issue occured: mobile hotspot

2 dmps( first crash + 1 attempt to reopen) + logs

Managed to reproduce it.

When did it happen: 19/03/2024 around 16:21 UTC

On what client did it happen: Android client 

Internet connection when issue occurred: cellular network

Samsung S7, Android 8.0.0, Samsung Experience version 9.0. build number : R16NW.G930FXXU8EVG3

"Exact same issue in the production client with wired internet. It's been happening for a while, got used to restarting the client 10 times per day by now 😅"

credit to @FeelsBadMan