Skip to content
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

[BUG] FileSaver MacCatalyst crushes when i dont have write access to the given filepath #1465

Open
2 tasks done
LocutusOfPenguin opened this issue Oct 19, 2023 · 3 comments
Open
2 tasks done
Assignees
Labels
area/essentials Issue/Discussion/PR that has to do with Essentials bug Something isn't working

Comments

@LocutusOfPenguin
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Did you read the "Reporting a bug" section on Contributing file?

Current Behavior

Start FileSaver (no special setup needed, as far i can see).
The Saver showing my HD (main) on the path. If i don't change it to f.e. my home dir, the sw crushing when i accept a choosen (upload) file.

This is esp bad, cause its the STARTup situation.

Feature: I would also like it have an option i can hand over at startup (where to start on path). btw: And to see the saver in my own language (its always in english, right now).

Expected Behavior

If no write access, give an error back. Not crush silently (i can only see a message in debug similar to "missing access rights".

Steps To Reproduce

see "Current behaviour"

Link to public reproduction project repository

see your own examples

Environment

- .NET MAUI CommunityToolkit: 6.0.0
- OS: MacCatalyst
- .NET MAUI: 8.0.0.163

Anything else?

No response

@ghost
Copy link

ghost commented Oct 20, 2023

Hi @LocutusOfPenguin. We have added the "needs reproduction" label to this issue, which indicates that we cannot take further action. This issue will be closed automatically in 5 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@ghost
Copy link

ghost commented Oct 23, 2023

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 2 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

@ghost ghost added the stale The author has not responded in over 30 days label Oct 23, 2023
@VladislavAntonyuk VladislavAntonyuk removed the stale The author has not responded in over 30 days label Oct 24, 2023
@vhugogarcia vhugogarcia added the area/essentials Issue/Discussion/PR that has to do with Essentials label Dec 7, 2023
@VladislavAntonyuk VladislavAntonyuk self-assigned this Mar 7, 2024
@TiberiusDRAIG
Copy link

TiberiusDRAIG commented May 10, 2024

Just adding my name to this as we've just bumped into it in our app, and it's blocking a feature merge. What we see is that when you don't have write-access to the destination the awaited SaveAsync method never returns, and we see something along the lines of the following in the console:

2024-05-10 16:58:44.324 MyID Client[28185:989352] Save Panel failed to move file:///var/folders/fr/c9t01l654cx4r6dx_w1t3t01v1j780/T/170a2ae1-1931-4b3d-925f-c10ef9c2e241/myIdClientErrorLog_133598303184352990.zip to file:///myIdClientErrorLog_133598303184352990.zip. Error: Error Domain=NSCocoaErrorDomain Code=642 "You can’t save the file “myIdClientErrorLog_133598303184352990.zip” because the volume “Macintosh HD” is read only." UserInfo={NSDestinationFilePath=/myIdClientErrorLog_133598303184352990.zip, NSUserStringVariant=Move, NSFilePath=/var/folders/fr/c9t01l654cx4r6dx_w1t3t01v1j780/T/170a2ae1-1931-4b3d-925f-c10ef9c2e241/myIdClientErrorLog_133598303184352990.zip, NSUnderlyingError=0x60000189b630 {Error Domain=NSCocoaErrorDomain Code=642 "You can’t save the file “myIdClientErrorLog_133598303184352990.zip” because the volume “Macintosh HD” is read only." UserInfo={NSSourceFilePathErrorKey=/var/folders/fr/c9t01l654cx4r6dx_w1t3t01v1j780/T/170a2ae1-1931-4b3d-925f-c10ef9c2e241/myIdClientErrorLog_133598303184352990

For now we're using the folder picker to set a destination then manually saving the file(s) with generated filenames, but that has its own issues which is why we were trying to move to FileSaver in the first place.

EDIT: Encountered in MCT 9.0.0. Let me know if you still need a repro.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/essentials Issue/Discussion/PR that has to do with Essentials bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants