Could a loading state of the app causing the Universal Linking (deeplinking), to fail??

• We have a web URL: https://www.myapp.com/profile and a matching AASA route: {"/": "/profile", "comment": "Matches any URL whose path is exactly /profile" },.
• On my device, i have this link in my Notes app so when I press the link, it correctly opens the mobile app.
  • But the app stays on the home screen and doesn’t open the stack/screen.
• However, if I run npx uri-scheme open myapp://profile --ios the app correctly opens the scheme based route & navigates to the correct stack/screen
• Our site does show up on the validator and we know the routes work on our legacy app so it is correctly serving content already.
• In Development, If I try to run npx uri-scheme open https://myapp.com/profile --ios it just opens on the website, not the app.

How else can I try to debug why the https:// route itself isn’t opening to the route, but opens the app – while the scheme based route does work? We do have a loading state when the app opens, to check user auth session & load data, but I would think if this is an issue, then the same thing would happen if opening the scheme myapp:// directly also (which it does not).