where is the use guiedence bro
AndroidManager - module for managing android emulators
-
Come on, support you to improve the program
-
@shashou520 I'm afraid there is no point in improving. I looked at the issue with multithreading, it looks like the problem is on the library side and is related to the ports on which the server is running.
Therefore, I see no reason to improve software that works in 1 thread. Perhaps in the future I will try to write a server, but this is not certain. ;)
If anyone knows a node package with no issues - let me know and I'll rewrite on it. As exampe here is python module which I use for automation. But I didn't see any its implementations on node js.
-
-
thanks Look forward to your perfect improvement of the module
-
Hello thanks for module
Im having issues installing this module any help ?
-
@boliotrmezemer hello, the screenshots won't open.
-
Hello was really looking for this.
Can u by any chance make a video how to setup this for the newbies for example how to connect with the android device , i smh cant figure that out.
Is there anything required to install in bas to be installed for it to work. Thanks!
-
@hetznerrdps hello, you can check manual from the start post that contains info about preparing your PC to work with emulators. Also see an example of BAS template there.
-
BAS KHÔNG CHUYÊN DỤNG ĐỂ LÀM VIỆC NÀY, TẠI SAO PHẢI CỐ GẮNG
-
Version 2.0
The main change in this version is the move to Appium, which uses the uiautomator2 driver to send commands to emulators. Appium is used for all actions related to interacting with elements via xpath, as well as for the actions "Connect to Device" (a session is created for the specified device by serial number on the server), "Disconnect from Device", "Take Screenshot", "Open Notifications Panel" and "Get XML dump".
Due to the use of appium, multithreading is now working.
Other changes:
- Node js has been updated to version 18.10.0.
- Removed actions:
- "Device Info" - there is no method for this action in the appium, and it is not clear what device settings need to be collected.
- Added actions:
- "Start Server";
- "Stop Server";
- "Is App Installed";
- "Is App Running";
- "Open Notifications Panel".
- Changed action settings:
- "Connect to Device" - all fields except "Serial number" have been removed. Added "Set up device" selector;
- "Take Screenshot" - removed the fields "Image quality" and "Save method on device" (appium does not allow to choose the quality and the folder for saving on the device itself).
For the following actions, the "Number of steps" parameter has been changed to "Duration, ms":
- "Long Click by Xpath";
- "Long Click by Coordinates";
- "Swipe on Screen".
- Fixed a bug in the "Scroll to Element" action. If "to the left" or "to the right" was selected in the scroll direction, then the scroll was performed down.
- Timeouts are now passed to Node js from the settings for actions that require a wait.
Please see the detailed instructions for installing the environment and launching the module in the first post.
-
Is there any documentation on how to use it? How to open/install apps, etc? Maybe Sample BAS file?
-
@ChrisHolmes said in AndroidManager - module for managing android emulators:
Maybe Sample BAS file?
The sample is in the first post
-
-
Hello, thank you so much for this module. One question.
how can I get a device list? -
@wakid48219 are you joking? :) The name of the first action is "Get Devices List".
