Closed jamesvanhorn closed 1 year ago
So I was able to "solve" this in a hacky way and I'm on the hunt now for the right way.
My fix:
Is there a way to specify this dependency using an Appium capability? I'll admit I don't know a ton about the android build process so I could be way off base, but this fix did work in successfully starting a session though and unblocking me for locally. The fix isn't portable at all though other environments.
Is there a way to specify this dependency using an Appium capability?
No, maybe it has no way. How the test target app's dependencies refer to it? I wonder if it is not adding dependencies in https://github.com/appium/appium-espresso-driver/blob/master/espresso-server/app/build.gradle.kts#L91-L146 For example, it needs additional references in https://github.com/appium/appium-espresso-driver/blob/master/espresso-server/build.gradle.kts
in case anyone else stumbles across this, the answer ended up being to declare the library which uses lib yoga.so (br.com.zup.beagle:beagle-yoga-layout:1.19.0) under additionalAndroidTestDependencies
but NOT under additionalAppDependencies
This packaged the libyoga.so file into the espresso test server apk and then things worked fine.
Appium version: 2.0.0-beta.53 Espresso driver version: espresso@2.15.1
Issue: Seems like our app developers added some new dependencies which are breaking things. Espresso server and session starts, but then fails with a cryptic error message I haven't been able to solve. Seems like we need to add some new additionalAppDependency but I can't figure out what.
Capabilities
Error snippet:
Any ideas on how to track down the needed dependency?