-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Stabilize deep linking on the simulator/emulator for E2E #5536
Comments
Update: This happens to me on my Physical Android device on MM version 5.12.1, downloaded from the store |
The PR created #5543, doesn't solve this particular issue of universal links, I will move this issue to the backlog until we have enough resources to move forward
|
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions. |
@andreahaku do you remember why this PR was closed? Did it not address the issue? |
I did not close it. I thinks it's been closed for inactivity. There is still no solution to it unfortunately. |
## **Description** Deeplinks were skipped when branch io subscription contains an error but that shouldn't prevent handling the current link. Instead we log the error and continue to process the deeplink which is especially important for SDK connection which would otherwise be ignored. ## **Related issues** Fixes: #5536 ## **Manual testing steps** On IOS you would normally have to build the app twice to process deeplinks with branch io. 1. Retrieve universal link while building the app only once on Ios 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've clearly explained what problem this PR is solving and how it is solved. - [x] I've linked related issues - [x] I've included manual testing steps - [x] I've included screenshots/recordings if applicable - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. - [x] I’ve properly set the pull request status: - [x] In case it's not yet "ready for review", I've set it to "draft". - [x] In case it's "ready for review", I've changed it from "draft" to "non-draft". ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
I am experiencing an issue when trying to deep link on the simulator. I can successfully deep link to a dapp or to a particular transaction the first couple of times. Afterward, it is impossible to actually deep link.
For example, I would attempt to deep link here: https://metamask.app.link/dapp/metamask.github.io/test-dapp/
the app launches but I am not taken to the mm test dapp in the browser view. See the recording here.
This is breaking the e2e deep linking tests. I can confirm that this DOES NOT happen on physical devices
See my original slack message here: https://consensys.slack.com/archives/C02U025CVU4/p1671222774797949
To reproduce on your simulator/emulator:
Just an FYI: Wiping the device each time works but this does not make sense for E2E testing.
The text was updated successfully, but these errors were encountered: