Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 1223031]
Blink>Identity>DigitalCredentials
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Blink
Blink>Identity
[ID: 1253656]
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Estimated effort
Description
I am experiencing inconsistent results—sometimes the deep link works as expected, while at other times, I receive the error: "No app deep linking permission found" (screenshot attached).
Could you please help me identify the possible cause of this inconsistency? Is there any specific configuration or setting that might be affecting this behavior?
I am concerned that this could indicate a security issue or a misconfiguration in my app. For reference, here is the asset links
file:
Additionally, I am attaching a video recording (MOI_GoogleDigitalLinks_REC.mp4) demonstrating the issue, as it still persists and remains inconsistent. Further Observations: The issue occurs across different browsers.
I have tested using a VPN to rule out any country-level web link restrictions, but the inconsistency remains.
At times, manually enabling supported web addresses triggers the functionality, but this is not a viable solution for end users (screenshot attached).
I am uncertain whether this issue is due to security measures applied or if it's related to caching issues on Google's servers.