Since #7861 all the sessions of the Maestro account are ended after each run,
so the device under test is always the last session. In this case the title of
the sign out screen does not contain "Remove this device" anymore, and tapping
on the second occurrence of this text fails. Tap on the submit button using its
test tag instead.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Fix#7181: Remove back arrow from device verified screen and use 'Done' text
* Update screenshots
* Fix failing Maestro test by tapping 'Done' instead of 'Continue'
---------
Co-authored-by: ElementBot <android@element.io>
Co-authored-by: thirumani-vihaan <your-github-email@example.com>
* Try fixing DM creation in Maestro
* Also handle 'invite new people to this room' with first invite to aRoomName
* Try adding a room list clean up sub-flow
* No need to press back button after successful invites
* Looks like 'hideKeyboard' works as 'back' and messes up with the navigation. Try using the workaround described in https://docs.maestro.dev/reference/commands-available/hidekeyboard#workarounds
* Fix Maestro: tap on confirmation for inviting unknown users to a room
* Tap on back after inviting some user
* Tap on back again
* Confirm inviting someone to a DM
* Make fix conditional
* Fix the `assertSessionVerificationDisplayed.yaml` check
* Previous 'Location' is now 'Share location'
* We don't have a GPS location, so the text is 'Share selected location'
* 'Create a new conversation' is now 'Create room'
* Try adding a background logcat process
* 'Sign out' is now 'Remove this device'
* Adjust the logcat filtering so it silences everything that's not our app, otherwise the logs can get quite large
* Increase the timeout for asserting 'Be in your element' is visible
* Disable the chrome onboarding flow. This simplifies the code a lot and helps avoid corner cases.
* More delays with timeout!
* Add more info to the summary, specially when the tests fail, so we can quickly check what failed.
* Make sure Maestro tests can't run in parallel, but APK builds can
* Try fixing Maestro tests again: they fail when creating a room because the texts have changed
* Try using a retry on the webview before the login so we skip Chrome's setup
* Try handling edge case when leaving a room does not remove the screen
* Ensure the CI is marked as failed when Maestro test is failing
* Fix typo in String to disable bookmark in ChromeCustomTab
* Fix Maestro test now that matrix.org is using MAS to authenticate.
* Fix Maestro test - other issues due to recent changes.
* Maestro: add test on Element Call
* Run through Chrome on boarding step.
* Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361
* Revert "Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361"
This reverts commit d400644622c1a240deb61040f9095e3221e07f21.
* Add comment on Maestro flow.
Add Maestro local CI workflow:
- Remove previous Maestro Cloud.
- Use an emulator with Pixel 7 Pro - API 35.
- Allow to record several videos in the background to verify the run.
- Upload test results.
- Allow either dispatching a new flow, running the 'build apk' job or run with a PR after the 'Build APK' flow has succeeded.
* Add QR code login.
* Add FF to disable it in release mode.
* Force portrait orientation on the login flow.
* Create `NumberedList` UI components.
* Improve camera permission dialog.
* Make nodes in qrcode feature use `QrCodeLoginScope` instead of `AppScope`
* Bump SDK version.
* Fix maestro tests
---------
Co-authored-by: Benoit Marty <benoit@matrix.org>
Co-authored-by: ElementBot <benoitm+elementbot@element.io>
* Add plain text editor based on markdown input
- Fix autofocus of message composer.
- Remove `Message` data class, fetch the details in `MessagesPresenter` instead.
- Remove `enable rich text` option from advanced settings, set it as a build configuration instead.
* Fix MentionSpanProvider
* Bump RTE library to released `v2.37.3`
---------
Co-authored-by: ElementBot <benoitm+elementbot@element.io>
* Improve enter recovery key screen UI
* Add instructions to reset the encryption of the logged in account.
* Update screenshots
* Fix maestro flow
---------
Co-authored-by: ElementBot <benoitm+elementbot@element.io>
* Add `SessionData.needsVerification`:
- Allows us to add a skip button for debug builds.
- We can have the verification state almost instantly.
- It doesn't depend on network availability to know the verification state and display the UI.
* Add DB migration.
- Make the skip button in the verification flow skip the whole flow including the completed screen.
- Save the session as verified in `RustEncryptionService.recover(recoveryKey)`.
* Enforce session verification for existing users too.
* Fix verification confirmed screen subtitle (typo in id, was using the wrong string)
* Update screenshots
---------
Co-authored-by: ElementBot <benoitm+elementbot@element.io>
* Move session verification to the FTUE
* Allow session verification flow to be restarted
* Use `EncryptionService` to display session verification faster
* Remove session verification item from settings
* Remove session verification banner from room list
* Remove 'verification needed' variant from the `TimelineEncryptedHistoryBanner`
* Improve verification flow UI and UX
* Remove 'verification successful' snackbar message
* Only register push provider after the session has been verified
* Hide room list while the session hasn't been verified
* Prevent deep links from changing the navigation if the session isn't verified
* Update screenshots
* Renamed `FtueState` to `FtueService`, created an actual `FtueState`.
---------
Co-authored-by: ElementBot <benoitm+elementbot@element.io>
Benoit Marty
Jenna Vassar
Thirumani Vihaan
Jorge Martin Espinosa
Andy Balaam
Benoit Marty
ganfra
ElementBot
Benoit Marty