E2E: Multichain workflow in smoke pipeline is a bit unstable

[cortisiko]

What is this about?

The multichain workflows for iOS and Android have become unstable recently. One of the main culprits is the existence of the toast notification. Sometimes, the toast notification blocks a particular UI the test cannot interact with, resulting in failures. Depending on the time of day bitrise might play nice and the toast disappears in a timely fashion. This is not ideal, as it could lead to false positives. We should modify the tests better to handle the appearance of the toast(s).

Here is a video recording showcasing the behavior of the toast.
https://github.com/user-attachments/assets/1d03a5f4-8f49-4223-9871-a70ad6b534ec

Scenario

No response

Design

No response

Technical Details

The two problematic tests are these it blocks:

• allows simultaneous granting and revoking of multiple chain permissions
• should add network permission when requested

Keep in mind they are flakey, specifically on Android and not iOS.

Threat Modeling Framework

No response

Acceptance Criteria

The Multchain workflow should pass consistently. Be sure to run the workflow at least 3 times to confirm it is fixed. Use the multichain_permissions_e2e_pipeline to confirm the multichain tests are running as expected instead of running smoke.

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