- Last Updated
Mobile SDK 3.0.0 Migration — Physical Device Smoke Checklist (Unreal)
These are the items to check on a physical device after upgrading to 3.0.0 or higher by following the Mobile SDK 3.0.0 Migration Guide (Unreal).
00. What This Document Covers
This document collects only items that do not show up at build time. The problems most easily missed in this migration are
not compile errors but cases where the build succeeds, yet the app silently fails at runtime.
- The build succeeds even if the 2.9.x 8) patch remains in the iOS engine — login does not complete after external login
- The build succeeds even if window setup is missing when applying SceneDelegate — the app does not proceed past launch
- In some cases the build succeeds even if a coordinate or the
play-services-games-v2line is missing from_APL.xml
Compile · link · coordinate checks are done in Step.6 of the migration guide, not in this document. Run this document
after that step is complete.
💡 On Android, the plugins automatically add the push and overlay handling code to
GameActivity.
There is no code for the game to add; the items below verify that the automatically added handling works.
Time required: About 20 minutes per platform after preparation.
01. Preparation
- Android device + APK: Push and payment cannot be verified properly on an emulator
- iOS device + adhoc/development IPA: The simulator cannot receive push
- Test push sending: You must be able to send a test push from the server (A-3 · A-4 · I-2)
- Payment test account: An account registered for Google · Apple payment testing (C-1)
- External login account: An account for the external login used by the game (Google · Apple · Naver, etc.) (I-1)
- Deep link URL: Only for games using deep links — the URL actually used by the game (I-3)
💡 Test push sending and payment test accounts take time to prepare, so request them first.
02. Android
A-1. Login → enter the game
- Launch the app, log in, and enter the game screen
Expected: No blocking point from login success to entering the game.
On failure: A missing coordinate is the most common cause — check that the coordinate table in guide Step.4 matches the
plugins copied in Step.1.
A-2. GPG login — only for games using GPG
- Run Google Play Games login
Expected: Login completes after selecting the GPG account.
Cause (on failure): The com.google.android.gms:play-services-games-v2 line was deleted from _APL.xml
together with com.stove:* (guide Step.4 ⚠️).
A-3. Push — tap the notification while the app is running
- Launch the app, go to the home screen, and leave it in the background
- Send a test push from the server
- Tap the notification
Expected: The app returns to the foreground and the navigation in the push (notice · event, etc.) is handled.
A-4. Push — tap the notification after the app is fully terminated
⚠️ This is a different code path from A-3. Check both.
- Swipe the app away from the recent apps list to terminate it completely
- Send a test push and tap the notification
Expected: The app launches fresh and the navigation in the push is handled.
Cause (if A-3 · A-4 fail): Check that both the StovePush plugin folder (Step.1) and the com.stove:stove-push-firebase
coordinate (Step.4) are present. If the game modifies onCreate · onNewIntent of GameActivity through its own_APL.xml, also check that the code does not block the plugin's handling.
A-5. File attachment in an overlay screen
- Open an SDK overlay screen such as customer support · inquiry
- Tap the file (image) attachment button and pick an image from the gallery
Expected: The selected image appears in the attachment list.
Failure sign: The gallery opens normally, but after picking an image and returning, nothing
happens (no error either).
Cause: If the game modifies onActivityResult of GameActivity through its own _APL.xml,
check that the requestCode 7585 result is delivered to the SDK.
03. iOS
I-0. First launch after install — only for games that applied SceneDelegate
- Install and launch the IPA
Expected: The game screen appears after the splash.
Failure sign: The app does not proceed past a black screen or the splash right after launch.
Cause: Part of 1. Implement the common Scene lifecycle in Development Environment Setup iOS Unreal UISceneDelegate Update
is missing. Check that UIApplicationSceneManifest exists in the final .app's Info.plist, and that window creation and engine
initialization run in IOSSceneDelegate.
I-1. Return to the app after external login
⚠️ This is the item most often missed on iOS.
- Run the external login used by the game (Google · Apple · Naver, etc.)
- Complete authentication in the browser · system sheet · external app
Expected: The app returns automatically and login completes.
Failure sign: Authentication finished, but the app does not return, or it returns and the login result is not applied,
remaining in a waiting state.
Cause:
- The 2.9.x 8) patch (
application:openURL:options:, etc.) remains in the engine — guide Step.5 ① - If SceneDelegate was applied, the code that forwards from
scene:openURLContexts:tohandleOpenURL:is missing
I-2. Push
- With the app running, send a test push and tap the notification
- Fully terminate the app, send again, and tap the notification
Expected: In both cases the app opens and the navigation in the push is handled.
On failure: Check push permission · certificates · provisioning profile first (causes unrelated to the
migration are more common).
I-3. Deep link — only for games using deep links
Write the deep link URL in the Notes app and tap it. Check while the app is running.
Expected: The app returns to the foreground and navigates to the screen specified by the link.
Cause (on failure):
- I-1 also fails → Same cause as I-1
- I-1 passes → The game's deep link handling was not moved to
OnOpenURL(guide Step.5 ③), or the URL scheme settings are wrong
04. Both Platforms
C-1. One payment
- Make one actual purchase with a test account
Expected: Payment completes and the item is granted.
Cause (on failure): Check that both the StoveIAP plugin folder (Step.1) and the com.stove:stove-iap-google
coordinate (Step.4) are present. Since iOS runs on StoreKit 2 from 3.0.0, also check the product status in
App Store Connect and the test account.
C-2. Log out → log in again
- Log out and log in with a different account
Expected: The account switches normally and no previous account information remains.
05. Recording Results
| ID | Item | Result | Notes |
|---|---|---|---|
| A-1 | Login → enter the game | ☐ | |
| A-2 | GPG login (if using GPG) | ☐ | |
| A-3 | Push (app running) | ☐ | |
| A-4 | Push (app terminated) | ☐ | |
| A-5 | Overlay file attachment | ☐ | |
| I-0 | First launch (if SceneDelegate applied) | ☐ | |
| I-1 | Return to the app after external login | ☐ | |
| I-2 | Push (running · terminated) | ☐ | |
| I-3 | Deep link (if using deep links) | ☐ | |
| C-1 | One payment | ☐ | |
| C-2 | Log out → log in again | ☐ |
Test environment record — needed to reproduce failures.
| Item | Value |
|---|---|
| Unreal Engine version | |
| SDK plugin version | |
| Copied plugins | |
| iOS engine modification | SceneDelegate applied / applied as guided by the development team |
| Android device · OS | |
| iOS device · OS |
06. Priority
If time is short, cut down in the order below. The top 2 cannot be replaced by any other test.
- I-1 (return after external login) — the only way to verify guide Step.5
- C-1 (one payment) — the only item that verifies the payment path after the iOS StoreKit 2 transition
- A-4 (push while terminated) — not replaced by A-3
- I-0 · A-1 — failures are immediately visible, so these can be deferred
- A-2 · A-3 · A-5 · I-2 · I-3 · C-2
- Developers Center Usage / Smilegate Publishing Games: stove.developers@smilegate.com
- STOVE Store Onboarding / STOVE Studio: store.support@smilegate.com