You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am calling Swifter.authorize(withCallback: URL, presentingFrom: UIViewController, success: Swifter.TokenSuccessHandler, failure: Swifter.TokenFailureHandler) from a buttonpress in a UIViewControllerRepresentable. When clicking the Button, I am directed to a website in Safari to authorize my App. So far so good. After authorizing my app and getting returned by the Callback URL: “MyTwitterApp://“ neither the code inside Swifter.TokenSuccessHandler nor inside Swifter.TokenFailureHandler is run. Even the debugger does not step into it. In addition, at buildtime I get many warnings about init(account:) being deprecated since iOS 11.0 along other stuff. As I am using the newest version of Swifter and as I have found a fairly recent tutorial (definitely created after the launch of iOS 11) showing Swifter working, I am not sure if that creates any problem.
However, my main complaint is, that I am not able to authorize my app, as the code in success is not accessed.
The text was updated successfully, but these errors were encountered:
I am calling
Swifter.authorize(withCallback: URL, presentingFrom: UIViewController, success: Swifter.TokenSuccessHandler, failure: Swifter.TokenFailureHandler)
from a buttonpress in aUIViewControllerRepresentable
. When clicking the Button, I am directed to a website in Safari to authorize my App. So far so good. After authorizing my app and getting returned by the Callback URL:“MyTwitterApp://“
neither the code insideSwifter.TokenSuccessHandler
nor insideSwifter.TokenFailureHandler
is run. Even the debugger does not step into it. In addition, at buildtime I get many warnings aboutinit(account:)
being deprecated since iOS 11.0 along other stuff. As I am using the newest version of Swifter and as I have found a fairly recent tutorial (definitely created after the launch of iOS 11) showing Swifter working, I am not sure if that creates any problem.However, my main complaint is, that I am not able to authorize my app, as the code in
success
is not accessed.The text was updated successfully, but these errors were encountered: