AndroidManager - module for managing android emulators

[aefrgn]

@thepappo said in AndroidManager - module for managing android emulators:

@aefrgn because your xpath query is invalid.

@rooory446 said in AndroidManager - module for managing android emulators:

device not found

DEVICES_LIST variable is empty, check that at least 1 device is running.

Even "Take Screenshot" same error.

We do not specify xpath there.
If xpath is wrong, why is it giving a screenshot error?

[thepappo]

@ahmad said in AndroidManager - module for managing android emulators:

When I install any app it gives error

You pass null instead of serial of the device.

@ahmad said in AndroidManager - module for managing android emulators:

And if open any app it gives an error

Also check that SERIAL variable contains correct serial number.

You can execute this command manually in the console for debugging like this:
adb -s YOUR_SERIAL shell am start YOUR_ACTIVITY

this command opens activity YOUR_ACTIVITY.

[ahmad]

This post is deleted!

[ChrisHolmes]

Is there any way to get the device name or index? I found some useful actions, but need each memu name or index.

[thepappo]

@ChrisHolmes memuc listvms. Set memuc at system variables before running.

[ChrisHolmes]

I have already done that. Like, the script works in multithreaded mode.

1. Scripts create MEmu
2. Get the Device List
3. Create resource - devices (serial)
4. Starts server
5. Connects to MEmu (serial)

If you run the script in multi-thread mode, then memuc listvms. it will just list all devices, not the MEmu it connected.

[ChrisHolmes]

@ChrisHolmes said in AndroidManager - module for managing android emulators:

memuc listvms

Found solution. This kinda helped.

[ChrisHolmes]

So maybe someone have idea.

so, I use "Run Process" for specific tasks and works while recording mode - memuc -i [[DEVICEINDEX]] adb “devices” (you need to have adb.exe file in MEmu folder). Whit this it gets serial for the specific MEmu. If I run ADB "devices", it will get serials for all active MEmu (That I don't want)

When I run the script in run mode - it crashes since there are adb.exe files in the platform-tools folder and MEmu folder.

C:\Users\HumbleRecords>where adb
C:\Users\HumbleRecords\AppData\Local\Android\Sdk\platform-tools\adb.exe
C:\Program Files\Microvirt\MEmu\adb.exe

[thepappo]

@ChrisHolmes said in AndroidManager - module for managing android emulators:

so, I use "Run Process" for specific tasks and works while recording mode - memuc -i [[DEVICEINDEX]] adb “devices” (you need to have adb.exe file in MEmu folder).

Why not just use the command adb devices without running memuc or action Get Devices List? In this case you don't need to rename adb.exe from memu folder.

[Peach]

Hello, I like the module very much, great work!
Any solution for typing bug? Error: SubprocessError: Subprocess finished with code 1. Error: adb: failed to stat Release/BrowserAutomationStudio/apps/25.3.8/e/0d00.mNPT/distr/app/lib/ADBKeyboard.apk: No such file or directory ". I tried installing manually the apk but didnt help.

[ChrisHolmes]

@Peach did you set the path to Platform-Tools?

open cmd and type where adb

[Peach]

@ChrisHolmes Yes I have it, where adb works

[ahmad]

The script runs perfectly fine but at a certain point the script stops with this message۔

Thread ended with message "invalid session id: A session is either terminated or not started"

[caras269]

Hello, first of all I like the module very much, thank you.

my question

If we set memu , apium and jdk on each of the remote machines (rdp) as you mentioned in your first message, can the module access the apiums on the rdp's on the remote machines and run on android emulators?

[thepappo]

@Peach said in AndroidManager - module for managing android emulators:

Hello, I like the module very much, great work!
Any solution for typing bug? Error: SubprocessError: Subprocess finished with code 1. Error: adb: failed to stat Release/BrowserAutomationStudio/apps/25.3.8/e/0d00.mNPT/distr/app/lib/ADBKeyboard.apk: No such file or directory ". I tried installing manually the apk but didnt help.

Is this issue has occured when you started the compiled script? I already answered in Russian topic.

@caras269 said in AndroidManager - module for managing android emulators:

If we set memu , apium and jdk on each of the remote machines (rdp) as you mentioned in your first message, can the module access the apiums on the rdp's on the remote machines and run on android emulators?

Good question. I didn't test it. Please let us know here if you check it.

[Peach]

@thepappo Hello, No, not in complied script, I get this error during the script editor/recorder.

[thepappo]

@Peach ok, anyway I plan to add the checkbox to disable installation of this apk in the next update.

UPD. Checked the code. If you install AdbKeyboard manually, then it should work.

[ChrisHolmes]

For some reason I'm getting a lot of this error

Thread #1 : Thread ended with message "Embedded language execution timeout"

[aefrgn]

@aefrgn said in AndroidManager - module for managing android emulators:

@thepappo said in AndroidManager - module for managing android emulators:

@aefrgn because your xpath query is invalid.

@rooory446 said in AndroidManager - module for managing android emulators:

device not found

DEVICES_LIST variable is empty, check that at least 1 device is running.

Even "Take Screenshot" same error.

We do not specify xpath there.
If xpath is wrong, why is it giving a screenshot error?

please answer my question

[thepappo]

@ChrisHolmes these errors can occur due to nodeJS timeout. When your script does nothing for a timeout.