[GH-ISSUE #222] Persist OAuthSwiftCredential version #123

New issue

Closed

opened 2026-03-03 16:45:52 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 16:45:52 +03:00

Owner

Originally created by @paulhimes on GitHub (Apr 14, 2016).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/222

The "version" property of the OAuthSwiftCredential object is not persisted during the NSCoder encode / decode cycle.

The version always comes back as OAuth1 after a decode.

Originally created by @paulhimes on GitHub (Apr 14, 2016). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/222 The "version" property of the OAuthSwiftCredential object is not persisted during the NSCoder encode / decode cycle. The version always comes back as OAuth1 after a decode.

kerem closed this issue

2026-03-03 16:45:52 +03:00

kerem commented

2026-03-03 16:45:53 +03:00

Author

Owner

@phimage commented on GitHub (Apr 14, 2016):

Yes it is not and a PR can be done if this is a real problem

In which case not persist the version could be a problem?
(The credential could not be set in oauthclient)

@phimage commented on GitHub (Apr 14, 2016): Yes it is not and a PR can be done if this is a real problem In which case not persist the version could be a problem? (The credential could not be set in oauthclient)

kerem commented

2026-03-03 16:45:53 +03:00

Author

Owner

@phimage commented on GitHub (May 4, 2016):

without response I close

@phimage commented on GitHub (May 4, 2016): without response I close

kerem commented

2026-03-03 16:45:53 +03:00

Author

Owner

@phimage commented on GitHub (Jul 7, 2016):

N.B. now the credential could be set when initialising client, this could add misunderstanding

@phimage commented on GitHub (Jul 7, 2016): N.B. now the credential could be set when initialising client, this could add misunderstanding

kerem referenced this issue

2026-03-03 16:49:16 +03:00

[PR #123] [CLOSED] Check the http url response's status code before using it #526