[PR #568] [MERGED] Add support for expired Twitter tokens #673

New issue

Closed

opened 2026-03-03 17:29:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 17:29:36 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/OAuthSwift/OAuthSwift/pull/568
Author: @deyton
Created: 1/23/2020
Status: ✅ Merged
Merged: 1/24/2020
Merged by: @phimage

Base: master ← Head: twitter-expired-token

📝 Commits (1)

7354314 Add support for expired Twitter tokens

📊 Changes

2 files changed (+18 additions, -0 deletions)

View changed files

📝 OAuthSwiftTests/OAuthSwiftErrorTest.swift (+14 -0)
📝 Sources/NSError+OAuthSwift.swift (+4 -0)

📄 Description

See https://developer.twitter.com/en/docs/basics/response-codes

Twitter sends back errors in an errors array in the body, but it doesn't use any of the currently-supported method of indicating an expired or invalid token.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OAuthSwift/OAuthSwift/pull/568 **Author:** [@deyton](https://github.com/deyton) **Created:** 1/23/2020 **Status:** ✅ Merged **Merged:** 1/24/2020 **Merged by:** [@phimage](https://github.com/phimage) **Base:** `master` ← **Head:** `twitter-expired-token` --- ### 📝 Commits (1) - [`7354314`](https://github.com/OAuthSwift/OAuthSwift/commit/7354314a66351d99ae2aa09a548219997a1373f2) Add support for expired Twitter tokens ### 📊 Changes **2 files changed** (+18 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `OAuthSwiftTests/OAuthSwiftErrorTest.swift` (+14 -0) 📝 `Sources/NSError+OAuthSwift.swift` (+4 -0) </details> ### 📄 Description See https://developer.twitter.com/en/docs/basics/response-codes Twitter sends back errors in an errors array in the body, but it doesn't use any of the currently-supported method of indicating an expired or invalid token. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>