Mutation doesn't appear to update a queried object so no changes visible in the UI until app is reloaded

[duncangroenewald]

Question

Perhaps I misunderstand how Apollo-ios is supposed to work but if I query and object and then submit a mutation to update some of its properties the original objects properties don't seem to be updated - they are in the database but they are never reflected in the UI until the application is shutdown and restarted.

Am I missing something here ? Doesn't the client side cache the objects and automatically update properties following a mutation ?

Interesting that none of the tutorials seem to show updates to an object that has been fetched and how to ensure that the updates are reflected in the UI.

Should this work and if not then what is the normal way to reflect updates in the user interface.

[AnthonyMDev]

If you want data to automatically update in the UI, you need to use a GraphQLQueryWatcher. Properties on the generated models are not updated automatically.

[duncangroenewald]

Hmm, ok I am still trying to get my head around whether there is any point or whether to just do my own client side object model with proper observable properties. It also seems strange to have to precompile each possible transaction variation - struggling to understand the use case for that. Typically I would have a client side model than knows which properties have changed and then create a dynamic transition to update just those properties. Apollo seems to require that each possible transaction variation gets predefined at compile time. Maybe I am miss understanding how it is supposed to be used.

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better.