mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 20:55:57 +03:00
[GH-ISSUE #524] OAuthSwift - The operation couldn’t be completed. (OAuthSwiftError error -11.) #343
Labels
No labels
bug
cocoapod
duplicate
enhancement
feature-request
help wanted
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/OAuthSwift#343
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wikydtron on GitHub (Mar 28, 2019).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/524
Description:
I'm trying to send GPX file to Strava but when I send it via in-app I get this error message.
Here's some of my code:
OAuth Version:
OS (Please fill the version) :
Installation method:
Library version:
Xcode version:
10.1
@abinrm commented on GitHub (Apr 29, 2019):
I get this same error when I receive http response code 400 a response, I still don't know how to extract the response code from OAuthSwiftError. Whats your response code?
@phimage commented on GitHub (Apr 30, 2019):
@abinrm you don't know because you do not read response at your question or do not know how to use swift error...
please do not pollute other topic
@wikydtron you do not receive only "The operation couldn’t be completed. (OAuthSwiftError error -11.)"
You receive a well typed error OAuthSwiftError.requestError, then there is more information in the network error. print all error, not .localizedDescription
see https://github.com/OAuthSwift/OAuthSwift/blob/master/Sources/OAuthSwiftError.swift#L34
@SixFiveSoftware commented on GitHub (Jun 6, 2019):
I received this exact error as well when accessing Twitter's OAuth1 API, and in my case, I hooked up my Charles Proxy and found that I was receiving an error with:
...which was slightly different than the
-11error, but was directly related in the proxy output and the error seen by OAuthSwift.Searching around online, I found other articles that suggested recreating the OAuth manager instance with the consumer key and secret, and try again. So far, this has worked for us, but time may tell. Something inside the OAuth manager might have been cached such that a new instance cleared it up. Hope this helps.
@phimage commented on GitHub (Jun 10, 2019):
Just to clarify one time again, then I close