Bug #12094 - Fix _appiumStart method#12095
Bug #12094 - Fix _appiumStart method#12095christian-bromann merged 45 commits intowebdriverio:mainfrom
Conversation
…smine. Update the Cucumber Step Mode. Change constants and option names.
The _startAppium is stucking whitout timeout when the promise emit 'data' but the data not includes the specific text. I've set a timeout y default in 60sec by security, and implemented a validation to reject only once at the first failure. Add some comments.
|
@christian-bromann please check this changes. |
christian-bromann
left a comment
There was a problem hiding this comment.
Some last comments/suggestions.
Co-authored-by: Christian Bromann <git@bromann.dev>
Co-authored-by: Christian Bromann <git@bromann.dev>
Signed-off-by: Lara, Manuel <lararojas.mr@gmail.com>
…to bugfix/appium-start-function
@christian-bromann I saw some TC failing. Anything that I can do? - I've just update the branch. |
Signed-off-by: Lara, Manuel <lararojas.mr@gmail.com>
…to bugfix/appium-start-function
Signed-off-by: Lara, Manuel <lararojas.mr@gmail.com>
|
@christian-bromann I sent some fixes :) all test cases are passing now. Sorry hehe |
|
Hey lararojasmr 👋 Thank you for your contribution to WebdriverIO! Your pull request has been marked as an "Expensable" contribution. We are looking forward to more contributions from you in the future 🙌 Have a nice day, |
|
Hey, let me check this now. Thanks for reporting it.On 31 Jan 2024, at 09:50, Filip ***@***.***> wrote:
Hey, I recently updated from 8.29.1 to 8.29.3 and it looks like this change introduced a bug with logging that generates countless "INFO @wdio/appium-service: Appium started with ID: 496446" messages as can be seen in this screenshot:
image.png (view on web)
Reverting back to 8.29.1 resolves the issue
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
@picakia @christian-bromann A new ticket should be created for this issue, I have the solution but I not sure about how proceed here. |
|
@lararojasmr feel free to just raise a PR, no need to create an extra issue for it if you have a solution already. Thanks for looking into it. |
|
@christian-bromann sorry to late I created a new Issue haha. But I've added the fixes in this PR ☝🏼 |
* Update to RN 0.73 * Change files * RN 73 requires node 18 * Add 72 profile * Update wdio/appium etc to get it running on node 18 * fix * fix * Update podfile locks * fix * fix * fix * see if building fixes resolution of focus-zone by e2e tests * Try specifying reports dir with full path * Try debug level reporting to identify error creating logs * try enabling more logs * alternate way to specify logfile. * downgrade @wdio/appium-service to move before webdriverio/webdriverio#12095 * Test no-packager * yarn init-test-app (With cleanup) * Try install Java18 * fix * fix * Android E2E fixes * fix? * fix * fix * Add more logging for E2E android test failure * more logs * more log * Use actual scroll region, to avoid OS swipe gestures * Increase android time out to navigate to page * fix * remove extra try/catch and logging * Fix windows build * test windows PR without node install --------- Co-authored-by: Saad Najmi <sanajmi@microsoft.com>

Proposed changes
I've added a timeout to the method and fix the issue that happened when the promise emit data but is not include the information that is in the conditional, that could be a error.
I added a rejectOnce method to ensure that the reject is called once.
The bug is #12094.
Types of changes
Checklist
Further comments
Reviewers: @webdriverio/project-committers