// 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.
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.
Review the AppsFlyer Unity plugin for release readiness, including versioning, changelog, Android/iOS parity, billing library variants, .unitypackage artifacts, and integration safety.
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.
| name | plugin-api-change |
| description | 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. |
Use this skill when adding, removing, or changing a Unity plugin API.
Make a safe API change across all plugin layers while preserving backward compatibility where possible.
Assets/AppsFlyer/AppsFlyer.cs.AppsFlyerAndroid.cs (Android) | AppsFlyeriOS.cs (iOS) → Native bridgeAppsFlyer.cs — public API entry pointAppsFlyerAndroid.cs — Android delegation (uses AndroidJavaClass/AndroidJavaObject)AppsFlyeriOS.cs — iOS delegation (uses [DllImport("__Internal")])#if UNITY_IOS / #if UNITY_ANDROID guards.asmdef) boundaries — do not breakAppsFlyerSDK — do not changeAppsFlyerAndroidWrapper.java — Java bridge methodAppsFlyeriOSWrapper.mm — Objective-C++ bridge functionReturn: