-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Encountered internal error running command: Error: targetSdkVersionFromManifest failed. Original error: Cannot read property '1' of null #7353
Comments
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. |
#7349 The same here |
Seems something broken with appium-adb v2.9.0, Please downgrade appium-adb to v2.7.0 as a temporary work around. |
same me via window 7 |
@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 |
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 |
@sravanmedarapu Thank you so much for working this issue, It didn't work for me. Now i cannot do anything about test |
tried finally it's working now.. |
Hi, this workaround "npm install appium-adb@2.7.0" didn't change a thing neither. |
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 |
Hey I am also facing same issue with ios10.0.1 and with latest appium 1.6.2 beta.. |
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. 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. |
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. |
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? |
@viveksinghtt, Can you please execute |
Apart downgrading to appium-adb@2.7.0, if it doesn't work, is there an other workaround while waiting the hotfixe ? |
@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. |
@sravanmedarapu, Thank you very much for your quick feedback. |
Same. |
@jlipps can we please have a hot fix release for this |
@vikramvi this issue has been picked by @sravanmedarapu and he is working on it .. |
Workaround for now as below Goto directory /usr/local/lib/node_modules/appium After this npm -g ls , shows updated appium-adb@2.7.0 from appium-adb@2.9.0 |
I can confirm that after struggling with this issue all weekend installing on the latest Macbook Pro that the above workaround works perfect! |
@vikramvi ran appium and
|
Same issue happened for me, I downgraded appium to 1.6.1 it works again. |
@chenyu22 Issue is fixed in apapium-adb@2.9.1 |
No compatible version found: appium@1.6.3, build failed? |
appium@1.6.3 is not released yet. |
+1 @vikramvi solution! |
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? |
@davidrova, Issue is fixed in appium-adb@v2.9.1. |
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. |
@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 We are relying on But there are cases where we don't find |
Hi, |
@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 |
I've tried all solutions presented above but didn't work for me :( Thanks for the tips, It was a good starting point! |
Thanks ! Just did that : workaround for 1.6.2 is reverting to 1.6.0 |
Issue is fixed in appium-adb v2.9.1 |
Hi, I was just saying that I installed appium-adb to 2.9.1 and the issue was still there... |
Yes me to, I guess the appium-adb 2.9.1 install didn't work. |
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. Result is that it is working :) The error is displayed And all is working... |
@vincentlabatut Yep, nodejs local installation always confusing. @jeangb check that you upgrading appium-adb in your appium/node_modules |
Yes it was because I was doing "npm install appium-adb@2.9.1" from $home... |
I did npm install -g appium-adb@2.9.1 in /usr/local/lib/node_modules/appium |
@srkannan please upgrade appium version to 1.6.3 , thats got the fix |
Upgrading to appium version 1.6.3 helped, Thanks. |
This has worked for me as well. |
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. |
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: