Development FAQ
Questions commonly asked regarding the development of Naver Game SDK.
Last updated
Questions commonly asked regarding the development of Naver Game SDK.
Last updated
When the message" Scope Status Invalid : Authentication failed" appears
‘Delete’ the Client ID that had been registered on the SDK management page and register it again. (Refer to the image below) Then see if the same issue occurs again.
We receive a lot of inquiries regarding login failures such as the following in the development process.
The following issue occurs when the Android package name (or iOS URL Scheme) that had been inputted to the ‘Naver Developers Center’ does not match with the actual game’s Android package name (or iOS URL Scheme).
Apply the values within the boxed area of the image above exactly as the same as the values in the game application.
[Reference] If the iOS project has multiple URL schemes an API call, such as the one shown below, is needed.
When making the release build to upload the Android project to the actual market, the Proguard is set in a lot of cases. In this situation, if nothing is set, the SDK’s library does not function normally, so please follow the guide and add the options to be removed from the Proguard.
The Naver ID is used to log into NaverGameSDK. If the Naver app is installed, ‘Naver App’s Convenient Login’ is used, but starting from iOS version 9 and above, an application that can call for it needs to be registered. The following categories have to be added from the lab’s plist.
For more detailed information, check the Login with Naver ID developer’s guide. https://nid.naver.com/devcenter/docs.nhn?menu=IOS
If the URL Scheme that had been set when registering for Login with Naver ID is not registered to the Xcode project, the login does not operate normally. Info -> Add URL Schemes from the URL Types category.
If you cannot login after not only checking the parts below but also the parts above, call upon the interface, [[NCSDKLoginManager getSharedInstance] setNaverLoginURLScheme:@"set skim value"]; while resetting or move the iOS URL Scheme provided by the Naver Developers Center to the highest position of the list to check.
This problem often occurs when adding many libraries, so attempt to build by setting to multiDex. For more detailed information, refer to the link below.
https://developer.android.com/studio/build/multidex.html
http://developers.kongregate.com/blog/dealing-with-the-64k-method-limit-in-your-unity3d-gamehttps://www.reddit.com/r/Unity3D/comments/3zv91o/android_build_dex_issues_please_help_xpost_unity2d/
If the problem is not resolved after referring to the above items, try the method stated below. Though it may differ for the versions of Unity being used, we provide the guide shown below because there have been cases in which the problem was resolved using the said guide. The https://appmediation.com/unity-enable-multidex/ file has been extracted from the sample, and this file allows the Gradle to be set locally if it is inputted into the project path below.
Set the Multidex and other elements. in accordance with the reference file. Check the build after putting the file into the Assets/Plugins/Android/ path of the Unity project.
Select Build System - Gradle(New)
If the file attached is put through the path below, Gradle uses the local’s instead. Check the attached file by copying it.
The structure of the file attached is as follows, and the contents regarding the build and Multidex are as follows as well. Check after putting the part below in accordance with the current project structure.
The NaverGame Android SDK included in the Unity Package stores the Android libraries used for the SDK in an .aar file for the project’s convenience. However, if the additional libraries used by your company for project development are identical to the library used by the SDK, an error can occur as the same library is referenced twice.
In the case that there are .jar and .aar files identical to the library used by the SDK within the Plugins/Android folder are present.
In the case that the library identical to the library used by the SDK within the dependencies block inside the mainTemplate.gradle in the Plugins/Android folder is announced with implementation or compile,
The problem can be solved by referencing the Android Platform Application Guide created without including the library used by the SDK. Follow the steps below.
Delete the Naver Game SDK (navergame-sdk-x.x.x.aar) within Plugins/Android, which was included in the Unity Package.
Download the library for gradles included in the Android Platform Application Guide.
Move the downloaded library (navergame-sdk-gradle-x.x.x.aar) to Plugins/Android within the Unity project.
Standardize the version of the library that had been duplicated after declaring the library used by the SDK in the dependencies block of Plugins/Android/mainTemlate.gradle.
Build the Unity project.
If you have any additional questions, please send them to Naver Game’s e-mail.
If the game reveals its status as development in process, and if you cannot login like below, please check the development status value of the application from the ‘Naver Developers Center.’ The status must appear as ’Service Applied’ after a Login with Naver ID review and approval if it is to be applied normally.
In order to apply the current SDK, follow the steps below for games that support 19 or below. 1) Change the aar file extension to zip and modify the minSdkVersion of the AndroidManifest.xml file by decompressing the file.
2) Compress the file again as a zip and change the file extension to aar.
3) Branch process to only allow versions 19 or above to be able to enter the SDK.
EXC_BAD_ACCESS that occurs from libraries related to AFNetworking
Our service has been developed using ARC. The fobjc-arc option must be added to all the files in the library for projects that do not use ARC.
