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 using a custom authentication flow in my app, and I do not want to use SPAuthenticaionViewController. However when I subscribe to SPAuthenticatorDelegate I am forced to add the following properties to my view controller.
Sounds accurate: those two properties would be probably better part of a protocol. Back in the day, this was implemented to be consumed by Simplenote iOS.
You can check out it's current implementation here and here. Long story short, the customized login screen inherits from SPAuthenticationViewController, and tweaks few things around.
I'm sorry to say we can't really provide a schedule of when we'd be able to update / enhance the SPAuthenticatorDelegate protocol, since this is a bit of a low priority at this moment.
I am using a custom authentication flow in my app, and I do not want to use SPAuthenticaionViewController. However when I subscribe to SPAuthenticatorDelegate I am forced to add the following properties to my view controller.
@Property (nonatomic) SPAuthenticator *authenticator;
@Property (nonatomic, assign, readwrite) BOOL signingIn;
Shouldn't these just be some required methods to implement in an a authentication protocol?
The text was updated successfully, but these errors were encountered: