Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null #7353

jhwing · 2016-12-03T02:29:49Z

when i run sample-code android_simple.py i got this error ,i search everywhere ,no result

[debug] [AndroidDriver] Shutting down Android driver
[debug] [AndroidDriver] Called deleteSession but bootstrap wasn't active
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running '/Users/jihongwen/Development/android/android-sdk-macosx/platform-tools/adb' with args: ["-P",5037,"-s","760ABLMW96TX","shell","am","force-stop","io.appium.unlock"]
[debug] [Logcat] Stopping logcat capture
[debug] [AndroidDriver] Not cleaning generated files. Add clearSystemFiles capability if wanted.
[MJSONWP] Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null
at Object.wrappedLogger.errorAndThrow (lib/logger.js:60:13)
at ADB.callee$0$0$ (../../../lib/tools/android-manifest.js:101:9)
at tryCatch (/Users/jihongwen/.nvm/versions/node/v7.2.0/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (/Users/jihongwen/.nvm/versions/node/v7.2.0/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/Users/jihongwen/.nvm/versions/node/v7.2.0/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (/Users/jihongwen/.nvm/versions/node/v7.2.0/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
at process._tickCallback (internal/process/next_tick.js:103:7)
[HTTP] <-- POST /wd/hub/session 500 1585 ms

The text was updated successfully, but these errors were encountered:

joodies · 2016-12-03T08:48:15Z

same issue here withe appium 1.6.2, on windows 7.

same error with appium 1.6.1 on windows 7.

test with latest chrome on android.

sankleta · 2016-12-03T12:50:56Z

#7349 The same here

sravanmedarapu · 2016-12-03T14:34:30Z

Seems something broken with appium-adb v2.9.0, Please downgrade appium-adb to v2.7.0 as a temporary work around.

chanisasuw · 2016-12-03T16:25:01Z

same me via window 7
I installed appium version 1.6.2

sravanmedarapu · 2016-12-03T16:27:49Z

@chanisasuw, I am working on this issue. As a temporary workaround, please downgrade appium-adb to 2.7.0.

npm install appium-adb@2.7.0

mykola-mokhnach · 2016-12-03T17:33:48Z

It is also possible to avoid the issue for now by explicitly setting the android:targetSdkVersion property in the manifest file (https://developer.android.com/guide/topics/manifest/uses-sdk-element.html). It seems like the actual implementation does not respect the fact, that this property can be omitted (and it is equal to android:minSdkVersion in such case).

@jlipps FYI

chanisasuw · 2016-12-03T17:37:04Z

@sravanmedarapu Thank you so much for working this issue, It didn't work for me.

Now i cannot do anything about test

joodies · 2016-12-05T03:14:33Z

tried
npm install -g appium-adb@2.7.0

finally it's working now..

jeangb · 2016-12-05T17:01:00Z

Hi, this workaround "npm install appium-adb@2.7.0" didn't change a thing neither.

devin-joubran-moovel · 2016-12-05T19:49:16Z

Hi,

I'm also experiencing this issue on a mac 10.11.6, android nexus 5 api 23; appium 1.6.2. Tried appium-adb 2.7.0 and no changes

Rdexmah · 2016-12-05T21:42:52Z

Hey I am also facing same issue with ios10.0.1 and with latest appium 1.6.2 beta..
You got any resolution >

cavanpage · 2016-12-06T00:45:37Z

npm install appium-adb@2.7.0 worked for me.

I am pretty new to node so I wasn't installing it into the right place at first.
Make sure you execute that command within the appium directory (for windows the default location for me is C:\Users\myusername\AppData\Roaming\npm\node_modules\appium" )

I am running appium@1.6.0 on windows 7, testing a Samsung S6 with the newest chrome app.

I also had to replace the "appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe" with the latest driver from here https://sites.google.com/a/chromium.org/chromedriver/ . This stopped the "NoSuchSession" error.

My tests are running great now.

lilfry14 · 2016-12-06T00:58:44Z

I was having this issue with appium 1.6 on a Mac 10.11.6 and npm install appium-adb@2.7.0 worked for me.

viveksinghtt · 2016-12-06T07:21:26Z

i have this issue as well...on mac...npm install -g appium-adb@2.7.0 didnt work.... @sravanmedarapu can you please provide a hotfix for this?
On mAc u need to naviagte to folder where appium is installed and then run this command.Then it works fine as @sravanmedarapu said

sravanmedarapu · 2016-12-06T08:22:31Z

@viveksinghtt, Can you please execute nm install appium-adb@2.7.0 from appium installed repo.

jeangb · 2016-12-06T09:22:20Z

Apart downgrading to appium-adb@2.7.0, if it doesn't work, is there an other workaround while waiting the hotfixe ?

sravanmedarapu · 2016-12-06T09:26:29Z

@jeangb, I am working on this issue. Will update here once issue is fixed.

Downgrading to appium-ad@2.7.0 should work as the issue reported introduced in v2.9.0.

jeangb · 2016-12-06T09:28:44Z

@sravanmedarapu, Thank you very much for your quick feedback.

z00sts · 2016-12-06T09:44:11Z

Same.
Ubuntu 14.04x64, appium 1.6.1
Downgrading to appium-adb@2.7.0 helps.
Any ideas why appium-adb 2.8+ is not working with appium@1.6+?

vikramvi · 2016-12-06T11:43:00Z

+1

https://gist.github.com/vikramvi/2717dbd538e23515c406fd6b4703ed29

vikramvi · 2016-12-06T11:43:17Z

@jlipps can we please have a hot fix release for this

saikrishna321 · 2016-12-06T11:52:42Z

@vikramvi this issue has been picked by @sravanmedarapu and he is working on it ..

vikramvi · 2016-12-06T11:57:06Z

Workaround for now as below

Goto directory /usr/local/lib/node_modules/appium
and run below command
npm install appium-adb@2.7.0

After this npm -g ls , shows updated appium-adb@2.7.0 from appium-adb@2.9.0

steveyoungqa · 2016-12-06T14:21:46Z

I can confirm that after struggling with this issue all weekend installing on the latest Macbook Pro that the above workaround works perfect!

upadhyaynidhi · 2016-12-06T18:08:13Z

@vikramvi ran appium and
Getting such errors after Goto directory /usr/local/lib/node_modules/appium
and run below command
npm install appium-adb@2.7.0

Error: Cannot find module 'babel-runtime/helpers/sliced-to-array'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:289:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/appium/build/lib/main.js:7:22)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Function.Module.runMain (module.js:457:10)

chenyu-wang · 2016-12-07T06:06:30Z

Same issue happened for me, I downgraded appium to 1.6.1 it works again.
Have any one tried the 1.6.3 version of appium, just want to check if it is fixed or not

sravanmedarapu · 2016-12-07T06:12:51Z

@chenyu22 Issue is fixed in apapium-adb@2.9.1

jibingli · 2016-12-07T06:41:47Z

No compatible version found: appium@1.6.3, build failed?

sravanmedarapu · 2016-12-07T06:57:31Z

appium@1.6.3 is not released yet.

cnpallares · 2016-12-07T14:02:11Z

+1 @vikramvi solution!

davidrova · 2016-12-07T15:46:50Z

I have the same issue with appium 1.6.2.

I have tried with appium-adb from 1.6.19 to latest with no sucess.

Any workaround? It is blocker.

Would the workaround be change manifest from android project?

I have several manifest files with the targetSdkVersion parameter, so I don't know where appium-adb is looking for this parameter. Which file path is opening?

sravanmedarapu · 2016-12-07T16:02:04Z

@davidrova, Issue is fixed in appium-adb@v2.9.1.

davidrova · 2016-12-07T17:05:16Z

Hi @sravanmedarapu,

I have checked that version. The exception still is thrown but it is true the application starts.

I still don't know which AndroidManifest.xml is appium-adb looking for because in our proyect it exists.

What we have checked is that in the apk it is cypher, but adb should decode it, isn't it?

If you need more info, let me know.

Regards,

PD. For the stakeholders: remember to restart appium after upgrade appium-adb.

sravanmedarapu · 2016-12-07T17:25:57Z

@davidrova, This implementation is as part of granting permissions to the AUT. but for granting the permissions we are relaying on device API (API >= 23) and targetSdkVersion from the AUT (targetSdkVersion >= 23).

We are relying on aapt dump badging APK command's result for fetching the targetSdkVersion. if the targetSdkVersion < 23, we are just skipping the permissions granting.

But there are cases where we don't find targetSdkVersion in the dump result and in such case we are throwing the exception and ignoring the execution to continue with.

vlaquest · 2016-12-08T13:44:33Z

Hi,
using 1.6.2 on windows. Just upgraded appium-adb to 2.9.1 but I still have the error.
Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null
And I get an internal error (http 500) so my test is failing, appium stops processing.
Just checked adb version : Android Debug Bridge version 1.0.36
Revision 302830efc153-android
This is blocking me :(

sravanmedarapu · 2016-12-08T13:54:18Z

@vincentlabatut, seems updating appium-adb to 2.9.1 was not successful. Can you please cross check(version in appium\node-modules\appium-adb\package.json).

Just to conform error message you have shared is related to 2.9.0, error message is changed in 2.9.1.

execute npm install appium-adb@2.9.1 from appium repo.

nrazvan87 · 2016-12-08T14:55:10Z

I've tried all solutions presented above but didn't work for me :(
I've installed then npm install appium-adb@1.6.0 and everything started to work smoothly.

Thanks for the tips, It was a good starting point!

vlaquest · 2016-12-08T16:02:46Z

Thanks ! Just did that : workaround for 1.6.2 is reverting to 1.6.0
it works again :)

sravanmedarapu · 2016-12-09T03:17:20Z

Issue is fixed in appium-adb v2.9.1

vlaquest · 2016-12-09T08:31:41Z

Hi, I was just saying that I installed appium-adb to 2.9.1 and the issue was still there...

jeangb · 2016-12-09T08:42:03Z

Yes me to, I guess the appium-adb 2.9.1 install didn't work.

vlaquest · 2016-12-09T09:34:34Z

Got it! My fault. I did not install appium-adb correctly because we need to upgrade the appium-adb module that is inside the node_modules of the node_modules/appium folder.
so just saying npm install appium-adb@2.9.1 is not sufficient. You have to do that from the node_modules\appium folder in order to upgrade the appium-adb that is where appium will find it.
We are not all nodejs expert (at least I am not), but now it looks obvious to me.

Result is that it is working :)

The error is displayed
[ADB] Error: fetching targetSdkVersion from local APK failed. Original error: targetSdkVersion is not specified in the application.
(with the full stack trace)
[ADB] Ran into problem getting target SDK version; ignoring...

And all is working...

z00sts · 2016-12-09T09:36:52Z

@vincentlabatut Yep, nodejs local installation always confusing. @jeangb check that you upgrading appium-adb in your appium/node_modules

jeangb · 2016-12-12T16:30:43Z

Yes it was because I was doing "npm install appium-adb@2.9.1" from $home...
I thought it will be installed in the right folder since the first time I installed appium with npm, it was installed in a custom folder and not in $home.
So yes, it's working with appium-adb 2.9.1, thanks.

srkannan · 2016-12-12T21:19:11Z

I did npm install -g appium-adb@2.9.1 in /usr/local/lib/node_modules/appium
But I still have the issue. I'm using Appium version 1.6.2

saikrishna321 · 2016-12-13T03:48:23Z

@srkannan please upgrade appium version to 1.6.3 , thats got the fix

srkannan · 2016-12-13T18:51:32Z

Upgrading to appium version 1.6.3 helped, Thanks.

hiran47 · 2017-02-02T12:47:33Z

Goto directory /usr/local/lib/node_modules/appium
and run below command
npm install appium-adb@2.7.0

This has worked for me as well.
OS X 10.12.3
Appium 1.6.2

lock · 2019-04-29T08:38:18Z

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

triager added the Needs Triage bugs which are not yet confirmed label Dec 3, 2016

sravanmedarapu mentioned this issue Dec 3, 2016

refactored targetSdkVersionFromManifest appium/appium-adb#187

Merged

sravanmedarapu closed this as completed Dec 9, 2016

jlipps added this to the Optimus Prime [Sprint 3] milestone Dec 9, 2016

jlipps added Android related to Android-native driver(s) Bug a problem that needs fixing and removed Needs Triage bugs which are not yet confirmed labels Dec 9, 2016

lock bot locked and limited conversation to collaborators Apr 29, 2019

Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null #7353

Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null #7353

Comments

jhwing commented Dec 3, 2016

joodies commented Dec 3, 2016 • edited Loading

sankleta commented Dec 3, 2016

sravanmedarapu commented Dec 3, 2016

chanisasuw commented Dec 3, 2016

sravanmedarapu commented Dec 3, 2016

mykola-mokhnach commented Dec 3, 2016

chanisasuw commented Dec 3, 2016 • edited Loading

joodies commented Dec 5, 2016

jeangb commented Dec 5, 2016

devin-joubran-moovel commented Dec 5, 2016

Rdexmah commented Dec 5, 2016

cavanpage commented Dec 6, 2016

lilfry14 commented Dec 6, 2016

viveksinghtt commented Dec 6, 2016 • edited Loading

sravanmedarapu commented Dec 6, 2016

jeangb commented Dec 6, 2016

sravanmedarapu commented Dec 6, 2016 • edited Loading

jeangb commented Dec 6, 2016

z00sts commented Dec 6, 2016 • edited Loading

vikramvi commented Dec 6, 2016

vikramvi commented Dec 6, 2016

saikrishna321 commented Dec 6, 2016

vikramvi commented Dec 6, 2016

steveyoungqa commented Dec 6, 2016

upadhyaynidhi commented Dec 6, 2016 • edited Loading

chenyu-wang commented Dec 7, 2016

sravanmedarapu commented Dec 7, 2016

jibingli commented Dec 7, 2016

sravanmedarapu commented Dec 7, 2016

cnpallares commented Dec 7, 2016

davidrova commented Dec 7, 2016

sravanmedarapu commented Dec 7, 2016

davidrova commented Dec 7, 2016

sravanmedarapu commented Dec 7, 2016

vlaquest commented Dec 8, 2016

sravanmedarapu commented Dec 8, 2016

nrazvan87 commented Dec 8, 2016

vlaquest commented Dec 8, 2016

sravanmedarapu commented Dec 9, 2016

vlaquest commented Dec 9, 2016

jeangb commented Dec 9, 2016

vlaquest commented Dec 9, 2016

z00sts commented Dec 9, 2016

jeangb commented Dec 12, 2016

srkannan commented Dec 12, 2016

saikrishna321 commented Dec 13, 2016

srkannan commented Dec 13, 2016

hiran47 commented Feb 2, 2017

lock bot commented Apr 29, 2019

joodies commented Dec 3, 2016 •

edited

Loading

chanisasuw commented Dec 3, 2016 •

edited

Loading

viveksinghtt commented Dec 6, 2016 •

edited

Loading

sravanmedarapu commented Dec 6, 2016 •

edited

Loading

z00sts commented Dec 6, 2016 •

edited

Loading

upadhyaynidhi commented Dec 6, 2016 •

edited

Loading