Jump to content

Phlo23

Group: Flush
  • Posts

    101
  • Joined

  • Last visited

Everything posted by Phlo23

  1. 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 bluetooth - pre_post.mp4 wired headphones: missing sounds pre - biriklovn wired - pre.mp4 wired headphones: missing sounds on flop - biriklovn wired - postflop.mp4
  2. 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. Texas_Holdem_-_NL4_cg3c883a_FPS__23.97Dr__6_2024-05-03_20-42-37_-_Trim.mp4 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. Videoclip_fara_titlu_-_Realizat_cu_Clipchamp_1.mp4 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.
  3. Same here. A few days ago, only the user field was completed with the autofill, the password had to be entered manually.
  4. 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.
  5. Joint report with @FeelsBadMan After a few tests, we noticed the following: The amount for the top up option isn't displayed correctly. More precisely, it's not updated since the last similar action. In order to correctly update the info, the banzai table must be resized. Even if this bug appears, the correct amount is added to the player's stack. @FeelsBadMan's simple and concise conclusion: "it's just lacking a trigger to refresh with the correct data and wait till something does eventually trigger it" Added some clips with the bug and the steps described below. teest.mp4 stuck amount.mp4 Banzai_Texas_-_NL1_cg3a9e42_2024-04-24_10-08-12.mp4
  6. 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.
  7. 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. 2nd bug.mp4
  8. I had one banzai table and suddenly the +1 option disappeared for a few moments. I went through the apps main menu for a few seconds and when I returned to the table it reappeared. It's the 2nd time I notice this, the 1st time it lasted approx. 2 min until the option reappeared and i didn't leave the table. In addition to the public screenshots, I've attached a clip where you can see the bug and a picture with details about the OS version.
  9. Phlo23

    Login error

    It should work now
  10. 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.
  11. Managed to reproduce the bug with fast scrolling just like @Rushbie said
  12. @shipallin Can you also upload a screenshot with display tab, please? Thanks 😊
  13. 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 😊
  14. 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 🙂
  15. 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
  16. 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
  17. I tried to open 16 tables. 12 tables were opened and after a few seconds they froze. They started turning white one by one and the app suddenly closed. After that, I tried to quickly reopen the app 2-3 times, each time the tables seemed to open, froze + crash. On the 4th attempt I had 3 tables, only then did the app stop crashing. Internet connection when issue occured: mobile hotspot I uploaded 3 dmps( first crash + 2 attempts to reopen) + logs
  18. I tried to open 7-8 hexa tables, 7 opened and I was able to play, only one was frozen (see the image below). I couldn't click on anything in that window, but I could hear a sound from the chips moving. I tried later to identify the game in HH. I found a possible hand from that game, but since it was a large volume in a short period of time, I can't be 100% sure. I recommend checking the logs. Internet connection when issue occured: mobile hotspot
  19. 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
  20. When clicking on the logout button on the mobile app I get you are logged out and then I get this error page, could be related to the white screen after timeout bug. IDK if it matters but the error gives a different version than that of my client. Internet connection when issue occurred: Wifi credit to @FeelsBadMan
  21. "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
  22. After timeout, instead of being redirected to the login window, you get a white screen. You can't click on anything, you have to close and reopen the app. Internet connection when issue occured: mobile hotspot Expected result: redirect to login window Actual result: white screen
  23. I have enabled biometric login in the app settings, and it's working in literally all other apps, but for whatever reason it just wont work for Unibet poker. I never get the option to sign in with my finger. credit to OP
  24. In the login interface on MacOS, when attempting to correct a mistyped username or password by using the Backspace key, the system erroneously registers the keypress twice, resulting in the deletion of two characters instead of one. This issue is also observable with other keys like the Tab key. However, the Space key functions as expected, deleting only one space per keypress. **Expected Result:** Each keypress (Backspace, Tab, etc.) should register as a single action. **Actual Result:** Backspace and Tab keys are registering as if pressed twice, thereby performing double the action for a single keypress. **Additional Info:** - The issue was not reproducible using the Space key, which functions correctly. credit to @orbit_white
×
×
  • Create New...