This document provides frequently asked questions and answers.
You can change your app's icon or name displayed on the Consent screen, a Kakao Talk message, or the Manage Connected Services page.
Refer to How to change OWNER.
If the owner is unknown or missing, send us an OWNER change request via platform.developers@kakaocorp.com
with the documents below.
Send us the following information and attachments via platform.developers@kakaocorp.com
.
No. App keys are unique identifier given to each app. You can check your app keys or reissue new ones in [My Application] > [App Keys]. However, make sure that the previous app keys after the reissue are deleted and cannot be recovered. If you request an API such as Kakao Login API using the previous app key, the request fails. Thus, do not reissue app keys for the service in operation, except for inevitable cases such as your app key is revealed.
Because an app is used to register service information on the Kakao platform, a newly added app is considered as a different service even though its name is the same as the existing app. Thus, the user information of the existing app cannot be shared with or migrated to the new app.
In addition, a member ID (user_id) is assigned to each user per app. If you add a new app, a different member ID is assigned to the same user on the new app. In this case, you cannot check if the user is the same person using the existing app, and the user also has to sign up again even though the user has previously signed up before.
For these reasons, do not change your app keys by creating a new app with the same service information or reissuing app keys. Make sure that you cannot recover the previous app keys or migrate user information after reissuing app keys.
In the following cases, you do not have to reissue app keys:
If you need to change the service information, you can modify it in [My Application] > [General]. If you lost all accounts with permission to manage the app so cannot check or modify the service information, you must request to change the app owner by referring to Q. How can I change the app owner?.
You can use the Kakao Open APIs free of charge for a certain duration every month as long as you have not exceeded the quota limit. If you request an API after exceeding the limit, you may receive the "API limit has been exceeded." message and will not be able to request the API anymore. To check the quota and limits for each API, refer to the quota.
If you want to increase the quota limit, request negotiation or partnership arrangements in DevTalk. To increase quota limit of the Kakao Maps API or Local API, check the Notice first. Kakao reviews your request and then may enter into partnerships or increase the quota limit temporarily as you request.
You can register site domains up to 10 by default. To register more than 10 site domains, permission is required. Proceed as follows to request permission:
@kakao
" with the following information:After permission is granted to your app, you can register up to 100 site domains. You can also use the wildcard subdomains functionality to allow more flexible subdomains.
Yes. Using the test app, you can test without affecting the actual operating service. To set up a test app, refer to Test app.
This error occurs when the key hash value used in your app is different from the value registered on the platform.
If you are using Android App Bundles, recommended method to publish your app, you must register the value obtained by using the Google Play Console to get Release key hash. With the Android App Bundles, when you sign your app bundle with an upload key and upload to the Google Play Console, Google Play generates the APK and signs your app. Thus, in this case, you cannot use the release key hash value obtained through Terminal or the Android SDK.
KakaoSDKFriend
and RxKakaoSDKFriend
modules include the built binary framework unlike other modules. If you want to insall KakaoSDKFriend
or RxKakaoSDKFriend
modules under 2.15.0 version, you must add the following code snippet at the bottom of your Podfile. Afterthat, run pod install
to apply the changes.
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
end
end
end