菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AppsFlyerSDK/appsflyer-cordova-plugin --skill cordova-test-app-contract命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| name | cordova-test-app-contract |
| description | 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. |
| globs | test-app/**,.af-e2e/test-plan.json,.af-smoke/rc-test-plan.json |
test-app/)Use when:
test-app/ (www/, config.xml, native hooks if needed).[AF_QA] lines or iOS file log).Normative: appsflyer-mobile-plugin-tooling/contracts/test-app-contract.md.
| Item | Location |
|---|---|
| Widget / bundle id | com.appsflyer.qa.cordova — test-app/config.xml |
| JS entry | test-app/www/js/index.js (and www/index.html) |
| E2E execution | Sibling copy only — scripts/sync-test-app-e2e-copy.sh + scripts/e2e-cordova-build.sh; do not cordova build from in-repo test-app/ with file:.. (ENAMETOOLONG risk) |
.env (E2E sibling) | ../appsflyer-cordova-plugin-e2e/.env (CI: ENV_FILE secret) |
| Deep link scheme (plan) | afqa-cordova:// — must match deep_link_url entries in .af-e2e / .af-smoke JSON |
DEV_KEY, APP_ID from .env at runtime; never commit .env. Provide test-app/.env.example. On missing key, log [AF_QA][CONFIG] and fail fast per contract.[AF_QA] — e.g. [AF_QA][startSDK] result: SUCCESS, [AF_QA][CALLBACK][onInstallConversionData] ….shouldStartSdk: false / manual start pattern per Cordova plugin API → register onInstallConversionData, onAppOpenAttribution, onDeepLinking → pre-start APIs → log --- Pre-start auto APIs complete --- → startSdk() → post-start APIs → three events (af_demo_launch, af_purchase, af_content_view).[AF_QA] lines to Documents/af_qa_logs.txt (Cordova: small native plugin, hook, or cordova-plugin-file — see workplan §Phase 3). The scenario runner prefers this file on iOS because simctl log show often misses WebView console.log output.Plans poll / grep for lines including:
[AF_QA][startSDK] result: SUCCESS[AF_QA][AUTO_APIS] --- Auto run complete --- (or pre/post complete lines per plan JSON — keep spelling identical to .af-e2e/test-plan.json)Until the test app emits these, phase_1 will fail even when install/launch succeeds.
.af-e2e / .af-smoke config.*.env documentedstartSdk[AF_QA] strings match plan patterns exactlyafqa-cordova URL scheme on Android + iOSaf_qa_logs.txt implemented and flushed[AF_QA] prefix or plan regexes ad hoc.