// Safely bump the wrapped Android SDK or iOS SDK version in the AppsFlyer Unity plugin, update the plugin version if needed, and validate all related files including both billing library variants.
Validate that expected AppsFlyer SDK events and callbacks were triggered during an end-to-end Unity app scenario using logs, callback payloads, and test evidence.
Run or review a basic end-to-end smoke test for the AppsFlyer Unity plugin on Android emulator or iOS simulator, covering startup, initialization, and basic event flow.
Analyze logs for a specific app launch and determine whether AppsFlyer initialization, start flow, callbacks, and expected events occurred correctly in the Unity plugin.
Debug communication issues between C# code and native Android/iOS implementations in the AppsFlyer Unity plugin.
Safely implement or modify a Unity plugin API in the AppsFlyer Unity plugin, including C# API, Android Java bridge, and iOS Objective-C bridge changes.
Review the AppsFlyer Unity plugin for release readiness, including versioning, changelog, Android/iOS parity, billing library variants, .unitypackage artifacts, and integration safety.
| name | sdk-version-bump |
| description | Safely bump the wrapped Android SDK or iOS SDK version in the AppsFlyer Unity plugin, update the plugin version if needed, and validate all related files including both billing library variants. |
Use this skill when updating the native Android or iOS SDK version wrapped by the AppsFlyer Unity plugin.
Perform a safe, consistent version bump across C#, Android, and iOS plugin layers, maintaining both billing library variants.
Assets/AppsFlyer/AppsFlyer.csandroid-unity-wrapper/build.gradle (af-android-sdk, billing library v7/v8)CHANGELOG.mddeploy/ .unitypackage files must be regenerated on release.android-unity-wrapper/build.gradle — af-android-sdk dependencyAppsFlyerAndroidWrapper.java — version constants if anyAppsFlyeriOSWrapper.mm — version constants if anyAssets/AppsFlyer/AppsFlyer.cs — version constantCHANGELOG.mddeploy/ .unitypackage files (must regenerate after bump)Return:
.unitypackage regeneration required: Yes | No.unitypackage files are release artifacts — flag them as needing regeneration.