-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
Apparent caching issue with Array of Custom Objects stored in Custom Object #518
Comments
Thanks for the detailed report. This may be related to mutable containers, see #102. That feature is getting removed in the next release of the SDK. I'll investigate further however, and see if I can't figure this one out. |
Thanks @richardjrossiii , even a workaround would be great. |
Confirmed that this no longer happens with the mutable containers fix in place. As a workaround until the next SDK release is out, please ensure that using latest master fixes this for you. If it doesn't work, feel free to reopen the issue with any more info you can find. Thanks for the concise, reproducible report & sample project too! |
Thanks @richardjrossiii , I'm back now after falling down a rabbit hole of disabling System Integrity Protection so I could install bundle so I could compile the framework so I could test the framework compiled from the master branch in my test code, and it works! When integrating it with my actual project I found apparent incompatibilities between the Parse framework and ParseFacebookUtilsV4 - it was trying to |
@craiggrummitt Yup, that solution works great. Current master of ParseFacebookUtilsV4 has it removed, so it's no longer needed and removal will be included in the next release. |
Great! Thanks for the reply @nlutsenko |
There seems to be some sort of caching issue with an Array of Custom Objects. I have included a link to a bare bones example of this problem. Let me describe the bare bones app, then the issue:
App:
Simple chat app with one channel, only functionality is displaying all messages, and add message. I have a custom class 'Message' and 'Chat' (which stores an array of Messages). Messages are displayed in a UITableView, and there is a button to 'reload' the chat using a query. The query uses 'includeKey' to ensure that the messages array is included. When the app starts up, if no chat exists, it creates one with a blank messages array.
The only changes to this app from the Parse Starter Project are: Chat.swift, Message.swift, AppDelegate.swift(to set the application id and register subclasses), ViewController.swift and the storyboard.
Problem:
The query seems to retrieve cached data (i.e. it doesn't update with updates in the data).
From my testing, the device that generates the 'Chat' object initially does not present this problem. However, the device that did not initially generate the 'Chat' object, does present this problem.
Steps to produce this problem:
Additional diagnostic notes:
In my actual app I had implemented a limit of 20 messages, and after that the first message was deleted. I noticed that after I started deleting messages, that this apparent caching problem stopped occurring.
The text was updated successfully, but these errors were encountered: