Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(IT Wallet): [SIW-1961] Handle invalid payload in deeplink for Remote presentation #6724

Merged
merged 49 commits into from
Feb 20, 2025

Conversation

RiccardoMolinari95
Copy link
Collaborator

@RiccardoMolinari95 RiccardoMolinari95 commented Feb 17, 2025

Short description

This PR handles the view for an invalid payload in the deeplink during the remote presentation flow

Warning

This PR depends on #6689

List of changes proposed in this pull request

  • Added a new Screen ItwRemoteDeepLinkFailureScreen
  • Added a new file, ItwFailureTypes.ts, specifically to manage errors for the support bottom sheet, outside the state machine flows. This type of error is intended to be global for ITWallet, and the flow to which it belongs must be specified in the code
  • Created the ZendeskSubcategoryValue enum in useItwFailureSupportModal, representing possible Zendesk subcategory values for opening a support ticket. This is passed as a prop when using useItwFailureSupportModal

How to test

To test the changes, use an invalid deeplink (e.g., https://continua.io.pagopa.it/itw/auth?client_id=abc123x) and verify that the support bottom sheet appears.

Note

I don't have the possibility to use deeplinks during development. I use the same deeplink flow but by scanning the QR code instead

Screen.Recording.2025-02-20.at.10.17.25.mov

RiccardoMolinari95 and others added 30 commits January 31, 2025 15:11
Copy link
Contributor

@mastro993 mastro993 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants