Unable to open deeplink on Pico Neo 3 and Oculus Quest 2

[zgk-vdg]

Configuration

Firefox Reality version: 12.2
Firefox Reality build ID: 5f700c8

Hardware: Pico Neo 3 Pro and Oculus Quest 2

Steps to Reproduce

1. Register Android app (ours) to handle custom scheme (i.e.: vrapp://loginresult?....)
2. Open FxR from within the app
3. Redirect user (via window.location or clickable link) to our App, using deeplink.

Current Behavior

The browser doesn't open our App.

Expected Behavior

Our App should open.

Context

Our app is made with Unity, we followed the documentation and double-checked the Android manifest included, you can find it below.
Following a detailed investigation we found that by running from a shell:

adb shell am start -a android.intent.action.VIEW -d "vrapp://loginresult?%7B%22token%22%3A%22dqn6cvtkjp3clb1k3rfg39sd1b%22%2C%22user_id%22%3A%221%22%2C%22fullname%22%3A%22Zgk%22%7D" com.dtales.vrapp

our application is launched as expected.

For reference here's the manifest.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.dtales.vrapp" xmlns:tools="http://schemas.android.com/tools" android:installLocation="preferExternal" android:versionName="1.0" android:versionCode="1">
  <supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true" android:anyDensity="true" />
  <application tools:replace="android:theme" android:theme="@style/UnityThemeSelector" android:icon="@drawable/app_icon" android:label="@string/app_name">
    <activity android:name="com.unity3d.player.UnityPlayerActivity" android:label="@string/app_name" android:exported="true">
      <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
      <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="vrapp" android:host="loginresult" />
      </intent-filter>
    </activity>
  </application>
</manifest>

Is this a bug or a known limitation of the browser?

We're relying on the deeplink capability to implement a SSO flow: it would require a much bigger effort to find another way around the issue.

Best regards

Error Logs and Stack Traces