reauthenticate

Makes the signed-in user prove who they are again.

NAVER shows its login screen even though a valid session exists, and the user has to enter their credentials — the question being whether the person holding the phone now is the person who signed in. Worth asking before something that cannot be undone: a payment, a change of registered details, deleting an account.

Why this is not a NaverLoginPrompt

NAVER's Android SDK has no equivalent. NidOAuth offers a login and a permission reprompt, and nothing that forces re-entry of credentials. Putting this in shared code would mean the same call doing two different things depending on the platform, which is worse than not offering it — so it lives here, callable from your iosMain source set or from Swift, and Android needs an answer of its own.

Before calling

Configure and log in first. This returns NaverLoginErrorCode.Authentication when the device holds no token, because a session that does not exist cannot be re-proved.

Unlike NaverLogin.login this is not serialised against a login already running — the mutex that does that belongs to NaverLogin and is private to it. Do not start one while the other is open: NAVER's SDK tracks a single pending flow, and the second one takes it.