I\'m completely stuck on an Apollo problem, for which I\'ve opened a GitHub issue and had zero response on.
I\'m calling an Apollo mutation, using optimisticRespon
I was doing some digging and I think I found the source of the problem. Unfortunately, I don't have a solution.
In short, the problem might be with a network link called OfflineLink that is used by aws-appsync.
aws-appsync has an ApolloLink called OfflineLink that intervenes with the request function.
What happens is something like this:
$apollo.mutate(...)ApolloClient.QueryManager initializes the mutation that triggers your update the first time with the optimistic response. That is happening inside ApolloClient data store, markMutationInit calls markMutationResult that calls your update.OfflineLink in the network chain.OfflineLink creates a new observer and dispatches the mutation info as an action.OfflineLink calls the observer's next function with the optimisticResponse as if it was the execution result!update the second time with the result which is actually the optimisticResponse.OfflineLink calls the observer's complete which resolves your promise.console.log('done!'...Meanwhile, OfflineLink prevents the original mutation from even sending the request, and a new mutation is generated and sent with the options you've given it.