Stubbe-Unibet

We've got a fix in the upcoming release, which might fix this one. I can't say for sure, due to the limited info, but there's also no value in keeping the report open with current details

Correct, it's just how the promo is designed. So even though I agree it could be considered a bug, I'll close this one, as it's by design.

Added to backlog as it should be, as you point out, a simple fix

Closing this one as I'd consider it more of a feature than a bug, until we have the proper table resizing released 😄 

MitID iOS issue likely identified and I'll try and get the fix live early next week

Tough case, but you managed to crack it 🙂 Thanks guys!

I'll get it added to the backlog, as a low priority item, given the small impact. For now, it'd just be to figure out the complexity of fixing it. 

I looked into it now, and it seems the password field was at some point changed to "new-password" field type, which is why it wasn't being populated automatically, when for instance using the Google autofill. If this happens again - that password isn't autofilled - please do let me know, as that would be a bug 🙂 

I'll test this one tomorrow if I can find the time. Never actually tried to play with audio through bluetooth on the Android app

As it's intentional design, I don't think it can be considered a bug, but it's good to have it reported anyway! There's a reason I haven't closed it yet, as I want it to be looked into again, to see if it's something that could possibly be easily improved. Especially now that there's a dedicated logout confirmation screen on the website (I believe that was part of the reason behind the current design; that we didn't have such confirmation on the website so it was built into the client instead), the current design is far from optimal - and you could argue it's a bug 🙂 

Do keep on reporting! Rather a few reports too many than too few! And if we end up improving this, I will send you some BP 😉 

Then we agree. It’s been a few years since I looked into this one, so don’t remember the details, but there was a reason for this design (if it was a good one, I don’t remember)

Now I watched the video again, and as said above, you’re not logged out before tapping the green tick. I saw you did that the first time I watched the video, but I didn’t notice the delay in loading the login page (or rather logout confirmation page now). This normally happens quite fast, but with a slow connection it can take a few seconds. I don’t believe the page needs to fully load (didn’t use to be the case at least), but I haven’t really tested with that new page. 

So it’s not even a bug as such, but just how the logout flow is currently designed (and it’s not perfect, I agree). You’re then supposed to be logged out when reopening app, but probably something with the url parameters messing that up (should have been fixed when the logout page issue was, but maybe your local domain was missed). Just on phone now so will look into it next week 

Does look like the beers played a part here 😄 notifications triggered due to Sensei state or black belt from what I can see

Then there’s the issue with the way these are set up as daily missions (what @FeelsBadMan) pointed out above, but it’s not a bug a such, so closing this one 

@Livertool does this happen every single time for you? Likely differences between domains/countries. If you have it consistently, I'll try and replicate your situation

@Livertool what screen do you see, if you just click the green tick and keep the app open? Will it not load that new "you have been logged out" screen? Perhaps the case that it isn't enabled for your domain yet. And if you don't time it perfectly, are you still logged in?

I need to have a closer look at this, but the autofill was never meant to be removed to my knowledge, as it's not really something we control but up to you, what you store in your browser. What was removed was the remembering of username, as that was stored locally