New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask about credentials.code #115
Comments
You need to move |
Problem still exists |
Try without the breakpoint. Cause this way you're actually stopping the code as it reaches that row, so it can't propagate any request as |
https://prnt.sc/pgynah |
|
Since I can't see it in your last screenshot, does it really not work with persisting the |
If I us .credentials, i have this error https://prnt.sc/pgyvlx |
how do you test sending a message back? |
let handler = APIHandler()
let credentials = Credentials( … )
func login() {
…
} |
its all code, there is an error anyway ( import UIKit class ViewController: UIViewController {
} |
And what is the error this time? @rmelnik7777 |
2019-10-09 17:32:25.333892+0300 TestInsta[9747:281440] [] nw_connection_receive_internal_block_invoke [C1] Receive reply failed with error "Operation canceled" |
That actually looks like some sort of Xcode warning, not something |
I have a similar problem. It is not clear how to get into the failure block to set an authorization code from SMS. Can you help with an example? |
Hello I have same problem too. Can you share a working sample application for two factor auth ? |
@sbertix will post a clear example soon. |
Sorry I haven't managed to post an example yet, I've been really busy. |
I'm totally new with swift but maybe I found the bug: |
I didn't have a chance to investigate it further but it might as well be. Apparently on the current commit |
Hello,
Please, tell me. I have a problem.
With request in func login, I get an SMS with the code, that I registered in credentials.code = "121332".
I can’t send this code back. How to do it? What am I doing wrong?
This is my code
class ViewController: UIViewController {
}
The text was updated successfully, but these errors were encountered: