Is there an existing issue for this?
Steps to reproduce
STEPS:
- Chrome must be set as the default browser since FF is not supported
- Start Maestro studio app
- Maestro Studio app opens Chrome to a Maestro page
4." Run from here" - launchApp:
5: The ourskylight.com/welcome page opens
- “Sign in” flow opens the "Log In" Modal
- Credentials are filled in by Maestro
- Credentials pass and are correct
- No other steps - it stops
CODE:
Most Current script: (REPRODUCIBLE FLOW)
url: https://ourskylight.com/welcome
---
- launchApp:
clearState: true
- tapOn: "Sign in"
- assertVisible: "Log In"
- tapOn:
id: "email"
- inputText: “my-user”
- tapOn:
text: "Password"
- inputText: “my-pass”
- assertVisible: "Log In"
- tapOn:
text: "Log In"
retryTapIfNoChange: true
waitToSettleTimeoutMs: 5000
- assertNotVisible: "Password"
Actual results
Actual: All steps pass and credentials are entered are successful
The login modal does not complete the login process or error.
The - assertNotVisible: fails
note: Different assertions were tried to check Maestros connection (and state?) to the login modal.
- After an MS stop/start, an Assertion passed.
- A follow up Run 4 minutes later, the assertion fails.
Screen Shot of results using the code provided in this bug:
- I opened devtools and was surprised the reference changed in the Maestro window from the login modal.
- The external chrome screens are visible with the "Log In" modal on the left.
Expected results
Expected: User to finish the login process -> login modal closes and the webapp moves to a logged in state, home page.
About app
ourskylight.com (2.2.1)
Company is skylight calendar
I believe it is react native.
They use Maestro for there products.
About environment
Environment:
MacBook Pro, Sequoia15.7.5 (2024)
Chrome Version 147.0.7727.56 (Official Build) (arm64)
ourskylight.com (2.2.1)
Maestro Studio 0.9.0, early access
(local) Demo work: /Users/temp DEL/Maestro/demo SL-exploreTask-atLogin.yaml
Logs
Logs
<!-- I do not have access to the logs from ourskylight web app. I do not have Maestro CLI installed -->
Maestro version
N/A
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
MAESTRO STUDIO 0.9.0 / Chrome
SUMMARY:
There is a consistent issue with Maestro Studio when running an app flow that uses a pop-up login modal. "tapOn" shows success but does not complete the login process.
GitBook Assistant supported and recommended this bug report after trying hours of iterations and test checks.
All work is only with Maestro Studio, using Chrome.
April 15th I updated to 0.9.0 alpha release. (yes, early access).
*The login completion with this login modal was working before 0.9.0
Is there an existing issue for this?
Steps to reproduce
STEPS:
4." Run from here" - launchApp:
5: The ourskylight.com/welcome page opens
CODE:
Most Current script: (REPRODUCIBLE FLOW)
Actual results
Actual: All steps pass and credentials are entered are successful
The login modal does not complete the login process or error.
The - assertNotVisible: fails
note: Different assertions were tried to check Maestros connection (and state?) to the login modal.
Screen Shot of results using the code provided in this bug:
Expected results
Expected: User to finish the login process -> login modal closes and the webapp moves to a logged in state, home page.
About app
ourskylight.com (2.2.1)
Company is skylight calendar
I believe it is react native.
They use Maestro for there products.
About environment
Environment:
MacBook Pro, Sequoia15.7.5 (2024)
Chrome Version 147.0.7727.56 (Official Build) (arm64)
ourskylight.com (2.2.1)
Maestro Studio 0.9.0, early access
(local) Demo work: /Users/temp DEL/Maestro/demo SL-exploreTask-atLogin.yaml
Logs
Logs
Maestro version
N/A
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
MAESTRO STUDIO 0.9.0 / Chrome
SUMMARY:
There is a consistent issue with Maestro Studio when running an app flow that uses a pop-up login modal. "tapOn" shows success but does not complete the login process.
GitBook Assistant supported and recommended this bug report after trying hours of iterations and test checks.
All work is only with Maestro Studio, using Chrome.
April 15th I updated to 0.9.0 alpha release. (yes, early access).
*The login completion with this login modal was working before 0.9.0