Getting error : "Connection error making token request to "<hostname>/connect/token": The network connection was lost..." on iOS 13, 12,11.

[shravankumarbj]

We are facing a issue in device in iOS 13, 12 and also in 11. Here is the log.

Printing description of tokenError: Error Domain=org.openid.appauth.general Code=-5 "Connection error making token request to 'https://.com/c2a48310-9715-3beb-895e-000000000000/login/token': The network connection was lost.." UserInfo={NSLocalizedDescription=Connection error making token request to 'https://.com/c2a48310-9715-3beb-895e-000000000000/login/token': The network connection was lost.., NSUnderlyingError=0x283b8a460 {Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={NSUnderlyingError=0x283b8acd0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={NSErrorPeerAddressKey=<CFData 0x281662710 [0x1c56575e8]>{length = 16, capacity = 16, bytes = 0x100201bb0d23e3560000000000000000}, _kCFStreamErrorCodeKey=53, _kCFStreamErrorDomainKey=1}}, NSErrorFailingURLStringKey=https://com/c2a48310-9715-3beb-895e-000000000000/login/token, NSErrorFailingURLKey=https://.com/c2a48310-9715-3beb-895e-000000000000/login/token, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=53, NSLocalizedDescription=The network connection was lost.}}}

[shravankumarbj]

We are using latest release AppAuth 1.2.0 in iOS. This issue happens randomly.

[WilliamDenniss]

https://.com/c2a48310-9715-3beb-895e-000000000000/login/token doesn't look like a valid URL to me. Is the client reconfigured?

[shravankumarbj]

Thanks for responding. Ofcourse I removed for security reasons. the URL was https://stg.xxxx.com/c2a48310-9715-3beb-895e-000000000000/login/token. May I know what client reconfigured means?. How to test it.?

[Luan-BK]

I'm currently experiencing the same issue. When calling the OIDAuthState.performAction() method from the AppDelegate's willEnterForeground it returns this connectivity error.

[fukemy]

hi, did someone solved this?

[fukemy]

@Luan-BK hi buddy, did u solved this?

[tdekoning]

@WilliamDenniss We're also experiencing this issue. In our case this only occurs when the user logs in after a fresh installation.