Repository navigation
Pulling a folder that contains "." in it #101
Description
Activity
@wherewhere what's so odd?
I'm trying to pull a directory,which it's name contains "."...such as in the image....Do a test with yourself....place on the main storage path a folder and call it aaa.bbb,you'll see it's buggy...
I've investigated into thePullFolderAsyncInternalfunction,and I've see there's a bug in theremotePath = LinuxPath.Combine(remotePath, stat.Path);line,where it's split the path by dots,and recognize the dot as a folder....So what? ConsoleApp.zip

Screenbits.2024-03-29_012356.2.2.mp4
@wherewhere I'm sorry,I'll be more specfic and focus the bug,in the sdcard it's indeed work,but try to pull a file from the "/sdcard/Android/data/xxxx"(any folder here-which are the external data folders for apps),you'll encouteer a bug.
I've tried to pull the outer folder,i.e "/sdcard/Android/data/",and I see it's pulling the main android root dir....This is Android promission issue. I don't know how to fix it.
@wherewhere hey bro,it's defintely nor android permission issue....because when you use this :
adb pull /sdcard/android/data/com.globile.mycontactbackup/filesin normal adb clil.... it works as charm... :(Why your markdown is so weird? The code block is not on codes...
I still have no idea, you can use adb command line by
List<string> IAdbCommandLineClient.ExecuteAdbCommand(string command)@wherewhere thanks for solution sir,how can I involve that line in my code?
How to get theIAdbCommandLineClientinterface?So why not just use
Processto invoke commands...@wherewhere cmon...please....
It's better to use
ProcessbecauseList<string> IAdbCommandLineClient.ExecuteAdbCommand(string command)set to force exit after 5s.@wherewhere thanks sir....appriciate it.
If there would be a fix in the next versions I would like to know :)



Describe the bug
The new 3.2.11 release is really good,but it's still has bugs ,such as I cannot pull a folder that it's name contains dots in it(such as common package names folders).
On any other folders it works perfect!!
Steps to reproduce the bug
pull folders
Expected behavior
No response
Screenshots
No response
NuGet package version
None
.NET Platform
No response
Platform type
No response
System version
No response
IDE
No response
Additional context
No response