We have found that the LINE login button (LineLoginButton) used in the sample app did not successfully register a login result callback listener. Therefore, this PR fixed this issue and also made some minor adjustments to other content.
To solve the issue of loginListener's onLoginSuccess and onLoginFailure not being called after login, we used the LoginDelegate provided by the SDK itself. Specifically, we passed the login activity's Intent and its relative params to LineLoginButton by calling loginDelegate.onActivityResult(...), allowing it to internally call the registered loginListener. For more information about LoginDelegate, please go to here.
In addition to this change, we also adjusted some of the other code in the sample app, such as the view model, to reflect these changes.
The minimum kotlin version of SDK has been upgraded to 1.7.20, and the gradle has been upgraded to 7.6.
Description
We have found that the LINE login button (
LineLoginButton) used in the sample app did not successfully register a login result callback listener. Therefore, this PR fixed this issue and also made some minor adjustments to other content.To solve the issue of
loginListener'sonLoginSuccessandonLoginFailurenot being called after login, we used theLoginDelegateprovided by the SDK itself. Specifically, we passed the login activity'sIntentand its relative params toLineLoginButtonby callingloginDelegate.onActivityResult(...), allowing it to internally call the registeredloginListener. For more information aboutLoginDelegate, please go to here.In addition to this change, we also adjusted some of the other code in the sample app, such as the view model, to reflect these changes.
The minimum kotlin version of SDK has been upgraded to
1.7.20, and the gradle has been upgraded to7.6.