Skip to content
Stove
Last Updated

Upgrading to 3.0.0

3.0.0 was released for all modules together. This page covers the changes and upgrade steps for every module in one place. Changes per module are also listed in each module's release notes.

3.0.0 (2026-10-08)

The SDK modules have been consolidated, so you must replace your dependencies.
Most authentication, payment, and push calls stay the same. Under What to Do When Upgrading below, check only the items that apply to your game.

At a Glance

ChangeAffected gamesWhat to do
Module consolidationAllRequired — replace dependencies
No automatic app exit on maintenance, sanctions, or force updatesAllRequired — handle app exit in the game
Game Log module separatedGames that use Game LogRequired — update code (call GameLog.Configure)
New login error codesGames that branch on login error codesCheck — read the cause code from origin_code
New setting for MemberNo gamesMemberNo gamesRequired — set enable_guid to false

What to Do When Upgrading

1. Replace your dependencies with the 3.0.0 modules.

Module names changed as the modules were consolidated. 2.9.x modules cannot be used together with 3.0.0 modules, so replace all of them.

💡 For Unity and Unreal, please follow the migration guides.

iOS (CocoaPods pods)

3.0.02.9.x
StoveSGSBase SGSLog SGSAuth SGSAuthUI SGSView
StoveProvidersSGSAuthApple SGSAuthFacebook SGSAuthGoogle SGSAuthNaver SGSAuthLine SGSAuthSteam
StoveIAP2SGSIAP2
StovePushSGSPush
StovePushExtensionSGSPushExtension (Notification Service Extension)
StoveGameLog (new)(included in the base modules)
Removed (no replacement)SGSGamingServices

Android (Gradle coordinates; all groups are com.stove)

3.0.02.9.x
stovebase log auth auth-ui view
stove-providersauth-google auth-googleplaygames auth-facebook auth-naver auth-line auth-steam auth-apple
stove-iapiap
stove-iap-googleiap-google
stove-iap-huaweiiap-huawei
stove-iap-onestoreiap-onestore
stove-pushpush
stove-push-firebasepush-firebase
stove-push-huaweipush-huawei
stove-gamelog (new)(included in the base modules)
Removed (no replacement)gamingservices
  • Add StoveGameLog / stove-gamelog only if your game uses Game Log.
  • Simply remove SGSGamingServices / gamingservices from your dependencies. The GPG User ID feature is included in StoveProviders.
Details — Code changes by platform
PlatformWhat changesWhat stays the same
AndroidGradle coordinatesimport packages (com.stove.auth…, etc.)
iOSPod names, #import paths (<SGSAuth/SGSAuth.h> → <Stove/Stove.h>; import Stove in Swift)Class names (SGSAuth, etc.), header file names
Unity.unitypackage set, Podfile, mainTemplate.gradleC# using Stove.StoveSDK, authentication, payment, and push calls
UnrealPlugin lists in .uproject, *.Build.cs, and _APL.xmlHeader #includes, stove:: calls

2. Handle app exit in the game on maintenance, sanctions, and force updates.

The SDK no longer force-quits the app when the notice screen is closed. Check the result's State and quit the app or block progress.

⚠️ If you do not handle this, users can keep playing after closing the notice screen.

📌 For how to handle it and code for each platform, see "Handling App Exit (3.0.0 or later)" in the Maintenance/Update guide.

3. If you use Game Log, your code needs to be updated.

Game Log has been split into a separate module. Add the dependency, and call GameLog.Configure once before using Game Log.

📌 For how to update your code, please contact your assigned technical PL.

Details — Dependencies to add and API changes

Dependencies to add

PlatformDependency
Androidcom.stove:stove-gamelog
iOSStoveGameLog pod
UnityStoveGameLog package
UnrealStoveGameLog plugin

API changes

  • GameLog.Configure has been added. Call it once before using Game Log.
  • The callback type of GameLog.Add has changed from Result to GameLogResult.
  • On Android, the package has changed from com.stove.log.game to com.stove.gamelog.domain, and the Context parameter has been removed from add and flush.

4. If you branch on login error codes, change how you read the cause code.

Login failures may now return error codes in the 60000 range. Regardless of whether you use the Data APIs or the SDK UI APIs (AuthUI, etc.), if your code branches on error codes for follow-up handling (such as logging out), update it to read the cause code from origin_code. Games that do not branch on error codes have nothing to do. For an example, see the integrated login code in Login.

📌 See the full list of 60000-range error codes in Integrated Error Codes > Mobile SDK > 3.0.0 New Error Codes.

Details — Checking the original cause code
  • The original cause code is included in the result's userInfo["origin_code"].
  • If your code branches on error codes, check both the 60000-range code and origin_code.
  • Existing error codes that are not in the table below are returned as the new error code 60000. The original code stays in origin_code. Examples: 10124, 11300, 44052.
  • The same existing error code can map to a different new error code depending on the login flow.
New error codeExisting error codeDescription
6020013004Regular-member conversion failed (account already in use)
60003406710Game withdrawal in progress
6000141005Invalid token
6000241006Invalid token
6000141007Email login failed (member not signed up)
6030041007Third-party login, sign-up required (member not signed up)
6000143000Email login failed (email not registered)
6030043000Third-party login, sign-up required (email not registered)
6000143002Wrong password 5 or more times
6030443002CAPTCHA required (wrong password 5 or more times)
6010043101Login restricted
6010043102Blocked after repeated login failures
6010043103Duplicate login restricted
6010043104Service use restricted
6000344000Inactive account
6000344001Withdrawal requested
6000344002Withdrawal completed
6000344004Overseas login blocked
6020045000Account already linked
6020045004Already used as the main account
6040045006GUID not registered
6030145006Game sign-up required
6020045011Already used as a sub account

5. If your game is a MemberNo game, set enable_guid to false.

MemberNo games need the setting below so that they can be identified as MemberNo games. GUID games have nothing to do.

PlatformWhere to setKeyValue
Android<application> meta-data in AndroidManifest.xmlcom.stove.config.enable_guidfalse
iOSInfo.plistStoveEnableGUID (Boolean)NO
Details — Setup examples

Android

Add the following inside <application> in AndroidManifest.xml.

xml
<meta-data
    android:name="com.stove.config.enable_guid"
    android:value="false" />

iOS

Add the following to the app target's Info.plist.

xml
<key>StoveEnableGUID</key>
<false/>

New Features

  • Unity and Unreal can now start as a guest, specify the identity verification type, and check the device registration state more simply.
    The existing methods still work. See the "From 3.0.0" notes in the Login, Identity Verification, and Device Registration guides.
  • Unity and Unreal can now request iOS push permission at any time you choose.
    iOS only. Call Push.RequestAuthorization (Unity) or Push::RequestAuthorization (Unreal) in iOS builds only (Unity #if UNITY_IOS, Unreal #if PLATFORM_IOS). If you do not call it, the SDK requests permission at login as before. On Android, the SDK requests the permission, so this API is not provided.
  • iOS UIScene is now supported.
    Apps that use a SceneDelegate must pass the URLs received in the SceneDelegate to the SDK. Otherwise, the app does not return after an external login. For how to apply this, see the Development Environment Setup guide for your engine.

Improvements

💡 No action is needed in your game for the items below.

  • Post-login guidance is adjusted on the server.
    To optimize the service globally, the authentication-related server APIs have been consolidated. Terms re-consent, device registration, and account status notices can be adjusted without an SDK update. Guidance screens are shown only in games integrated with the SDK UI APIs.
  • Improved Google login that failed on some Android devices.
    On certain devices, Google login could fail due to an issue in the Google framework, so the Google login API that the SDK calls internally has been switched to Google Sign-In (play-services-auth). The way your game calls login and the login screen users see remain the same.

Fixes

  • Fixed an issue where a completed iOS payment was reported as a failure.
    Even when payment and verification had completed successfully, an unnecessary error from the transaction-finish step was passed to the game.
  • Fixed an issue where iOS initialize stopped without responding.
    The callback was not called when values required for initialization, such as the app version, were empty.
  • Fixed an issue where initialize succeeded even though the remote configuration could not be fetched.
    This happened when the response body was corrupted, or on Android when a network error occurred and the previously saved configuration was used to report success. initialize now returns a failure, so please check your retry or notice handling.
  • Fixed an iOS push registration issue.
    The callback could be called twice when the registration info had not changed, or the registration info could fall out of sync with the server.

Requirements

💡 Same as 2.9.x. Follow each platform's (Apple, Google, engine) policy.

Item3.0.0
iOS minimum version15.0
Android minSdk / targetSdk / compileSdk24 / 35 / 35
Android Gradle Plugin / Kotlin / Java8.6.1 / 1.9.25 / 17



Do you have any inquiries?