# Launch Log Analysis

> Analyze logs for a specific app launch and determine whether AppsFlyer initialization, start flow, callbacks, and expected events occurred correctly in the Unity plugin.

- Skill: `appsflyersdk/launch-log-analysis` (Agent Skill)
- Install (CLI): `npx skillmds@latest add appsflyersdk/launch-log-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/appsflyersdk/launch-log-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: appsflyersdk (https://skillmd.com/u/appsflyersdk)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/appsflyersdk/launch-log-analysis

---


# Launch Log Analysis

Use this skill when inspecting logs from one or more app launches.

## Goal

Analyze each launch separately and determine whether expected AppsFlyer SDK flows occurred.

## Workflow

1. Separate logs by launch/session if multiple launches exist.
2. For each launch inspect evidence for: SDK initialization (`initSDK`), SDK start (`startSDK`), conversion callbacks, deep link callbacks, in-app events, warnings or errors.
3. Compare expected vs actual behavior for that launch.
4. Detect: missing events, duplicate events, unexpected events, inconclusive evidence.
5. Produce a launch-by-launch report.

## Output Format

For each launch return:
- Launch number
- Platform
- Expected events
- Confirmed events
- Missing events
- Duplicate or unexpected events
- Relevant log evidence
- Final result: Passed | Failed | Inconclusive

## Rules

- Treat each launch separately.
- Do not merge evidence from different launches.
- Do not guess when logs are noisy or incomplete.
- Recommend additional logging if needed.