Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Espresso server - spawn EINVAL Gradle error message #996

Closed
pbdeguzman opened this issue Apr 18, 2024 · 5 comments
Closed

Espresso server - spawn EINVAL Gradle error message #996

pbdeguzman opened this issue Apr 18, 2024 · 5 comments

Comments

@pbdeguzman
Copy link

pbdeguzman commented Apr 18, 2024

Hi, I'm new here and I tried to use Appium Espresso Driver as my Appium Framework on my Appium Inspector.

  • I run Appium via Command Line.

image

  • Then I setup the Appium Inspector and Start Session. Then, I encounter this error.

image

  • I check my test device and the espresso driver has been installed
    image

Here's my logs:
logs.txt

Is my setup correct? Or is there something missing on my end? Any help would be appreciated.

Thanks,

Patrick

@KazuCocoa
Copy link
Member

I would try out the gradle command directly. Perhaps the espresso server dependencies needs to be coordinated. It is not only building step but also launching the test app via instrument process (in espresso framework) related

@mykola-mokhnach
Copy link
Contributor

Seems related to appium/appium#20008

@pbdeguzman
Copy link
Author

Seems related to appium/appium#20008

Thanks to this I was able to proceed. Now I'm encountering socket hang up. I would try to read some issues regarding this.
image

Logs:
logs - socket hang up.txt

@KazuCocoa
Copy link
Member

The latest issue was your espresso server and the app under test did not have the same signature.

[EspressoDriver@6f23]   "alwaysMatch": {
[EspressoDriver@6f23]     "platformName": "Android",
[EspressoDriver@6f23]     "appium:udid": "0123456789ABCDEF",
[EspressoDriver@6f23]     "appium:deviceName": "p2pro",
[EspressoDriver@6f23]     "appium:automationName": "Espresso",
[EspressoDriver@6f23]     "appium:appPackage": "com.global.wwca",
[EspressoDriver@6f23]     "appium:forceEspressoRebuild": "true",
[EspressoDriver@6f23]     "appium:showGradleLog": "true",
[EspressoDriver@6f23]     "appium:espressoBuildConfig": "{\"additionalAndroidTestDependencies\": [\"androidx.lifecycle:lifecycle-extensions:2.2.0\", \"com.google.android.material:material:1.6.1\",  \"androidx.constraintlayout:constraintlayout:2.1.4\"]}",
[EspressoDriver@6f23]     "appium:ensureWebviewsHavePages": true,
[EspressoDriver@6f23]     "appium:nativeWebScreenshot": true,
[EspressoDriver@6f23]     "appium:newCommandTimeout": 3600,
[EspressoDriver@6f23]     "appium:connectHardwareKeyboard": true
[EspressoDriver@6f23]   },

Both the server package and the application under test must be signed with the same digital signature.

https://github.com/appium/appium-espresso-driver?tab=readme-ov-file#requirements

for example https://github.com/appium/appium-espresso-driver?tab=readme-ov-file#app-signing would help, or use app capability instead of appPackage etc...

@KazuCocoa
Copy link
Member

(closing as the original issue was fixed by the #997)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants