Crashing on Swift 3

[johnpaulmanoza]

Hi Im having a trouble loading the keychain data. App crash when loadDataForUserAccount is called. xcode stops here Locksmith.swift (Line 84). Thank you for any help.

Locksmith 3.0.0 Xcode 8.0

[ibeleliev]

This error occurs to me too. It is happening when i use Locksmith.loadDataForUserAccount for account that was previously deleted by using Locksmith.deleteDataForUserAccount. So it tries to read from something that doesn't exist in the keychain and returns error with statusCode -25300 / Locksmith.LocksmithError notFound /.

[rlam3]

@johnpaulmanoza were you able to resolve this problem? I'm having a similar issue as well...

[johnnyoin]

I have this issue as well but the app doesn't crash. Locksmith complains about a duplicate but still does the job. I'm not saying I don't want it to be fixed though 😄

[Micke5]

Any progress on this issue? I'm having the same problem :(

[rlam3]

@johnnyoin Were you able to resolve this issue?

[johnnyoin]

@rlam3 I didn't have to since the app doesn't crash in my case. It stops on the Swift Error breakpoint but still works properly.

[iwasrobbed]

The whole point of throw is for devs to use try and catch those errors so it won't crash. If you're doing try! instead of try then you're causing the crash, not Locksmith.

[rlam3]

@iwasrobbed are we assuming that the throw is only used for development and not for production?

[getaaron]

@rlam3 no, there may be keychain errors at any time. Your app should handle failure cases gracefully. Using try! is not graceful.

[rlam3]

@getaaron Could you please kindly provide an example of a more graceful approach? Thanks!

[iwasrobbed]

@rlam3 Look at the do catch section: https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html

[getaaron]

@rlam3 I would be happy to provide a code sample. Can you post a full stack trace and the method you're calling so I can see how you're getting this to occur?