- ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information) #7686
- Comments
- vikramvi commented Jan 12, 2017
- The problem
- Environment
- Details
- Link to Appium logs
- Code To Reproduce Issue [ Good To Have ]
- Launch Android SDK manager — Tools directory doesn’t exist? Mac
- 8 Answers 8
- After using android studio 3.1.2 it showing error=2, No such file or directory
- ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information) #7686
- Comments
- vikramvi commented Jan 12, 2017
- The problem
- Environment
- Details
- Link to Appium logs
- Code To Reproduce Issue [ Good To Have ]
ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information) #7686
Comments
vikramvi commented Jan 12, 2017
The problem
While trying to run script on appiun native app getting below error ( appium is registered as node on a selenium grid )
(An unknown server-side error occurred while processing the command. Original error: ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information)
Environment
- Appium version (or git revision) that exhibits the issue: 1.6.3
- Last Appium version that did not exhibit the issue (if applicable): NA
- Desktop OS/version used to run Appium: Mac 10.11.6
- Node.js version (unless using Appium.app|exe): 7.2.1
- Mobile platform/version under test:
- Real device or emulator/simulator:
- Appium CLI or Appium.app|exe:
Details
Registered appium node with below code
AppiumDriverLocalService driverLocalService1 = AppiumDriverLocalService
.buildService(new AppiumServiceBuilder()
.withAppiumJS(new File(«/usr/local/lib/node_modules/appium/build/lib/main.js»))
.usingDriverExecutable(new File(«/usr/local/bin/node»))
.usingPort(4723)
.withArgument(AndroidServerFlag.BOOTSTRAP_PORT_NUMBER,»4724″)
.withArgument(GeneralServerFlag.SESSION_OVERRIDE)
.withArgument(GeneralServerFlag.LOG_LEVEL, «debug»)
.withArgument(GeneralServerFlag.CONFIGURATION_FILE, nodeConfigFilePath)
.withCapabilities(new DesiredCapabilities(ImmutableMap.of(MobileCapabilityType.UDID, «000007CF003ACABB»))));
driverLocalService1.start();
env variable setup
export ANDROID_HOME=/Users/vikram-anna/Library/Android/sdk
export PATH=$ANDROID_HOME/platform-tools:$PATH
export PATH=$ANDROID_HOME/tools:$PATH
Link to Appium logs
FAILED TO CREATE NEW WEBDRIVER_DRIVER INSTANCE class io.appium.java_client.AppiumDriver: Could not instantiate new WebDriver instance of type class io.appium.java_client.AppiumDriver (An unknown server-side error occurred while processing the command. Original error: ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information)
Code To Reproduce Issue [ Good To Have ]
Please remember that, with sample code; it’s easier to reproduce bug and much faster to fix it.
Please git clone https://github.com/appium/sample-code and use one of your favourite languages and sample apps to reproduce issue.
In case a similar scenario is missing in sample-code, please submit a PR with one of the sample apps provided.
The text was updated successfully, but these errors were encountered:
Источник
Launch Android SDK manager — Tools directory doesn’t exist? Mac
I’m on mac, I think I’ve done everything right so far. following these instructions: http://developer.android.com/sdk/installing/adding-packages.html
it says to navigate to tools/ directory in terminal. Here are my steps.
cd Applications result is: No such file or directory
path to my tools directory is as follows
I tried putting my folder onto my desktop, both the tools folder, and my adt-bundle because I could change directory to my desktop, and when I enter ls to the terminal I see my tools folder, and my adt-bundle is there,
but the problem is when I try to enter
it says that it is not a directory.
8 Answers 8
Go to this directory:
I recently encountered this issue, and figured I’d post on this for clarification or for anyone still encountering it.
It seems you have to be at the root of the /adt-bundle-mac-VERSION/sdk directory in order to execute the «android» command. I normally cd into the directory until I reach the location of the command, but in this case I encountered the same issue as the original poster.
You must use the tab key to the android command. ie.
locate your installation /adt-bundle-mac-x86_64-20131030/sdk hit TAB key /tools hit TAB key /android
instead of cd adt-bundle-mac-x86_64-20131030/ cd/sdk cd/tools android
If done properly the SDK manager should launch for you.
Hope this helps anybody out there.
You can launch the SDK Manager by using the GUI:
- Launch Android Studio
- Create a new blank project
- In the toolbar, look for the icon with tooltip «SDK Manager»
Use cd /users/user/. your path. /android-sdk/tools
A lot of answers have been given here that you should go to /
For me, this did not work. When I opened the android file located at my /
So the right approach now, is as stated by @Shijil in his comment.
In the directory for your android sdk, you should use:
For SDK Manager:
For AVD Manager:
NB For the last command in each of the options above, you will have to supply additional args depending on the operation you want to perform. An example arg that works for both is —list . Running the commands without any args will only display the possible args you could have passed.
Personally, I think using the GUI in android studio is easier. Especially for linux beginners.
Источник
After using android studio 3.1.2 it showing error=2, No such file or directory
After installing Ubuntu 18 in new desktop with i7 and 24gb ram . We try to move our android studio project to new pc in zip format and our project work fine on old pc but it showing error on new pc .
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ‘:app:transformNativeLibsWithStripDebugSymbolForDebug’. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:63) at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88) at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:124) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:80) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:105) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:99) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.lang.Thread.run(Thread.java:745) Caused by: org.gradle.process.internal.ExecException: A problem occurred starting process ‘command ‘/home/developer/Android/Sdk/ndk-bundle/toolchains/mips64el-linux-android-4.9/prebuilt/linux-x86_64/bin/mips64el-linux-android-strip» at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:220) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:204) at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:340) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:86) at org.gradle.internal.operations.BuildOperationIdentifierPreservingRunnable.run(BuildOperationIdentifierPreservingRunnable.java:39) . 6 more Caused by: net.rubygrapefruit.platform.NativeException: Could not start ‘/home/developer/Android/Sdk/ndk-bundle/toolchains/mips64el-linux-android-4.9/prebuilt/linux-x86_64/bin/mips64el-linux-android-strip’ at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:27) at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start(WrapperProcessLauncher.java:36) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:68) . 7 more Caused by: java.io.IOException: Cannot run program «/home/developer/Android/Sdk/ndk-bundle/toolchains/mips64el-linux-android-4.9/prebuilt/linux-x86_64/bin/mips64el-linux-android-strip» (in directory «/home/developer/Documents/working_app/valyangadi_firebase_project/app»): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:25) . 9 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) . 10 more
What is this errors and How to solve this problem? This project works fine on my old laptop Ubuntu 14.04 LTS that using android studio 3.0
Источник
ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information) #7686
Comments
vikramvi commented Jan 12, 2017
The problem
While trying to run script on appiun native app getting below error ( appium is registered as node on a selenium grid )
(An unknown server-side error occurred while processing the command. Original error: ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information)
Environment
- Appium version (or git revision) that exhibits the issue: 1.6.3
- Last Appium version that did not exhibit the issue (if applicable): NA
- Desktop OS/version used to run Appium: Mac 10.11.6
- Node.js version (unless using Appium.app|exe): 7.2.1
- Mobile platform/version under test:
- Real device or emulator/simulator:
- Appium CLI or Appium.app|exe:
Details
Registered appium node with below code
AppiumDriverLocalService driverLocalService1 = AppiumDriverLocalService
.buildService(new AppiumServiceBuilder()
.withAppiumJS(new File(«/usr/local/lib/node_modules/appium/build/lib/main.js»))
.usingDriverExecutable(new File(«/usr/local/bin/node»))
.usingPort(4723)
.withArgument(AndroidServerFlag.BOOTSTRAP_PORT_NUMBER,»4724″)
.withArgument(GeneralServerFlag.SESSION_OVERRIDE)
.withArgument(GeneralServerFlag.LOG_LEVEL, «debug»)
.withArgument(GeneralServerFlag.CONFIGURATION_FILE, nodeConfigFilePath)
.withCapabilities(new DesiredCapabilities(ImmutableMap.of(MobileCapabilityType.UDID, «000007CF003ACABB»))));
driverLocalService1.start();
env variable setup
export ANDROID_HOME=/Users/vikram-anna/Library/Android/sdk
export PATH=$ANDROID_HOME/platform-tools:$PATH
export PATH=$ANDROID_HOME/tools:$PATH
Link to Appium logs
FAILED TO CREATE NEW WEBDRIVER_DRIVER INSTANCE class io.appium.java_client.AppiumDriver: Could not instantiate new WebDriver instance of type class io.appium.java_client.AppiumDriver (An unknown server-side error occurred while processing the command. Original error: ENOENT: no such file or directory, scandir ‘/Users/vikram-anna/Library/Android/sdk/platform-tools/build-tools’ (WARNING: The server did not provide any stacktrace information)
Code To Reproduce Issue [ Good To Have ]
Please remember that, with sample code; it’s easier to reproduce bug and much faster to fix it.
Please git clone https://github.com/appium/sample-code and use one of your favourite languages and sample apps to reproduce issue.
In case a similar scenario is missing in sample-code, please submit a PR with one of the sample apps provided.
The text was updated successfully, but these errors were encountered:
Источник
