-
Notifications
You must be signed in to change notification settings - Fork 267
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
Not being able to debug due to adb path being incorrect #781
Comments
Exact same error here |
#777 (comment) @macaetano check this out, it worked for me |
Thx @Sterlingryan, that worked for me too. |
@macaetano thanks for reaching us. Please, try updating to v0.6.16, versions v0.6.14-v0.6.15 are broken. |
V0.6.16 fixed that, thank you @ruslan-bikkinin that was very fast |
The latest update (0.6.17) produced a similar error as mentioned in this issue : [Error] Error: Error while executing command 'F:\Programs\Android\sdk\platform-tools\adb devices': Command failed: F:\Programs\Android\sdk\platform-tools\adb devices |
@Sterlingryan could you please copy-paste output of |
React-Native: Run Android [Info] Using Android SDK location defined in android/local.properties file: F:\Programs\Android\sdk. [Info] Starting React Native Packager. Scanning folders for symlinks in f:\GitHub\React Native Projects\RentProfileAgents\node_modules (67ms) BUILD SUCCESSFUL in 4s
|
It runs fine if I downgrade the extension to 0.6.13 |
@Sterlingryan, version 0.6.16 also seems to work fine. |
Yep you're right |
Hey guys, I confirm that this is a bug that impact users on Windows targeting android apps, and I am working on a fix now. As workaround, you can comment |
Actual Behavior
The filename, directory name, or volume label syntax is incorrect.
Expected Behavior
Software versions
Outputs (Include if relevant)
Thoughts
I can see that there is an extra '\' character between 'F' and ':', but for the life of me I cannot find where to go to fix it. I tried changing the environment variable for adb but it did not work.
The text was updated successfully, but these errors were encountered: