Draft
Conversation
Upgrade SDK to Android 33, port to shared file storage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade SDK to Android 33, port to the shared file storage dance.
This is a bit messy still, and I've moved the saves, game copies etc to the ExternalFilesDir, which is less easy to read/access using normal Android file apps - its now /Android/data.de.onyxbits.textfiction
There is a way to make it be the truely public accessible directory, "just" need to ask the user to choose that dir, and then remember that we asked about it (persist permissions)
This won't build to a target SDK later than 33, as of course some other stuff has been deprecated since that one as well..