Thread 1: Fatal error: Unexpectedly found nil while unwrapping an Optional value about aws-mobile-appsync-sdk-ios

[rohandubal]

Thanks for letting us know about this! We will update it to fail silently in this case or surface it in the error callback.

[michaeleconomy]

i tried disabling disk caching and it no longer crashes (setting databaseURL to nil in my appsyncclient).

[rohandubal]

Hi @michaeleconomy

Thanks for reporting this. I will investigate this and get back to you.

Thanks,
Rohan

[rohandubal]

I don't see anything wrong with your mutation code. Could you please show how you initialized the database for appsync client? Does switching to a new database help?

[michaeleconomy]

I switched identity pools - that might cause issues?

the database code was like this:
let databaseURL = URL(fileURLWithPath:NSTemporaryDirectory()).appendingPathComponent("appsync-local-db")

but i set the whole thing to nil and that fixed it

[rohandubal]

Setting it to nil will make the SDK use the in-memory database instead of a persistent store. The local store and cognito identity would be unrelated. One possibility is that if you are using temporary directory and the file got cleaned up by OS. You could use the NSDocumentsDirectory instead to avoid that issue.

[michaeleconomy]

Ok, I was going off of the documentation here:
https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app-ios.html

FWIW, I feel like this still shouldn't crash the application though.

I'm happy to continue to leave it set to nil (request caching isn't very worthwhile in my use case), but figured you guys would want to know about this issue.

[wallowabk]

I'm also seeing this. It is a mutation with no arguments that's causing the crash.

[frankmuellr]

@rohandubal Didn't we release a fix for this issue? If so, can you update the issue?

[palpatim]

I have a test that replicates this and am working on a fix for an upcoming release.

[palpatim]

This is released in 2.10.0