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

Added support for custom default directory to sync CreamAssets #194

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

EricWiener
Copy link

Added a static property to CreamAsset to allow changing the default directory to save CreamAssets too. This is needed if you want to use App Groups and need to use the shared directory instead of the default documents directory. Fully backward compatible and added usage to the README.

@EricWiener EricWiener changed the title Added support for custom default to sync CreamAssets Added support for custom default directory to sync CreamAssets Apr 1, 2020
@EricWiener EricWiener closed this Apr 2, 2020
@EricWiener EricWiener reopened this Apr 2, 2020
@EricWiener
Copy link
Author

Sorry please ignore the closing and re-opening ^

Added a static property creamAssetURL to CreamAsset that lets the user
specify the directory that they want to store CreamAssets in.

creamAssetDefaultURL will default to using creamAssetURL if specified.
If it is not specified, it will behave as usual (backwards compatible).
Added example showing where to specify the directory to use and discussed the reasons why you would want to do this, namely App Groups.
Previous modification returned the user specified URL right away without using file manager to make sure that all intermediate directories existed. Modified this to use the user specified URL if it existed, but to also make sure that this was a valid path.
…d primary key

Bug: the app would crash if a primary key was used that had an emoji in it.
This was an issue for my app because the app accidentally used an emoji in
a primary key if the user chose to include an emoji in the title of something.
Fix: removed all emojis from the primary key if they existed. This was enough
to allow me to remove the error when saving primary keys and allow existing
users to continue to use their iCloud without resetting their cached data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants