Jump to content

Phlo23

Group: Flush
  • Posts

    90
  • Joined

  • Last visited

About Phlo23

Recent Profile Visitors

251 profile views

Phlo23's Achievements

Rank 14

Rank 14 (13/40)

  • Great Content
  • First topic
  • One Year Anniversary
  • First Reply

Recent Badges

31

Reputation

  1. @shipallin Can you also upload a screenshot with display tab, please? Thanks 😊
  2. 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 😊
  3. 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 🙂
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. "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
  11. 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
  12. 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
  13. 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...