hi everybody, does anyone use "mobile:swipe" in XCUI iOS?
I am trying to get the coordinate differences of the viewport between before and after the swipe
i am in NATIVE context
Unable to create a new remote session. Please check the server log for more details. Original error: Could not start Mobile Browser Reason: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'app.com.devrelease' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command 'android-sdk/platform-tools/adb -P 5037 -s 66a402b3 shell am start -W -n app.com.devrelease/com.app.activities.SplashActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability (WARNING: The server did not provide any stacktrace information)Hi all, i'm running my appium throw browserstack and i get the following error. any one saw this before and can help me?
any one?
Hey, you solved this problem?
I am facing this error here running ios app automate on Browserstack.
@jonathansouza-hotmart: try to contact the support team of Browserstack
hi @FelixPWAC , I use "mobile:swipeGesture" for android and "mobile:swipe" for iOS
there is a way to " element.touchAction([
{ action: "tap" },
"release",
]);" in the center of the element?
{ action: "tap" },
"release",
]);" in the center of the element?
sometimes in iOS it taps outside of the element
appium does not accept this
ok, Felix I can share you an example. I was going crazy to make it work, because I have to test a react native mobile app
const swipeGesture = (dir, scrollViewElement) => {
if (browser.isAndroid) {
// Android UiAutomator2
driver.execute("mobile:swipeGesture", {
direction: dir,
elementId: scrollViewElement.elementId,
});
} else {
// iOS XCUITest
driver.execute("mobile:swipe", {
direction: dir,
element: scrollViewElement.elementId,
});
}
};
if (browser.isAndroid) {
// Android UiAutomator2
driver.execute("mobile:swipeGesture", {
direction: dir,
elementId: scrollViewElement.elementId,
});
} else {
// iOS XCUITest
driver.execute("mobile:swipe", {
direction: dir,
element: scrollViewElement.elementId,
});
}
};
in android uia2 you can use the gesture "mobile:swipeGesture", while in iOS XCUI Test you can use "mobile:swipe"
this example is webdriverIO, JS
besides I have no idea how the logic for the above code works
I was scrolling happily before I updated appium
with the below code
public void scrollIntoText(String input) {
public void scrollIntoText(String input) {
driver.findElement(MobileBy.AndroidUIAutomator("new UiScrollable(new UiSelector.scrollable(true))"+ ".scrollIntoView(new UiSelector.text(\""+input+"\"))"));}
@federicoitaly:matrix.org can you modify the below code to make scroll work as i Cant but it looks promising
JavascriptExecutor js = (JavascriptExecutor) driver;
HashMap<String, String> scrollObject = new HashMap<String, String>();
scrollObject.put("direction", "down");
js.executeScript("mobile: scroll", scrollObject);
JavascriptExecutor js = (JavascriptExecutor) driver;
HashMap<String, String> scrollObject = new HashMap<String, String>();
scrollObject.put("direction", "down");
js.executeScript("mobile: scroll", scrollObject);
HI @FelixPWAC , yes I know UiScrollable, I've used it as it is very quick, but eventually I decided to use "mobile:swipeGesture", although it's slower it's more accurate and in this way I have similar code for iOS and android
im new at here i have an problem and i wanna find an solution for this problem https://share.getcloudapp.com/12u4BrKj
Hi Guys , I am facing sudden slwodown issue on Android scripts (using wdio with appium) it wont click on element for 20seconds which was working fine earlier and we have found out that its beacaue of GradienText being used in app code, when i repalced it with RegalarText script started working fine. I am using uiautomator2 and resource-id locator strategy , can somebody suggest any solution ?
How can we verify the options available on screen when a video is playing in appium?
Can any one please suggest me how to achieve this?
's login screen.
Hi guys sometimes i got this problem, can someone has solution to fix it? thanks Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: socket hang up
Hi Guys , does anybody know how to parametrize App path in appium which gets build in /user/{username}/Library/Developer/Xcode/DerivedData/{MobileApp-sdfjhslkfllkjklfd} this is unique id on individual machine when the ios app is build}/Builds/Product/Debug-iphonesimulator/MobileApp.app
Hi Guys, I'm running my test script on emulator, and sometime i got the error message below:
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
Can you help me to solve this?
Hi @all I'm a beginner to Appium, I am facing this issue while opening my Testing App, I using Appium 1.21.0
'com.google.android.permissioncontroller' and fully qualified activity name : 'com.android.permissioncontroller.permission.ui.ReviewPermissionsActivity'
Code:
- TouchAction tc = new TouchAction(driver);
tc.tap(TapOptions.tapOptions().withElement(ElementOption.element(uidemo.btn_permission_continue)));
- @FindBy(id="com.android.permissioncontroller:id/continue_button")
public AndroidElement btn_permission_continue;
@Chienjen @worikgh @nileshpethe @Automation125
appium/appium#10642 this is still replicating on the latest version 1.21.0 but this was closed long back ago and no option to re-open
How to solve the problem of error in identifying wechat applet?