JensAPedersen
I know some people in Digitaliseringsstyrelsen.
That is great. It would be amazing if you could bring the problem to their attention. The problem being that MitID is an essential service and they're locking out people who don't use Chrome or Firefox. Firefox actually didn't work in the past either, but that has changed months ago. Other Chromium-based browsers are working so far, but who knows if that's deliberate or by accident. There's no good reason for why they're locking out Vanadium, but they're doing it anyway.
I've wrote to MitID support many many times. Sometimes I got answers saying "a future version may fix it" from their support and sometimes I get no answers. (In this case it doesn't even make sense since the problem isn't with the Android app, but the way their web form works.) I wasn't able to get a direct line of communication with the developers, nor I know if any of my messages were actually brought to their attention. It's all very opaque.
I think it is the implementation of MitID in MobilePay that is the problem.
Unless I missed something, it looks like the problem with MobilePay is actually entirely due to MitID, not really related to MobilePay. You can reproduce it by simply trying to login to mitid.dk
with Vanadium. What is going to happen:
- login form shows up
- you press the button to authenticate
- the button launches the MitID app, and you can authenticate there
- however, when control gets back to Vanadium you'll notice that the login form closed itself, and the post-authentication flow that actually logs you in doesn't happen
The same will happen with any app that opens an in-app browser (which will use the default browser). I can replicate that with my bank app, for example. If you switch to Chrome (or a Chromium-based browser), or Firefox, it works because in step 4 the form didn't close, and then it redirects to the URL that actually logs you in.
The problem is that the login form in mitid.dk
(or one of the subdomains which is used by third parties) is programmed in such a way that it doesn't like Vanadium, and then the moment you press the button to launch the MitID app then the form just closes itself instead of staying open and waiting for the outcome of the authentication. As it is closed, when the app is done authenticating and you get back to where you were, nothing happens and you're just stuck.