- Android FileSystem unable to read files and cache directories #767
- Comments
- sameesiddiqui commented Oct 11, 2017
- alexrussell commented Oct 12, 2017
- nikki93 commented Oct 12, 2017
- nikki93 commented Oct 12, 2017
- sameesiddiqui commented Oct 12, 2017
- sameesiddiqui commented Oct 12, 2017
- alexrussell commented Oct 13, 2017
- nikki93 commented Oct 13, 2017
- nikki93 commented Oct 13, 2017
- sameesiddiqui commented Oct 13, 2017
- nikki93 commented Oct 16, 2017
- kaulsalil88 commented Feb 2, 2018 •
- «Unable to read profile . The system cannot find the file specified» for adb.exe when attempting to complete profiling with FinishAotProfiling #4152
- Comments
- brendanzagaeski commented Jan 21, 2020
- Steps to reproduce
- Expected behavior
- Actual behavior
- Version information
- Log files
- ysmoradi commented Feb 23, 2020
- brendanzagaeski commented Mar 16, 2020
- Workaround
- Additional notes
- AleksandrAlekseev commented Mar 24, 2020
- brendanzagaeski commented Mar 28, 2020
- Workaround for macOS
- MathieuJack commented Apr 11, 2020
- brendanzagaeski commented Apr 11, 2020
- «Unable to read profile . The system cannot find the file specified» for adb.exe when attempting to complete profiling with FinishAotProfiling #4152
- Comments
- brendanzagaeski commented Jan 21, 2020
- Steps to reproduce
- Expected behavior
- Actual behavior
- Version information
- Log files
- ysmoradi commented Feb 23, 2020
- brendanzagaeski commented Mar 16, 2020
- Workaround
- Additional notes
- AleksandrAlekseev commented Mar 24, 2020
- brendanzagaeski commented Mar 28, 2020
- Workaround for macOS
- MathieuJack commented Apr 11, 2020
- brendanzagaeski commented Apr 11, 2020
Android FileSystem unable to read files and cache directories #767
Comments
sameesiddiqui commented Oct 11, 2017
Attempting to perform actions such as reading files from FileSystem.documentDirectory and FileSystem.cacheDirectory throws errors for invalid file uri on android. Reading from these directories works on iOS.
Reading from a child directory also works, just not these top level ones:
The text was updated successfully, but these errors were encountered:
alexrussell commented Oct 12, 2017
This is a dupe of #716, so one of these should really be closed. This one provides the correct context and description of the issue in the issue description, so I say close #716.
nikki93 commented Oct 12, 2017
@sameesiddiqui you mean just reading the file list ( readDirectoryAsync ) of those root directories right? Are you able to readAsString the contents of a file at the top level? (just checking)
nikki93 commented Oct 12, 2017
@sameesiddiqui does this work if you add / to the end of the directory path?
sameesiddiqui commented Oct 12, 2017
Yes, reading a file under the directory works:
But trying to do any task with the top directories fails, not just readDirectory:
Also tried appending / to the end of the path, but no dice. Looks like the path already has a trailing slash
sameesiddiqui commented Oct 12, 2017
dependencies in case you are wondering:
alexrussell commented Oct 13, 2017
If this is about readDirectoryAsync on the root of the filesystem and #716 is about files in the root of the filesystem maybe I’m wrong about the dupe (though #716 is specifically about using createDownloadResumable , which may perform a directory read, and therefore be back in dupesville).
nikki93 commented Oct 13, 2017
This is a little tricky since we want to be able to read and write under but not delete the root directory itself in each case. 🤔 Tracking a new issue to granularlize FS permissions here: #776 This will also allow stuff like copying from RN’s CameraRoll -> Expo FS.
nikki93 commented Oct 13, 2017
Let me know if you think that other issue sufficiently covers this case, I will also try to solve this issue while getting at that one. Then we can close this one and just track that. As a workaround for now @sameesiddiqui you can just create a subdirectory inside the root and create and list your files in that.
sameesiddiqui commented Oct 13, 2017
Interesting, on iOS there are permissions to delete these root directories. Just tested by deleting FileSystem.documentDirectory (throws no error) and tried to read it’s contents, which then tells me the directory doesn’t exist. Is this unintended behavior on iOS?
My understanding right now is that iOS root directories have r/w and Android root directories have neither. Is the end goal to make both have only read?
nikki93 commented Oct 16, 2017
I guess it’s a little weird @sameesiddiqui since they need to be not deleteable but they do need to be writeable (create new entries under) and definitely readable (list entries). I guess deletion requires write access on both the file and its parent directory (since the listing of the parent directory is being changed), in which case the conditions work out (since the parent of root is not read or writeable). Anyways, let’s track this discussion on #776 now since I think we can tackle this issue as part of that. Closing this to unify discussion, feel free to comment here though if something makes sense to be said here.
kaulsalil88 commented Feb 2, 2018 •
i know this is very late in the day but i have the following configuration in my package.json
«expo»: «^21.0.0»,
«expo-env»: «^1.1.0»,
«react»: «16.0.0-alpha.12»,
«react-native»: «https://github.com/expo/react-native/archive/sdk-21.0.2.tar.gz»,
. On android I need to create a sub folder and able to use both downloadAsync and createDownloadResumable . On IOS when using createDownloadResumable i am getting the following error on ios :
[EXFileSystem _downloadResumableCreateSessionWithUrl:withScopedPath:withUUID:withOptions:withResumeData:withResolver:withRejecter:]_block_invoke.298 + 418′,
‘3 hcl-concerts 0x000000010186d5cb -[EXDownloadDelegate URLSession:downloadTask:didFinishDownloadingToURL:] + 155’,
‘4 CFNetwork 0x000000010c0d20b2 __82-[NSURLSession delegate_downloadTask:didFinishDownloadingToURL:completionHandler:]_block_invoke + 38’,
Do I need to upgrade my expo version , want to avoid that as the release date is very close . I am not able to understand what is causing this issue .Please help .
Have created an issue here
#1405 .
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
«Unable to read profile . The system cannot find the file specified» for adb.exe when attempting to complete profiling with FinishAotProfiling #4152
Comments
brendanzagaeski commented Jan 21, 2020
Steps to reproduce
Create a new Android Single View App project.
Open Tools > Command Line > Developer Command Prompt.
Ensure that a target Android device is attached.
Run the following command in the solution directory:
After the app launches successfully, run the following command:
Expected behavior
The FinishAotProfiling target completes successfully.
Actual behavior
The FinishAotProfiling target fails:
Perhaps of interest, the adb logcat output seems to indicate that profiling started successfully on the device:
The following command also ran successfully when I ran it by hand:
And netstat on the device seems to indicate it is indeed listening on port 9999:
Version information
- Visual Studio 2019 version 16.5 Internal Preview
- Xamarin.Android SDK 10.2.0.84 (d16-5/ac3f71f)
- Mono: df42020
- Java.Interop: xamarin/java.interop@c0cc770
- ProGuard: xamarin/proguard@905836d
- SQLite: xamarin/sqlite@46204c4
- Xamarin.Android Tools: xamarin/xamarin-android-tools@9f4ed4b
Android 9.0 (API level 28) arm64-v8a Google Pixel 3
Log files
The text was updated successfully, but these errors were encountered:
ysmoradi commented Feb 23, 2020
I’m using vs 16.5 prev 3 and there is an error as followings:
I’m running with administrator privileges and there is no firewall in the middle )-:
brendanzagaeski commented Mar 16, 2020
Workaround
I was able to work around the Unable to read profile . The system cannot find the file specified error by adding the directory containing adb.exe to the PATH environment variable in the Developer Command Prompt before running msbuild -t:FinishAotProfiling :
Additional notes
It seems that msbuild -t:FinishAotProfiling might not yet do any steps to ensure the path to adb.exe is known before aprofutil attempts to start it.
AleksandrAlekseev commented Mar 24, 2020
@brendanzagaeski Thanks for solution for Windows, it works! I tested under Parallels on Windows.
But i have build on Mac and have some error, have any solution?
brendanzagaeski commented Mar 28, 2020
Workaround for macOS
Ah yes, on macOS, the workaround would be similar. For the default install path that Visual Studio for Mac uses for adb , the workaround would be:
MathieuJack commented Apr 11, 2020
I have the same problem, on MacOS.
Changing the PATH did not work for me.
I tried : Turning off firewall, and launching command as administrator.
Here is the full output:
Projet «/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» sur le nœud 1 (FinishAotProfiling cible(s)).
_ResolveSdks:
Found Java SDK version 1.8.0.
Found Java SDK version 1.8.0.
FinishAotProfiling:
«/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»
Calling ‘adb forward tcp:9999 tcp:9999’.
Reading from ‘127.0.0.1:9999’.
Read total 0 bytes.
EXEC : error : aotprofile-tool: Unable to read profile through local port: 9999. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
System.IO.IOException: Input file is too small.
at Mono.Profiler.Aot.ProfileReader.ReadAllData (System.IO.Stream stream) [0x00028] in :0
at aotprofiletool.MainClass.ReadProfileFromPort (Mono.Profiler.Aot.ProfileReader reader) [0x0012e] in :0
at aotprofiletool.MainClass.Main (System.String[] args) [0x00048] in :0
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Application.targets(62,5): error MSB3075: La commande «»/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»» s’est arrêtée avec le code 5. Assurez-vous d’avoir les droits suffisants pour exécuter cette commande. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
Génération du projet «/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» terminée (FinishAotProfiling cible(s)) — ÉCHEC.
ÉCHEC de la build.
«/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» (FinishAotProfiling cible) (1) ->
(FinishAotProfiling cible) ->
EXEC : error : aotprofile-tool: Unable to read profile through local port: 9999. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Application.targets(62,5): error MSB3075: La commande «»/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»» s’est arrêtée avec le code 5. Assurez-vous d’avoir les droits suffisants pour exécuter cette commande. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
brendanzagaeski commented Apr 11, 2020
@MathieuJack, the error messages from this feature are a little tricky at the moment because they show several of the same lines in the output for a few different problems. In this case, the important lines from what you’re seeing are:
System.IO.IOException: Input file is too small.
That’s a different complication than this item (#4152). The messages you’re seeing can happen if the app is for some reason no longer running on the device when the FinishAotProfiling target is invoked or if the app didn’t start with the correct settings during the BuildAndStartAotProfiling target.
If you get stuck on that issue after retrying the BuildAndStartAotProfiling target, the best next step would be to submit a new issue and attach the following info so the team can take a look:
- The diagnostic MSBuild output from the BuildAndStartAotProfiling step
- The adb logcat output from the device during both the BuildAndStartAotProfiling step and the FinishAotProfiling step
Источник
«Unable to read profile . The system cannot find the file specified» for adb.exe when attempting to complete profiling with FinishAotProfiling #4152
Comments
brendanzagaeski commented Jan 21, 2020
Steps to reproduce
Create a new Android Single View App project.
Open Tools > Command Line > Developer Command Prompt.
Ensure that a target Android device is attached.
Run the following command in the solution directory:
After the app launches successfully, run the following command:
Expected behavior
The FinishAotProfiling target completes successfully.
Actual behavior
The FinishAotProfiling target fails:
Perhaps of interest, the adb logcat output seems to indicate that profiling started successfully on the device:
The following command also ran successfully when I ran it by hand:
And netstat on the device seems to indicate it is indeed listening on port 9999:
Version information
- Visual Studio 2019 version 16.5 Internal Preview
- Xamarin.Android SDK 10.2.0.84 (d16-5/ac3f71f)
- Mono: df42020
- Java.Interop: xamarin/java.interop@c0cc770
- ProGuard: xamarin/proguard@905836d
- SQLite: xamarin/sqlite@46204c4
- Xamarin.Android Tools: xamarin/xamarin-android-tools@9f4ed4b
Android 9.0 (API level 28) arm64-v8a Google Pixel 3
Log files
The text was updated successfully, but these errors were encountered:
ysmoradi commented Feb 23, 2020
I’m using vs 16.5 prev 3 and there is an error as followings:
I’m running with administrator privileges and there is no firewall in the middle )-:
brendanzagaeski commented Mar 16, 2020
Workaround
I was able to work around the Unable to read profile . The system cannot find the file specified error by adding the directory containing adb.exe to the PATH environment variable in the Developer Command Prompt before running msbuild -t:FinishAotProfiling :
Additional notes
It seems that msbuild -t:FinishAotProfiling might not yet do any steps to ensure the path to adb.exe is known before aprofutil attempts to start it.
AleksandrAlekseev commented Mar 24, 2020
@brendanzagaeski Thanks for solution for Windows, it works! I tested under Parallels on Windows.
But i have build on Mac and have some error, have any solution?
brendanzagaeski commented Mar 28, 2020
Workaround for macOS
Ah yes, on macOS, the workaround would be similar. For the default install path that Visual Studio for Mac uses for adb , the workaround would be:
MathieuJack commented Apr 11, 2020
I have the same problem, on MacOS.
Changing the PATH did not work for me.
I tried : Turning off firewall, and launching command as administrator.
Here is the full output:
Projet «/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» sur le nœud 1 (FinishAotProfiling cible(s)).
_ResolveSdks:
Found Java SDK version 1.8.0.
Found Java SDK version 1.8.0.
FinishAotProfiling:
«/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»
Calling ‘adb forward tcp:9999 tcp:9999’.
Reading from ‘127.0.0.1:9999’.
Read total 0 bytes.
EXEC : error : aotprofile-tool: Unable to read profile through local port: 9999. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
System.IO.IOException: Input file is too small.
at Mono.Profiler.Aot.ProfileReader.ReadAllData (System.IO.Stream stream) [0x00028] in :0
at aotprofiletool.MainClass.ReadProfileFromPort (Mono.Profiler.Aot.ProfileReader reader) [0x0012e] in :0
at aotprofiletool.MainClass.Main (System.String[] args) [0x00048] in :0
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Application.targets(62,5): error MSB3075: La commande «»/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»» s’est arrêtée avec le code 5. Assurez-vous d’avoir les droits suffisants pour exécuter cette commande. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
Génération du projet «/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» terminée (FinishAotProfiling cible(s)) — ÉCHEC.
ÉCHEC de la build.
«/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj» (FinishAotProfiling cible) (1) ->
(FinishAotProfiling cible) ->
EXEC : error : aotprofile-tool: Unable to read profile through local port: 9999. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Application.targets(62,5): error MSB3075: La commande «»/Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/Darwin/aprofutil» -s -v -f -p 9999 -o «custom.aprof»» s’est arrêtée avec le code 5. Assurez-vous d’avoir les droits suffisants pour exécuter cette commande. [/Users/yadusurf/Documents/KODE/GIT/YDSMobile/Yadusurf.XamarinForms.Android/Yadusurf.XamarinForms.Android.csproj]
brendanzagaeski commented Apr 11, 2020
@MathieuJack, the error messages from this feature are a little tricky at the moment because they show several of the same lines in the output for a few different problems. In this case, the important lines from what you’re seeing are:
System.IO.IOException: Input file is too small.
That’s a different complication than this item (#4152). The messages you’re seeing can happen if the app is for some reason no longer running on the device when the FinishAotProfiling target is invoked or if the app didn’t start with the correct settings during the BuildAndStartAotProfiling target.
If you get stuck on that issue after retrying the BuildAndStartAotProfiling target, the best next step would be to submit a new issue and attach the following info so the team can take a look:
- The diagnostic MSBuild output from the BuildAndStartAotProfiling step
- The adb logcat output from the device during both the BuildAndStartAotProfiling step and the FinishAotProfiling step
Источник
