Large mutation breaks the cache

[paulsUsername]

Summary

Replication:
Perform a mutation that is large, perhaps 1-2mb, but make sure you do not set publishResultToStore to false. If you run this you will stop getting any responses from the Apollo as the cache (seemingly) is in a broken state.

Resolution:
You have to set publishResultToStore to false for these large mutations otherwise the SDK breaks.

SDK version min 1.14 but also easily replicated in 1.23.

Version

1.23

Steps to reproduce the behavior

Perform a mutation that is large, perhaps 1-2mb, but make sure you do not set publishResultToStore to false. If you run this you will stop getting any responses from the Apollo as the cache (seemingly) is in a broken state.

Logs

Anything else?

No response

[calvincestari]

HI @paulsUsername, thanks for raising this issue. Can you please provide a sample app demonstrating the bug. It doesn't have to necessarily be your schema or operation but a working sample that demonstrates the problem so we can debug it.

[AnthonyMDev]

I'm closing this issue due to inactivity. If this is still unresolved, feel free to provide more information and we can re-open this, or create a new issue.

[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.