This repository has been archived by the owner on Aug 24, 2019. It is now read-only.
use "SecItemUpdate" method when item already exists #85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I made a similar change locally and can confirm that this is a reasonable improvement. |
soffes
added a commit
that referenced
this pull request
Jun 19, 2015
use "SecItemUpdate" method when item already exists
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can access the keychain when the screen is locked (Today Widget) and the keychain will be locked when screen is locked for a certain amount of time.
If the keychain locked after item delete,The data will be lost.
So I think a good way to use [SecItemUpdate] method