NaverLoginConfig
Everything NAVER's SDKs need to identify your application.
Pass it to NaverLogin.configure once, before any other call.
About clientSecret
NAVER requires the client secret in the app, on both platforms — it is a parameter of the native SDKs' own initialisers, and there is no client-side flow that omits it. So it ships inside your APK and IPA, where anyone can read it out; treat it as public and design your backend on that assumption. In particular, a NAVER access token obtained by a client proves nothing to your server on its own: verify it server-side against NAVER before you trust it.
This library cannot fix that, and neither can NAVER's own SDKs. It is documented here because the alternative — saying nothing — leaves people believing a secret in an app is a secret.
Properties
The application name NAVER shows on its login and consent screens. The mobile web login screen shows the name registered on the console instead, so a mismatch here is visible to users.
The client secret issued alongside it. Read the note above.
iOS only, ignored on Android, and required there. The custom URL scheme NAVER returns to after an app-to-app login. It must match CFBundleURLSchemes in your Info.plist and the scheme registered on the console, and it must be unique to your app — a scheme another installed app also claims will break the login in ways that look random.
Functions
Deliberately omits clientSecret: configuration objects end up in logs and crash reports.