What is this about?

When the user opens a signed deeplink and the app cannot resolve the path, we assume:

• Whoever have signed the deeplink knew what they are doing
  so
• A version of the app exists that can handle this deeplink
  so
• The deeplink is not incorrect, but rather the app is outdated

Solution:
When a signed deeplink is clicked and cannot be resolved, redirect the user to a new 404 screen (similar design)

Header
Instead of:

This page does not exist

Will be:

This page is not supported in current version

Body
Instead of:

We can't find the page you are looking for

Will be:

Update to the latest version to use this feature

Scenario

No response

Design

No response

Technical Details

• Design and implement the minimum version check feature within the app.
• Test the feature to ensure it works as expected.

Threat Modeling Framework

No response

Acceptance Criteria

• The app checks if the deeplink is signed
• Users with older app versions are explicitly asked to upgrade when accessing unresolved signed deeplinks.
• Deeplinks function as expected for users with compatible app versions.

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response