// Debug communication issues between C# code and native Android/iOS implementations in the AppsFlyer Unity plugin.
| name | platform-channel-debug |
| description | Debug communication issues between C# code and native Android/iOS implementations in the AppsFlyer Unity plugin. |
Use this skill when a C#-to-native or native-to-C# flow is not working correctly.
Find where the Unity native bridge is broken between C#, the platform-specific wrappers, and native SDK integration.
AppsFlyer.cs → AppsFlyerAndroid.cs (AndroidJavaClass) | AppsFlyeriOS.cs ([DllImport])AppsFlyerAndroidWrapper.java | AppsFlyeriOSWrapper.mm#if UNITY_IOS / #if UNITY_ANDROID), null handling, callback thread assumptions.AppsFlyer.cs — public API call and platform delegationAppsFlyerAndroid.cs — AndroidJavaClass/AndroidJavaObject callAppsFlyeriOS.cs — DllImport extern function signatureAppsFlyerAndroidWrapper.java — Java bridge method signatureAppsFlyeriOSWrapper.mm — Objective-C++ bridge function signatureReturn:
needs verification.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.
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.
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.