We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is simply because every time you launch, the app's Documents directory changes.
More info: https://stackoverflow.com/questions/47864143/document-directory-path-change-when-rebuild-application
Since we store the full absolute paths in Recents in the ini file, they won't match, so won't work.
For now, I think I'll try to detect if it's a Documents directory, and patch in the current Documents path.
I wonder if we have more cases of absolute filenames being stored like that... probably:
For Recents, I'll just patch up any Documents paths on load, since it's easy to know what they should be.
For a more general solution, there seems to be something called Bookmarks: https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/AccessingFilesandDirectories/AccessingFilesandDirectories.html#//apple_ref/doc/uid/TP40010672-CH3
Should look into that, may be relevant for some cases.
The text was updated successfully, but these errors were encountered:
Documents path won't change "every time" but do change when upgrade apps/etc. So basiclly should still do that.
Sorry, something went wrong.
iOS: Update recents paths on load
606a895
Fixes the main part of #19211
Successfully merging a pull request may close this issue.
This is simply because every time you launch, the app's Documents directory changes.
More info: https://stackoverflow.com/questions/47864143/document-directory-path-change-when-rebuild-application
Since we store the full absolute paths in Recents in the ini file, they won't match, so won't work.
For now, I think I'll try to detect if it's a Documents directory, and patch in the current Documents path.
I wonder if we have more cases of absolute filenames being stored like that... probably:
Features affected by this
Workarounds
For Recents, I'll just patch up any Documents paths on load, since it's easy to know what they should be.
For a more general solution, there seems to be something called Bookmarks: https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/AccessingFilesandDirectories/AccessingFilesandDirectories.html#//apple_ref/doc/uid/TP40010672-CH3
Should look into that, may be relevant for some cases.
The text was updated successfully, but these errors were encountered: