القائمة
Review the AppsFlyer Unity plugin for release readiness, including versioning, changelog, Android/iOS parity, billing library variants, .unitypackage artifacts, and integration safety.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | plugin-release |
| description | Review the AppsFlyer Unity plugin for release readiness, including versioning, changelog, Android/iOS parity, billing library variants, .unitypackage artifacts, and integration safety. |
Use this skill before releasing a new version of the AppsFlyer Unity plugin.
Check whether the plugin is safe and ready for release.
.unitypackage files in deploy/ need to be regenerated.Assets/AppsFlyer/AppsFlyer.cs — version constantCHANGELOG.mdandroid-unity-wrapper/build.gradle — Android dependency versions, both billing variantsdeploy/ .unitypackage artifacts — freshnessReturn:
.unitypackage regeneration required: Yes | No.unitypackage files must be regenerated before tagging a release.