search

lovelysystems / robotframework-androidlibrary

Robot Framework Automation Library for Android
29 stars 22 forks source link

AndroidLibrary cannot run #64

Open dalewking opened 10 years ago

dalewking commented 10 years ago

The first problem is that calabash-android has moved on and is now at 0.4.x and no longer has an extract-manifest command. That causes the ExPat error reported in #63.

I tried backing up to an older version of calabash-android (0.3.x versions) which gets you past the extract-manifest itself, but then calabash fails to build the instrumentation because the old versions of calabash still expect aapt to be in the platform-tools directory and it was moved to a build-tools directory with later version of the Android tools.

So basically was unable to get this library to work.

memcmp commented 10 years ago

can you solve the problem locally? If so, would you be so kind as to send me a pull request with the fix?

dalewking commented 10 years ago

I don't have a solution, but it seems the easiest approach to get the package and main class is to parse the output of:

aapt dump badging <apk-file>

The output is text, but should be easily parsed to get the necessary information.

One issue will be actually getting the path to the aapt executable since that now lives in build-tools directory and is specific to version.

On Fri, Feb 28, 2014 at 3:12 AM, Philipp Bogensberger < notifications@github.com> wrote:

can you solve the problem locally? If so, would you be so kind as to send me a pull request with the fix?

Reply to this email directly or view it on GitHubhttps://github.com/lovelysystems/robotframework-androidlibrary/issues/64#issuecomment-36329626 .

Dale King