AppsFlyerSDK

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.

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.

Maps the AppsFlyer Cordova RC pipeline (RC prep, lint-test-build, E2E, npm publish, rc-smoke, promote) to workflow files in this repo. Use when editing rc-release, rc-smoke, promote-release, or lint-test-build; not for day-to-day feature work.

Run or triage AppsFlyer Cordova E2E/smoke via ./scripts/af-scenario-runner.sh, sibling E2E copy, smoke dir, and JSON reports. Use for local reproduction, CI log triage, or report summaries.

Maps AppsFlyer Cordova CI (android/ios E2E workflows, ENV_FILE, sibling copy, smoke scripts) to the tooling smoke/E2E story. Use when editing .github/workflows/*e2e*, rc-smoke (when added), or debugging scenario CI.

Build or review test-app/ for AppsFlyer Cordova against the tooling test-app contract: .env, [AF_QA] logs, auto-run SDK order, afqa-cordova deep links, iOS af_qa_logs.txt. Use when implementing Phase 3 or reviewing test-app PRs.

Performs a simple version-bump release of the AppsFlyer Cordova plugin (no public API changes). Use when the user wants to release a new Cordova plugin version that only updates SDK dependencies (Android, iOS) and plugin version.

Describes how the RC release pipeline works for the AppsFlyer Capacitor plugin and maps each stage to its workflow file. Use when inspecting, triggering, or debugging the RC-release, npm OIDC publish, rc-smoke, promote-release, or production-release workflows; not for day-to-day plugin development.

Verify an AppsFlyer Capacitor plugin release (RC or production) by installing from npm, building and running the example app on Android and iOS, and validating SDK behavior from device logs. Use when the user asks to test a release, verify an RC, run the example app after publishing, or check that a published plugin version works on both platforms.

Run or review an RC release for the AppsFlyer Flutter plugin. Follows the six-stage RC pipeline (RC-PREP, RC-E2E, RC-PUBLISH, RC-SMOKE, RC-PROMOTE, RC-RELEASE) defined in appsflyer-mobile-plugin-tooling. Use when cutting a new RC, debugging a failed rc-release / rc-smoke / promote-release run, or reviewing a promote PR.