Can not login via LINE apps. #10
Comments
I have the same trouble.
|
I have the same trouble. |
Here too. When I try to log in via LINE app (caling [adapter authorize]), it always returns the code LineAdapterErrorAuthorizationFailed with the message
In LINE app, my app which called [adapter authorize] was properly added to Authorized Apps (連動アプリ) although LineAdapter doesn't recognize it is authorized. On the other hand, logging in via LineAdapterWebViewController works fine. This problem is only for iOS. |
Got the same problem. |
"NLChannelGatewayErrorDomain Error 102" can occur if your iOS bundle ID is hasn't been properly registered in the "Technical Configuration" section of the Channel Console. Can you check to make sure that the an iOS Bundle ID has been registered and that it matches your application's iOS Bundle ID? For iOS applications, you should always check the following items:
|
Thank you for @mrmaakun ! I use another account to develop, so I haven't added "Roles" to that account. |
This is correct. If the app status is set to "DEVELOPING", only LINE accounts that are added to the "Roles" can log into the application. If the app status is set to "PUBLISHED", all LINE users will be able to log into the application. |
It looks like this issue has been resolved so I will close it. |
Hi @mrmaakun , is the bundle ID case sensitive? the bundle ID in 'Technical configuration' part (https://developers.line.me) only accept lowercase. But our app bundle identifier contains uppercase letter. I cannot change our app bundle ID easily. |
It turns out that my bundle ID doesn't starts with line3rdp, which cause the error. Now it's working for me. |
Hi @mrmaakun, one more following question, is the URL Scheme required to be in the format of this? can it be this format? |
It must be in the format |
When I authorized at LINE apps and it called back to my apps, It's always error like this
I have already double checked about configuration. It's all correct. However, I can login via LineAdapterWebViewController. Thank you for your suggestion.
The text was updated successfully, but these errors were encountered: