How to debug your build locally / "It works on my Mac/PC but not on bitrise.io"

viktorbenei · January 23, 2017, 9:42am

If the build works on your local Mac/PC but not on bitrise.io, that’s usually because of uncommitted / gitignored files or a tool version difference. There can be other reasons, for example in case of iOS code signing errors it’s usually because a code signing file which is available on your Mac, but you did not upload it to bitrise.io and so it’s not available there.

In any case, the first steps you should try, preferably before you’d report the issue (as this will be the first thing we’ll ask for anyway ;)) is to do a full clean clone of your project, and try to run the build there. This helps to eliminate the most common issue, that you have a file in your project’s regular working directory which is not committed into git, and so it’s not available when bitrise.io clones the repository.

Testing with a full clean git clone

open your Terminal / Command Line
type in: cd /tmp
clone your repository with: git clone REPOURL ./quick-repo-test --branch BRANCH-YOU-WANT-TO-TEST
- example: git clone https://github.com/bitrise-io/bitrise.git ./quick-repo-test --branch master
cd ./quick-repo-test

and then run the commands you want to test, to build your project, or open the project file from this directory (you can open the directory in Finder / file browser by typing in: open .).

Test with the Bitrise CLI

You can also run the same build locally, using the Bitrise CLI. For this, follow the steps in the previous section (Testing with a full clean git clone), and once you’re in the /tmp/quick-repo-test directory:

Do a clean git clone, as described in the previous section: Testing with a full clean git clone
Install the Bitrise CLI following the install instructions (it takes less than a minute to install it, the Bitrise CLI is distributed as a single binary, without any installer)
Download your app’s bitrise.yml from bitrise.io:
1. open the app on bitrise.io
2. click the Workflow tab to open the Workflow Editor
3. on the left side select bitrise.yml
4. download the yml and save it into /tmp/quick-repo-test with the file name bitrise.yml
Now that you have the bitrise.yml in /tmp/quick-repo-test, run the build with: bitrise run WORKFLOW-TO-RUN (e.g. bitrise run primary)

This should help to reproduce the issue in most cases.

Additional notes for iOS projects

Make sure that you run the tests in the same simulator as the one bitrise.io runs. If you use the Bitrise CLI to run the tests locally this is not required, that uses the same configuration.
If you’re debugging an iOS unit/UI test issue, please make sure to reset the iOS Simulator (in the Simulator app select the Simulator menu bar item → then Reset Content and Settings…).

Additional notes for Android/Gradle projects

If you still can’t reproduce the issue locally (after following the previous steps), you might also want to delete the $HOME/.gradle (hidden) directory, to clear your Gradle caches. (Quick Terminal / Command Line command: rm -rf $HOME/.gradle)

Download and use the Android/Linux environment

This only works if your project uses the Android/Linux environment. If you do, that’s awesome, as you can download and use the exact same environment as the one your build is running in on bitrise.io!

To do this, please follow this guide: https://bitrise-io.github.io/devcenter/docker/run-your-build-locally-in-docker/

Note: for best efficiency you should first do a clean git clone (as described above → Testing with a full clean git clone) and run docker from there, so that files which are in your .gitignore won’t affect the build, and the build can run the way how it runs on bitrise.io.

Still doesn’t work

Please report the issue at http://discuss.bitrise.io/c/issues/build-issues - we’ll try to help as soon as possible!

viktorbenei · August 16, 2017, 7:51pm

Most frequent UI/Unit Test issues:

Timezone: make sure your tests can run in any timezone, or mock the timezone. You most likely run your tests on your Mac in a different timezone, not the one the bitrise.io build servers are running in.
Clean simulator (especially iOS Simulator): your tests will run with a clean simulator on bitrise.io; when testing locally please make sure to use a clean simulator (iOS Simulator: “Reset Content and Settings”).
Simulator device: make sure to test with the same device and OS version locally when debugging issues. Your UI tests might expect a certain resolution or other parameter of a device (e.g. if you compare screenshots).

viktorbenei · September 20, 2017, 1:50pm

iOS Code Signing - debugging Provisioning Profiles:

Xcode looks for provisioning profiles in a single directory: $HOME/Library/MobileDevice/Provisioning Profiles

To test whether your app can be signed with the given signing files (e.g. the one you upload(ed) to bitrise.io):

Create a new directory, e.g. on your Desktop, call it “ProvProfile-Backup”
Open the ~/Library/MobileDevice/Provisioning Profiles directory
- from Finder: click Go (menu) -> Go to Folder and then copy paste: ~/Library/MobileDevice/Provisioning Profiles
- or if you prefer the Terminal, run: $ open "$HOME/Library/MobileDevice/Provisioning Profiles"
Move all files from ~/Library/MobileDevice/Provisioning Profiles into the “Backup” directory, to have a backup. Make sure that ~/Library/MobileDevice/Provisioning Profiles is empty!
Now, activate the provisioning profiles you want to test, e.g. download from bitrise.io and double click the files, or just move them into the ~/Library/MobileDevice/Provisioning Profiles directory. Note: if you double click a provisioning profile file, Xcode simply copies that file into the ~/Library/MobileDevice/Provisioning Profiles directory, with the UDID of the profile as the filename, but the filename does not matter actually.
Now try to build / archive / etc your project.

If the build fails, or you’re prompted that files have to be downloaded that means that those files are also required for the actions you do, so you’ll have to upload those files to bitrise.io as well.

Once you can perform all the actions (build, archive, generate ipa, etc.) you want to, that means that all required provisioning profiles are in ~/Library/MobileDevice/Provisioning Profiles, and you can simply upload all of the provisioning profile files from ~/Library/MobileDevice/Provisioning Profiles bitrise.io / copy to another Mac etc. and if the certificate is available on the Mac (or on bitrise.io) the build, archive, export ipa etc. actions will work on the other Mac too.

viktorbenei · October 17, 2017, 6:40pm

iOS Code Signing - debugging Certificates (.p12):

The same “temporary remove” for Certificate (which is about the same as for the Prov Profiles above) looks like this:

Open Keychain Access on your Mac
On the left side select the login Keychain (top left area)
Select the My Certificates Category on the left side (bottom left area)
Now, create a backup by selecting all the items on the right side (e.g. by clicking into the right side list and hitting Cmd + a)
Screen_Shot_2017-10-17_at_20_34_021179×746 66.9 KB
Right click → Export X items…
Save it into a .p12 file e.g. to your Desktop (that .p12 will include all of the certificates and private keys you selected!)
Make sure it’s properly backed up, as private keys can’t be regenerated!! You’ll have to generate new ones if you’d accidentally delete or lose this .p12!
Now that you have your backup, go back to Keychain Access, select all items just like you did before (same Keychain and Category, exactly the same steps) then Right click → Delete X items… to delete those certs.

At this point your certificate list is empty and you can experiment with importing e.g. the .p12 you uploaded to bitrise.io or with any other .p12 file (e.g. the one you got from your colleague) and try to build with those.

Once you want to restore the original certs simply double click the .p12 backup file you created and that will restore all the original certs & private keys.

webmasterdragon · August 3, 2020, 5:52pm

I have similar issue here.
On my local bitrise is success and I can install app via testflight.
But on remote bitrise build is something wrong, I can’t install app via testflight.
Both build are success and uploaded to testflight, local bitrise build is working normally.
All stack should be same since I am using same bitrise.yml file on both build.
I am using fastlane for my React Native build.
Anyone can help me better track issue?

bitce · August 14, 2020, 1:08pm

Hi @webmasterdragon,

Sorry to hear about this! Can you please raise this issue either in a separate thread, or contact support directly for more prompt help? Thanks!

webmasterdragon · August 14, 2020, 1:41pm

It is here separate request.

Rolika · October 14, 2020, 7:15am

Hi.

Using the same simulator plus clean simulator still giving error

it is running on my local while in bitrise it is giving no such element found then time out issue.

ment’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 37457 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 38580 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 40081 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 41085 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 42314 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 43513 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 44242 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 45022 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 46800 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 47743 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 48613 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [BaseDriver] Waited for 49467 ms so far

[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’

[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0/element] with body: {“strategy”:“id”,“selector”:“action_messaging”,“context”:"",“multiple”:false}

[WD Proxy] Got response with status 404: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:257)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:50)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann…

[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError

[debug] [W3C (41c1194b)] Encountered internal error running command: NoSuchElementError: An element could not be located on the page using the given search parameters.

[debug] [W3C (41c1194b)] at AndroidUiautomator2Driver.findElOrEls (/usr/lib/node_modules/appium/node_modules/appium-android-driver/lib/commands/find.js:75:11)

[debug] [W3C (41c1194b)] at runMicrotasks ()

[debug] [W3C (41c1194b)] at processTicksAndRejections (internal/process/task_queues.js:97:5)

[HTTP] <-- POST /wd/hub/session/41c1194b-b23f-4ec7-a3a3-cf3e615c5da7/element 404 61232 ms - 490

[HTTP]

[HTTP] --> DELETE /wd/hub/session/41c1194b-b23f-4ec7-a3a3-cf3e615c5da7

[HTTP] {}

[debug] [W3C (41c1194b)] Calling AppiumDriver.deleteSession() with args: [“41c1194b-b23f-4ec7-a3a3-cf3e615c5da7”]

[debug] [BaseDriver] Event ‘quitSessionRequested’ logged at 1602658450715 (06:54:10 GMT+0000 (Coordinated Universal Time))

[Appium] Removing session 41c1194b-b23f-4ec7-a3a3-cf3e615c5da7 from our master session list

[debug] [UiAutomator2] Deleting UiAutomator2 session

[debug] [UiAutomator2] Deleting UiAutomator2 server session

[debug] [WD Proxy] Matched ‘/’ to command name ‘deleteSession’

[debug] [WD Proxy] Proxying [DELETE /] to [DELETE http://127.0.0.1:8200/wd/hub/session/dae8b57c-808a-4d14-be5e-29440cb557f0] with no body

[debug] [WD Proxy] Got response with status 200: {“sessionId”:“dae8b57c-808a-4d14-be5e-29440cb557f0”,“value”:null}

[debug] [UiAutomator2] Resetting IME to ‘com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME’

[debug] [ADB] Running ‘/opt/android-sdk-linux/platform-tools/adb -P 5037 -s emulator-5554 shell ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME’

[debug] [Instrumentation] .

[debug] [ADB] Running ‘/opt/android-sdk-linux/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop app.work.rxr.io.stg’

[debug] [Instrumentation] Time: 563.19

[debug] [Instrumentation]

[debug] [Instrumentation] OK (1 test)

[debug] [Logcat] Stopping logcat capture

[debug] [ADB] Removing forwarded port socket connection: 8200

[debug] [ADB] Running ‘/opt/android-sdk-linux/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp:8200’

[UiAutomator2] Restoring hidden api policy to the device default configuration

[debug] [ADB] Running ‘/opt/android-sdk-linux/platform-tools/adb -P 5037 -s emulator-5554 shell ‘settings delete global hidden_api_policy_pre_p_apps;settings delete global hidden_api_policy_p_apps;settings delete global hidden_api_policy’’

[debug] [Instrumentation] The process has exited with code 0

[debug] [BaseDriver] Event ‘quitSessionFinished’ logged at 1602658458376 (06:54:18 GMT+0000 (Coordinated Universal Time))

[debug] [W3C (41c1194b)] Received response: null

[debug] [W3C (41c1194b)] But deleting session, so not returning

[debug] [W3C (41c1194b)] Responding to client with driver.deleteSession() result: null

[debug] [W3C (41c1194b)] Destroying socket connection

[HTTP] <-- DELETE /wd/hub/session/41c1194b-b23f-4ec7-a3a3-cf3e615c5da7 200 7677 ms - 14

[HTTP]

[ERROR] Tests run: 5, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 622.48 s <<< FAILURE! - in TestSuite

[ERROR] qa.testing.Controlpagetesting.Elocationtest Time elapsed: 131.798 s <<< FAILURE!

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of Located by By.chained({By.id: propertyFilterTextView}) (tried for 60 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.Elocationtest(Controlpagetesting.java:377)

Caused by: org.openqa.selenium.NoSuchElementException: Can’t locate an element by this strategy: By.chained({By.id: propertyFilterTextView})

at qa.testing.Controlpagetesting.Elocationtest(Controlpagetesting.java:377)

Caused by: org.openqa.selenium.TimeoutException: Expected condition failed: waiting for io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction@6dab9b6d (tried for 1 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.Elocationtest(Controlpagetesting.java:377)

Caused by: org.openqa.selenium.NoSuchElementException:

Cannot locate an element using By.chained({By.id: propertyFilterTextView})

For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’

System info: host: ‘prd-latest-use1c-201014062802-xgepytwsdn2tvojcypbjxh’, ip: ‘10.0.0.250’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.4.0-57-generic’, java.version: ‘1.8.0_265’

Driver info: driver.version: AndroidDriver

at qa.testing.Controlpagetesting.Elocationtest(Controlpagetesting.java:377)

[ERROR] qa.testing.Controlpagetesting.FEhometraffic Time elapsed: 101.301 s <<< FAILURE!

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of Located by By.chained({By.id: app.work.rxr.io.stg:id/footTrafficLinearLayout}) (tried for 60 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.FEhometraffic(Controlpagetesting.java:418)

Caused by: org.openqa.selenium.NoSuchElementException: Can’t locate an element by this strategy: By.chained({By.id: app.work.rxr.io.stg:id/footTrafficLinearLayout})

at qa.testing.Controlpagetesting.FEhometraffic(Controlpagetesting.java:418)

Caused by: org.openqa.selenium.TimeoutException: Expected condition failed: waiting for io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction@6a55299e (tried for 1 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.FEhometraffic(Controlpagetesting.java:418)

Caused by: org.openqa.selenium.NoSuchElementException:

Cannot locate an element using By.chained({By.id: app.work.rxr.io.stg:id/footTrafficLinearLayout})

For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’

System info: host: ‘prd-latest-use1c-201014062802-xgepytwsdn2tvojcypbjxh’, ip: ‘10.0.0.250’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.4.0-57-generic’, java.version: ‘1.8.0_265’

Driver info: driver.version: AndroidDriver

at qa.testing.Controlpagetesting.FEhometraffic(Controlpagetesting.java:418)

[ERROR] qa.testing.Controlpagetesting.JWellnesslocation Time elapsed: 112.175 s <<< FAILURE!

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of Located by By.chained({By.id: action_messaging}) (tried for 60 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.JWellnesslocation(Controlpagetesting.java:493)

Caused by: org.openqa.selenium.NoSuchElementException: Can’t locate an element by this strategy: By.chained({By.id: action_messaging})

at qa.testing.Controlpagetesting.JWellnesslocation(Controlpagetesting.java:493)

Caused by: org.openqa.selenium.TimeoutException: Expected condition failed: waiting for io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction@421bba99 (tried for 1 second(s) with 500 milliseconds interval)

at qa.testing.Controlpagetesting.JWellnesslocation(Controlpagetesting.java:493)

Caused by: org.openqa.selenium.NoSuchElementException:

Cannot locate an element using By.chained({By.id: action_messaging})

For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’

System info: host: ‘prd-latest-use1c-201014062802-xgepytwsdn2tvojcypbjxh’, ip: ‘10.0.0.250’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.4.0-57-generic’, java.version: ‘1.8.0_265’

Driver info: driver.version: AndroidDriver

at qa.testing.Controlpagetesting.JWellnesslocation(Controlpagetesting.java:493)

[INFO]

[INFO] Results:

[INFO]

[ERROR] Failures:

[ERROR] Controlpagetesting.Elocationtest:377->BaseTest.click:193->BaseTest.waitForVisiability:184 » Timeout

[ERROR] Controlpagetesting.FEhometraffic:418->BaseTest.click:193->BaseTest.waitForVisiability:184 » Timeout

[ERROR] Controlpagetesting.JWellnesslocation:493->BaseTest.click:193->BaseTest.waitForVisiability:184 » Timeout

[INFO]

[ERROR] Tests run: 5, Failures: 3, Errors: 0, Skipped: 0

[INFO]

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 10:34 min

[INFO] Finished at: 2020-10-14T06:54:20+00:00

[INFO] Final Memory: 25M/463M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project ProjectLLITY: There are test failures.

[ERROR]

[ERROR] Please refer to /bitrise/src/android_automation/tenant-ios-automation/target/surefire-reports for the individual test results.

[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.

[ERROR] -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

total 101792

bitce · October 29, 2020, 1:47pm

Hey @Rolika please create a seperate issue report or contact us directly about this!

Topic		Replies	Views
Bitrise macOS client Development	9	1771	August 31, 2020
Github repo cannot be found Builds ios	4	3076	September 11, 2018
Got success message for everything in BitRISE CLI locally but no build released Question & Answer ios	2	886	January 29, 2018
Build succeeded previously were failing now with out any change on the code Builds	5	2314	July 6, 2019
How to experiment with Bitrise configs locally, on your Mac/Linux Debugging bitrise-cli	22	10149	April 13, 2022

How to debug your build locally / "It works on my Mac/PC but not on bitrise.io"

Testing with a full clean git clone

Test with the Bitrise CLI

Additional notes for iOS projects

Additional notes for Android/Gradle projects

Download and use the Android/Linux environment

Still doesn’t work

Related Topics