Stubbe-Unibet

Both MitID and BankID login has been fixed. There're still some improvements to be made, which will hopefully be part of next release. Marking as fixed, as it's more about improving it now.

EDIT: MitID Android is still a bit bugged, as it requires an app update as well. Will be part of the next release.

The fix will be released later today, so marking as fixed

Our QA have tried to reproduce the issue, but unfortunately no luck so far 😞

Current plan is to start working on it after:

MitID and BankID login broken on Android app - Bug Reports - Unibet Community (90% complete)

Android app with grey/black screen after login - Bug Reports - Unibet Community

Fingerprint login not working on Android - Bug Reports - Unibet Community

Reason the above get priority is that impact is bigger overall, and for the 2nd one it's a bug that can be reproduced 100% of the time, so will likely be fixed much faster. For 3rd one, we've already done a fair bit of work and should be close to the finish line.

Thanks for the report, @punterfifth9! Unfortunately not possible to do anything with crashes, unless:

1. It's a consistent issue that can be reliably reproduced (not the case here)

2. We've got the dmp file from the crash. "If you are experiencing crashes on Windows, please use this special client version which will generate a file with crash details (.dmp file)
Download special Windows client build for crash issues."

Note that above link is for current client version and after next release there'll be a different one.

Was fixed together with the idle timeout issue. Thanks for the report!

The issue has now been fixed. Thanks for the report!

Due to the MitID and BankID issues, this one has not seen any progress. I'm hopeful we can pick it up end of next week, when MitID and BankID fixes have hopefully been released (and proved to be working on production).

We've started development on this one and a fix has been tested on the test environment. I hope we'll manage to release it next week, but I'll need to sync with the teams on Monday.

Good progress on both MitID and BankID Android login. Hope to have the fixes released early next week.

Thanks for submitting the bug report here as well! I've been looking into it for a while, and we've finally identified the issue.

Unfortunately, there're multiple teams involved and it might take a while before a proper fix is in place. I'm investigating whether there's a potential temporary workaround for the issue.

It might seem very odd, but it is actually rather common that hand strength isn't considered in these cases.

That of course doesn't mean it's perfect, and I tend to agree it'd be more logical or cause less confusion, if secondary finishing positions were decided based on hand strength rather than at random. 

This is from the tournament description of your tournament: "Secondary finishing positions are decided at random and not by hand strength or seat".

As it's by design, it's not a bug, but it is something I'm considering putting on the backlog eventually anyway, as an improvement.

@Greg8 thanks for the report! Can you confirm if it works, when you switch to your local language instead of English? 

Marking this as solved, as it's technically more of an incident than a bug. 

The tournament pause is a feature and worked as expected. More info here: 

Thanks for the report! I couldn't reproduce this one, so I've set status to awaiting feedback. Please do let me know, if you manage to reproduce it/experience it again! 

I actually had this one during our recent staff tournaments, also on Android. Was busy with other stuff on the laptop at the same time, so didn't notice when it break or have any clue about what might have caused it. Please keep an eye on this one and report any further instances! If we can figure out how to reproduce it, we've come far 🙂

EDIT: I should add that when I had the issue, I'm almost certain no gifs were shown at all; not for other players either. It could of course be no one else used gifs at the table for about an hour, but that's highly unlikely, as they were frequently used in the staff event. So possibly a slightly different issue to yours.

Thanks for the update @Livertool! I'll close it for now, but if it becomes a thing again/it tends to break more often, when not on latest version, please update here.

Thanks for the detailed report and screen recording! It's the same issue reported here: 

So "fix" for now is to not use autofill. Hope to have this one looked at after Easter.

@Livertool, see the questions above. Especially the keyboard used is key here. In the past, we've had some issues with for instance just the default Samsung keyboard.