Receiving App Link instead of BankID uri scheme from Initialize when using embedded webview

[span]

Question
How can I return the bankid:/// scheme BankID link as done in https://demo.activelogin.net when logging in through an embedded webview?

Describe the problem
When calling Initialize from Instagram embedded webview on Android and iOS (have not checked all versions), the App Link https://app.bankid.com... is received. The embedded views do not handle this link properly and cannot detect the device.

To solve this, it seems to me the bankid:/// link should be returned, as it is on the demo site. I cannot figure out how to do it, and I cannot verify the demo site source code (although I presume it is mostly similar to the samples?).

I tried investigating the device detection and I ran the unit tests on the sample header below, and it correctly identifies it as Chrome and Android. Thus the App Link is resolved. However, when sniffing the traffic in a proxy to check what link is received from demo site, I get the bankid:/// link!

This is full response:

{
  "isAutoLaunch": true,
  "deviceMightRequireUserInteractionToLaunchBankIdApp": true,
  "checkStatus": true,
  "orderRef": "<redacted>",
  "redirectUri": "bankid:///?autostarttoken=<redacted>&redirect=null",
  "qrStartState": null,
  "qrCodeAsBase64": null
}

Request headers

METHOD: POST
URL
<redacted>/Api/Initialize
HEADERS
accept:
application/json
accept-encoding:
gzip, deflate
accept-language:
en-SE,en-US;q=0.9,en;q=0.8,sv-SE;q=0.7,sv;q=0.6
connection:
keep-alive
content-length:
1702
content-type:
application/json
cookie:
<redacted>
host:
<redacted>
origin:
<redacted>
referer:
<redacted>
requestverificationtoken:
<redacted>
sec-fetch-dest:
empty
sec-fetch-mode:
cors
sec-fetch-site:
same-origin
user-agent:
Mozilla/5.0 (Linux; Android 12; IN2013 Build/RKQ1.211119.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/102.0.5005.125 Mobile Safari/537.36 Instagram 242.0.0.13.111 Android (31/12; 408dpi; 1080x2181; OnePlus; IN2013; OnePlus8; qcom; en_SE; 380288917)
x-requested-with:
com.instagram.android

What area is it related to
Device detection, BankID App Launching

Expected behavior
The bankid:/// url should be returned as it is on the demo site since that will work. But how and why when device detection identifies it as Android and Chrome :S

NuGet package version
5.0

Runtime version
.net 6

Smartphone (please complete the following information):

• Device: iPhone, iPad, OnePlus 8

Workaround(s)

1. I implemented a custom launcher that checked the x-requested-with header. If it exists, I return the bankid:/// scheme. Did not fix things for iOS.
2. Use the UA parser that is non default. Currently under testing. If this works, perhaps the default device detections can/should be replaced?

Related issues
#360
#339
https://stackoverflow.com/questions/60878744/how-to-open-an-android-app-link-from-a-webview

[span]

An update on the ua parsing.

It seems instagram on my Ipad uses the user agent of: Mozilla/5.0 (iPad; CPU OS 15_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 221.0.0.9.115 (iPad14,1; iPadOS 15_1; sv_SE; sv-SE; scale=2.00; 750x1334; 349031919). I would suspect the IPhone has something similar. That would mean the UAParserDeviceDetector and BankIdSupportedDeviceDetector both fail to recognize the browser on Ios devices in instagram browser and thus produce the "wrong" link.

Still curious on how this works on the demo site :P