https://s3-us-west-2.amazonaws.com/endtest-tests/NZ82qFazDW8MuBV0Wo1HsYlPhobq3X/Element_Inspector_2.html
See more: https://th.wikipedia.org/wiki/%E0%B8%9C%E0%B8%B9%E0%B9%89%E0%B9%83%E0%B8%8A%E0%B9%89:Ferrell_Sykes/%E0%B8%97%E0%B8%94%E0%B8%A5%E0%B8%AD%E0%B8%87%E0%B9%80%E0%B8%82%E0%B8%B5%E0%B8%A2%E0%B8%99
16 replies
i have a Screen with a button.
but with the inspector i cant get the button.
i checked the whole structure and go through everything. i cant get it .
when i try to pick it with the "Screenshot" i cant get the button. Just the whole Screen.
any ideas?
with appium i cant access any type of elements in the Screen. it just highlights the whole screen
So i solve this Problem.
For everyone who is struggeling with Appium.
If you use the Inspector and you cant select a element because the whole Screen is selected you have to set"appium:settings[snapshotMaxDepth]": 60 in your Capabilities.
It took now 2-3 Hours to research this shit in the Internet.
i hope i can help someone who is searching here :)
1 reply
Hi!
I had a quick, broad question. I want to use Appium to automate my dating app swiping on apps like Bumble and Tinder.
I downloaded Appium and did some research with iOS, and it seems like I cannot automate production applications (ipa), dude to limitations with Xcode. However, it seems like in Android, I can. I was able to get Appium Server and Inspector running, along with Android Studio. I downloaded the Bumble .apk and got everything connected, but the .apk wasn't running correctly in the Android Studio emulator.
I am thinking of buying a very cheap Android phone and downloading the apps on there. Can I still use the Server and Inspector to connect to the phone via USB, and automate swiping on production applications that are already installed on the phone? Or is Appium only limited to testing development applications?
1 reply
I am trying to run automation tests in Bitrise but got an error. I can run my tests on my local machine and everything is ok.
*> device: simulator iOS 15.4
machine: Xcode 13.3.x on macOS 12.2 java: 17 selenide 6.4.0 appium 1.22.3 gradle 7.4 Node.js: 12.22.11 NPM: 6.14.16*
Could you please help me?
**2022-04-18T15:44:00.567+0000 [DEBUG] [TestEventLogger] [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-04-18T15:44:00.567+0000 [DEBUG] [TestEventLogger] [debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8237/status] with no body
2022-04-18T15:44:00.568+0000 [DEBUG] [TestEventLogger] [WD Proxy] connect ECONNREFUSED 127.0.0.1:8237
2022-04-18T15:44:01.571+0000 [DEBUG] [TestEventLogger] [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2022-04-18T15:44:01.571+0000 [DEBUG] [TestEventLogger] [debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8237/status] with no body
2022-04-18T15:44:01.572+0000 [DEBUG] [TestEventLogger] [WD Proxy] connect ECONNREFUSED 127.0.0.1:8237
2022-04-18T15:44:02.335+0000 [DEBUG] [TestEventLogger]
2022-04-18T15:44:02.335+0000 [DEBUG] [TestEventLogger] com.tunein.mobile.tests.ios.IosBooksAroundFirstTest.beforeTest STARTED
2022-04-18T15:44:02.390+0000 [DEBUG] [TestEventLogger]
2022-04-18T15:44:02.390+0000 [DEBUG] [TestEventLogger] com.tunein.mobile.tests.ios.IosBooksAroundFirstTest.beforeTest FAILED
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:585)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:225)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:164)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:79)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:87)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//io.appium.java_client.ios.IOSDriver.<init>(IOSDriver.java:105)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.tunein.mobile.appium.driverprovider.IosDriverProvider.createDriver(IosDriverProvider.java:73)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.webdriver.DefaultDriverFactory.createInstanceOf(DefaultDriverFactory.java:40)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.webdriver.DefaultDriverFactory.create(DefaultDriverFactory.java:29)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.webdriver.WebDriverFactory.createWebDriverInstance(WebDriverFactory.java:109)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.webdriver.WebDriverFactory.createWebDriver(WebDriverFactory.java:69)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.drivercommands.CreateDriverCommand.lambda$createDriver$1(CreateDriverCommand.java:80)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.logevents.SelenideLogger.get(SelenideLogger.java:165)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.drivercommands.CreateDriverCommand.createDriver(CreateDriverCommand.java:53)
2022-04-18T15:44:02.391+0000 [DEBUG] [TestEventLogger] at app//com.codeborne.selenide.impl.WebDriverTIn case you won't find the magic solution for your problem, you should try it.
2 replies
Hi Everyone, LinkedIn is hiring a Software Engineer - Android. Anywhere in the US, full time.
In this role, you will design and execute user-facing features for the native LinkedIn app as well as LinkedIn Learning app on Android devices, by leveraging mobile operating system frameworks for multi-threading, persisting data, and managing user experience and graphics across multiple screen sizes.
Key Skills: API, Android, OOP, (MVC/MVVM/MVP), Data structures and Algorithms
Please send your resume directly at masundaray@linkedin.com, or ping me if you have any queries.
i get the error when i start server Appium automatic, but when i run manual by appium -p 4723 still runs well. my code : service=AppiumDriverLocalService.buildService(new AppiumServiceBuilder()
.withArgument(GeneralServerFlag.SESSION_OVERRIDE)
.withLogFile(new File( "Server.log")));
// service = AppiumDriverLocalService.buildService(builder);
service.start(); my error
[Appium] Non-default server args:
[Appium] address: 127.0.0.1
[Appium] sessionOverride: true
[Appium] logFile: C:\Users\GIANGTHAO\Desktop\Git\SerenityAppium\Server.log
[Appium] Appium REST http interface listener started on 127.0.0.1:4723
[HTTP] --> GET /status
[HTTP] {}
[debug] [HTTP] No route found for /status
[HTTP] <-- GET /status 404 10 ms - 211
[HTTP]
[HTTP] --> GET /status
[HTTP] {}
[debug] [HTTP] No route found for /status
[HTTP] <-- GET /status 404 8 ms - 211
[HTTP]
[HTTP] --> GET /status
[HTTP] {}
[debug] [HTTP] No route found for /status
[HTTP] <-- GET /status 404 2 ms - 211
[HTTP]
[HTTP] --> GET /status
[HTTP] {}
[debug] [HTTP] No route found for /status
[HTTP] <-- GET /status 404 1 ms - 211
[HTTP]
- driver.switchTo().alert(); and then accept alert
2.capabilities.setCapability(“autoAcceptAlerts”,true);
Java appium 8.0.0
If I set implicit wait once then I change it later it doesn't take effect for some reason. If I call getImplicitWaitTimeout I get the correct value, but in real it is not using that
Any suggestion?
Any suggestion???
hello everyone,
Have you ever used appium mobile terminal automatic replacement test? The previous appium version used by the server was 1.8.1. Because the version was too low, many functions of the new version could not be used (for example, by copying the content on the clipboard and pasting the copied content in the input box of the Tiktok app page. 1.8.1 does not have this function. It needs to scroll constantly to find the desired anchor or content. The code is very redundant, etc.), but there are no problems such as the slow connection between the server and the mobile phone The program can't get the elements on the mobile app because of the slow interaction. At present, appium 1.0 is installed on the test server because you want to use the new functions of the higher version of appium Version 22.3, but there is a problem that the program on the server is very slow to obtain the elements in the mobile app, which often leads to the failure to obtain the elements and the interruption of the connection.
