- Cập nhật lần cuối
Mobile SDK 3.0.0 Migration — Real Device Smoke Checklist (Unity)
Mobile SDK 3.0.0 마이그레이션 가이드(Unity) These are the items to verify on a real device after upgrading to 3.0.0 as instructed.
00. What this document covers
I have collected only the items that do not appear in a build. The problem that is easy to miss in this migration is not a compile error, but a case where the build succeeds but it does not work without errors when executed.
- The build succeeds even without the 3 Android entry point hooks (
Push.handleIntent×2 ·ViewUI.handleIntent/7585) - The build succeeds even without
onOpenURL:andconfigurationForConnectingSceneSession:in the iOS AppController - The build succeeds even if the manifest points to a non-existent Activity class
Compile, link, and coordinate checks are done in Step.5 of the migration guide, not in this document. Please execute this document after that is finished.
Time required: It takes about 20–30 minutes per platform after completing the pre-preparation.
01. Pre-preparation
- Android real device + APK: Push notifications and payments cannot be properly verified on an emulator
- iOS real device + adhoc/development IPA: Push notifications cannot be received on a simulator
- Test push sending: Must be able to send test push notifications from the server (A-2 · A-3 · I-2)
- Deeplink URL: URL actually used in the game (A-4 · I-3)
- Payment test account: Account registered for Google/Apple payment testing (C-1)
- External login account: Google or Apple account (I-1)
- Log check:
adb logcatfor Android, and Xcode Devices or Console.app for iOS
💡 Since test push sending and payment test accounts take time to prepare, please request them in advance.
02. Android
A-0. First execution immediately after installation
- Install the APK and execute it via the launcher icon
Expectation: The app launches normally.
Failure signs: It terminates immediately upon execution and logcat inClassNotFoundException: Didn't find class "…" or ActivityNotFoundException remains.
Cause: AndroidManifest of activity android:name points to a non-existent class.
Refer back to Step.1 A · B of the guide — if you are extending by inheriting, it should be your own class; if you are using the SDK file as is, it should be com.stove.unity.StoveUnityPlayerActivity, and if the latter, that .kt file must actually exist in Assets/Stove/Plugins/Android/.
# 실제로 무엇이 런처로 등록됐는지 확인
adb shell cmd package resolve-activity --brief -c android.intent.category.LAUNCHER <패키지명>
A-1. Login → Enter Game
- Execute the app, log in, and enter the game screen.
Expectation: There are no blocking points from successful login to entering the game.
In case of failure: Missing coordinates are the most common — check if the coordinate list in Step.3 of the guide and the imported packages are 1:1. If you see logcat in NoClassDefFoundError, that is the issue.
A-2. Push — Tapping notification while the app is running (onNewIntent path)
- Execute the app and go to the home screen to leave it in the background
- Send a test push from the server
- Tap the notification
Expectation: Returns to the app, and the navigation (notice/event, etc.) contained in the push is processed.
Cause (in case of failure): There is no onNewIntent in Push.handleIntent of the entry point Activity.
A-3. Push — Tapping notification while the app is completely terminated (onCreate path)
⚠️ This is a different code path from A-2. You must do both. If you only do one, you pass with one hook missing.
- Swipe to completely terminate the app from the recent apps list
- Send a test push and tap the notification
Expectation: The app executes newly and the navigation contained in the push is processed.
Cause (in case of failure): There is no onCreate in Push.handleIntent(applicationContext, intent).
A-4. Deeplink
adb shell am start -a android.intent.action.VIEW -d "<딥링크 URL>"
Expectation: The app opens and moves to the screen specified by the link. Check both the state where the app is running and the terminated state (the path is different for the same reason as A-2/A-3).
A-5. File attachment on the overlay screen (requestCode 7585)
⚠️ This is the only path to verify this hook. It does not appear in any other test.
- Open the SDK overlay screen such as Customer Center · Contact Us
- Press the file (image) attachment button and select an image from the gallery
Expectation: The selected image appears in the attachment list.
Failure signs: The gallery opens normally, but after selecting an image and returning, nothing happens (no error either).
Cause: There is no onActivityResult in if (requestCode == 7585) ViewUI.handleIntent(requestCode, resultCode, data) of the entry point Activity.
03. iOS
I-0. First execution immediately after installation — Check for black screen
- Install and execute the IPA
Expectation: The game screen appears after the splash screen.
Failure signs: It does not proceed beyond a black screen immediately after execution (not a crash).
Two causes:
- Missing
application:configurationForConnectingSceneSession:options:in the custom AppController (Guide Step.4 ③) - Unity is below 2022.3.72f1 but SceneDelegate was not applied →
Appendix A of the guide (Source +Info.plist+UnityFrameworkCompile Sources registration).
For 2022.3.72f1 and above, Unity handles it, so this is not the cause.
💡 If you use your own build post-processing script, this setting is not automatically included. The SDK sample is handled by
XcodeSettingsPostProcesser, but the game's own script must be reflected directly.
I-1. Returning to the app after external login
⚠️ This is the most frequently missed item on iOS.
- Execute Google or Apple login
- Complete authentication in the browser/system sheet
Expectation: Automatically returns to the app and login is completed.
Failure signs: Authentication is finished, but it does not return to the app, or even if it returns, the login result is not reflected and it remains in a waiting state.
Cause: Missing Guide Step.4 ② in the custom AppController —AppDelegateListener adoption · init of UnityRegisterAppDelegateListener(self) ·onOpenURL: implementation — all three must be present. In the UIScene lifecycle, application:openURL:options: is not passed to the app delegate, so if only the existing override remains, this symptom occurs (do not delete the existing override).
I-2. Push
- Send a test push while the app is running and tap the notification
- Completely terminate the app, then send again and tap the notification
Expectation: In both cases, the app opens and the navigation contained in the push is processed.
In case of failure: Check push permissions · certificates · profiles first (causes unrelated to migration are more common). If it is on the SDK side, check the SGSPushNotificationCenterDelegate adoption of the AppController and the import path of ① in Guide Step.4.
I-3. Deeplink — Only for games that use deeplinks
Write the deeplink URL in a memo app and tap to open it (Universal Links will not open the app if entered in the Safari address bar).
- Tap the link while the app is running
- Completely terminate the app, then tap again
Expectation: In both cases, the app opens and moves to the screen specified by the link.
Cause (in case of failure):
- Only 1 fails → Same
onOpenURL:path as I-1 - Only 2 fails → Cold start path. If Unity is below 2022.3.72f1, check if the SceneDelegate in Appendix A of the guide is missing
- I-1 passed but both fail → It is on the URL scheme · Universal Links setting side, not the SDK entry point
04. Common to both platforms
C-1. 1 Payment
- Actually pay for 1 product with the test account
Expectation: Payment is completed and the item is provided.
Cause (in case of failure): It is most common that the imported market package and mainTemplate.gradle coordinates are mismatched (Guide Step.3). Since 3.0.0 has separate packages for each market, check whether the package for the market you are using was imported and whether those coordinates were entered together.
C-2. Account logout → Re-login
- Log out and log in with a different account
Expectation: The account is switched normally and no previous account information remains.
05. Result Recording
| ID | Item | Result | Note |
|---|---|---|---|
| A-0 | First execution after installation | ☐ | |
| A-1 | Login → Enter game | ☐ | |
| A-2 | Push (App running / onNewIntent) | ☐ | |
| A-3 | Push (App terminated / onCreate) | ☐ | |
| A-4 | Deeplink (Running · Terminated both) | ☐ | |
| A-5 | Overlay file attachment (7585) | ☐ | |
| I-0 | First execution — No black screen | ☐ | |
| I-1 | Return to app after external login | ☐ | |
| I-2 | Push (Running · Terminated both) | ☐ | |
| I-3 | Deeplink (Running · Terminated both) | ☐ | |
| C-1 | 1 Payment | ☐ | |
| C-2 | Logout → Re-login | ☐ |
Test environment record — The following is required to reproduce the failure.
| Item | Value |
|---|---|
| Unity version | |
| Received package type | By feature / Full package |
| Imported package | |
| Android entry point | Own Activity(Inheritance) / SDK file |
| iOS AppController | Game's own / SDK file |
| Android device · OS | |
| iOS device · OS |
06. Priority
If you are short on time, reduce in the following order. The top 3 are not replaced by any other test.
- A-5(File attachment /
7585) — The only path to verify this hook - I-1(Return from external login) — The only path to verify iOS Step.4 ②
- A-3(Push notification from app terminated state) —
onCreatePath to verify the hook. It is not replaced by A-2 - I-0(Black screen) · A-0(First launch) — Can be postponed as it is immediately visible if it fails
- C-1 · A-4 · I-3 · A-2 · I-2 · C-2
- Developers Center Usage / Smilegate Publishing Games: stove.developers@smilegate.com
- STOVE Store Onboarding / STOVE Studio: store.support@smilegate.com