[INFO]
Minimum specifications
- User run environment : iOS 12 or later
- Build environment : Xcode 15 (iOS 16.1 SDK) or later
[Caution]
If some IdPs are supported, see the Support iOS Version field in the 3rd Party Gamebase Auth Adapters table shown below. When releasing the AppStore, Apple version policy must be complied with.
- https://developer.apple.com/ios/submit/
Gamebase can be setup as below.
Download Gamebase.xcframework.zip and required adapters.
Also download SDK files to authenticate each IdP, which are required only for a login.
Then, include corresponding SDK files to a target of your project.
Gamebase iOS SDK Components
Gamebase SDK | Gamebase Auth Adapter | External SDK & Compatible Version | Usage | Support iOS Version |
---|---|---|---|---|
Gamebase | Gamebase.xcframework Gamebase.bundle |
NHNCloudSDK 1.8.4 | Includes the interface and key logic of Gamebase | iOS 12 or later |
Gamebase Auth Adapters | GamebaseAuthFacebookAdapter.xcframework | FacebookSDK 17.0.2 | Supports Facebook login | iOS 12 or later |
GamebaseAuthPaycoAdapter.xcframework | PaycoID Login 3rd SDK v1.5.11 | Supports PAYCO login | iOS 12 or later | |
GamebaseAuthNaverAdapter.xcframework | naveridlogin-sdk-ios-4.2.1 | Supports NAVER login | iOS 12 or later | |
GamebaseAuthGamecenterAdapter.xcframework | GameKit.framework | Supports Game Center login | iOS 12 or later | |
GamebaseAuthGoogleAdapter.xcframework | GoogleSignIn 7.0.0 | Supports Google login | iOS 12 or later | |
GamebaseAuthTwitterAdapter.xcframework | Supports Twitter login | iOS 12 or later | ||
GamebaseAuthLineAdapter.xcframework | LineSDK 5.11.0 | Supports LINE login | iOS 13 or later | |
GamebaseAuthAppleidAdapter.xcframework | Sign In with Apple | iOS 12 or later | ||
GamebaseAuthHangameAdapter.xcframework | HangameID SDK 1.15.0 | Supports Hangame login | iOS 12 or later | |
GamebaseAuthWeiboAdapter.xcframework | weibo_ios_sdk-3.3.4 | Supports Weibo login | iOS 12 or later | |
GamebaseAuthKakaogameAdapter.xcframework | KakaoGame 3.19.0 | Supports Kakao login | iOS 13 or later | |
Gamebase IAP Adapters | GamebasePurchaseIAPAdapter.xcframework | StoreKit NHNCloudIAP 1.8.4 |
Supports in-game purchase | iOS 12 or later |
Gamebase Push Adapters | GamebasePushAdapter.xcframework | NHNCloudPush 1.8.4 | Supports Push | iOS 12 or later |
[Caution]
Gamebase SDK iOS 2.13.0 or later supports Sign In with Apple in iOS 9 or later, and additionally the Service ID needs to be set in the Gamebase Console.
[Caution]
The Gamebase Framework files that contain Adapter in their name can be selected to determine whether they will be used within the project or not. It is recommended to remove any unused Adapter Frameworks. To use these Adapter Frameworks, the external SDKs specified in the above table might be required. For some Auth Adapters, be aware of the supported iOS versions listed in the table above. (If an Auth Adapter that supports iOS version 12 or later is included in the build, it will crash on iOS 11 or earlier.)
[INFO]
For setting of external SDKs which each IdP provides, refer to each IdP guide.
By decompression, following SDKs will show, including Gamebase.xcframework.
[INFO]
The -ObjC option to the Linker allows all Objective-C classes and categories of Static Library to be loaded.
Therefore, if this option is not set, an error like selector not recognized may occur during runtime.
[Caution]
- When building with Unity (2019.3 or later), import the Gamebase iOS SDK only to the UnityFramework target.
- When you run Unity build, Unity-iPhone and UnityFramework are created in the Xcode project target.
- Note that there may be problems with operation if you import the Gamebase iOS SDK in duplicate for each target.
You can set the Gamebase iOS SDK with CocoaPods.
platform :ios, '12.0'
target 'SampleApplication' do
use_frameworks!
pod 'Gamebase'
pod 'GamebaseAuthFacebookAdapter'
pod 'GamebaseAuthGamecenterAdapter'
pod 'GamebaseAuthPaycoAdapter'
pod 'GamebaseAuthNaverAdapter'
pod 'GamebaseAuthTwitterAdapter'
pod 'GamebaseAuthGoogleAdapter'
pod 'GamebaseAuthLineAdapter'
pod 'GamebaseAuthAppleidAdapter'
pod 'GamebaseAuthWeiboAdapter'
pod 'GamebasePushAdapter'
pod 'GamebasePurchaseIAPAdapter'
# Regarding how to use the following modules, please contact the Customer Center.
pod 'GamebaseAuthHangameAdapter'
pod 'GamebaseAuthKakaogameAdapter'
end
[Note]
Enter the target name of the created project in the target 'SampleApplication' do part.
You can specify versions by writing in this way: pod 'Gamebase', '2.48.0'. If no version is specified in each pod, the newest version is used.
Only some specific Adapters can be selected and applied.
[Caution]
If you do not use the latest Gamebase version, some adapter may not be available.
[Note]
For more detailed information on how to use CocoaPods, see Using CocoaPods at CocoaPods Guide.
[Caution]
- Make sure that Gamebase service is enabled by creating a new project from NHN Cloud Console.
- Make sure that Client ID is issued by each IdP console and the IDs are entered in the Gamebase console.
<key>LSApplicationQueriesSchemes</key>
<array>
<string>fbapi</string>
<string>fb-messenger-share-api</string>
</array>
<key>FacebookAppID</key>
<string>{FACEBOOK_APP_ID}</string>
<key>FacebookClientToken</key>
<string>{FACEBOOK_CLIENT_TOKEN}</string>
<key>FacebookDisplayName</key>
<string>{FACEBOOK_DISPLAY_NAME}</string>
<key>LSApplicationQueriesSchemes</key>
<array>
<string>naversearchthirdlogin</string>
<string>naversearchapp</string>
</array>
URL Scheme must be configured.
For ATS setting, register the Scheme in the Info.plist file.
<key>LSApplicationQueriesSchemes</key>
<array>
<string>lineauth2</string>
</array>
<key>LSApplicationQueriesSchemes</key>
<array>
<string>sinaweibo</string>
<string>weibosdk</string>
<string>weibosdk2.5</string>
<string>weibosdk3.3</string>
</array>
{ "url_scheme_ios_only": "Your URL Scheme" }
NAVER
{ "url_scheme_ios_only": "Your URL Scheme", "service_name": "Your Service Name" }
LINE
<key>LineSDKConfig</key>
<dict>
<key>ChannelID</key>
<string>{Issued LINE ChannleID}</string>
</dict>
Included in SDK.
The API which is not supported by Gamebase anymore is processed as deprecated (deprecate). A (deprecated) API can be deleted without any prior notice when the following conditions are met:
Minor version updates of five or more times.
Time elapse of at least five months