att-framework-audit

Detects tracking SDKs missing App Tracking Transparency consent in iOS projects.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/tvh25082004/Badminton --skill att-framework-audit-tvh25082004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: att-framework-audit
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/privacy/att-framework-audit
Command: npx skills add https://github.com/tvh25082004/Badminton --skill att-framework-audit-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? iOS apps that integrate analytics or advertising SDKs without implementing the App Tracking Transparency prompt are rejected under App Store Guideline 5.1.2(i). This Skill audits your project before submission to catch missing ATT consent flows that would otherwise cause a rejection. ## Core Features & Use Cases - Tracking SDK Detection: Scans Swift sources and dependency manifests (Podfile, Package.swift) for Firebase, Amplitude, Mixpanel, Segment, Branch, AppsFlyer, Adjust, and similar SDKs. - ATT Compliance Checks: Verifies ATTrackingManager import, requestTrackingAuthorization calls, and the NSUserTrackingUsageDescription key in Info.plist. - Prioritized Findings: Outputs findings ranked from CRITICAL (guaranteed rejection) to LOW (best practice) with file paths and line numbers. - Use Case: Before submitting an app update that added Firebase Analytics, run this audit to confirm the ATT prompt is implemented and the purpose string is descriptive enough to pass review. ## Quick Start Audit my iOS project for App Tracking Transparency compliance and list any missing consent flow pieces.

Frequently Asked Questions about att-framework-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my iOS app needs the App Tracking Transparency prompt?▼

Any app integrating analytics, attribution, or advertising SDKs like Firebase, AppsFlyer, or Adjust that performs cross-app or cross-site tracking must show the ATT prompt. This audit greps your Swift sources and dependency manifests to detect such SDKs and flags missing consent flows.

How to fix App Store rejection under Guideline 5.1.2(i)?▼

Import AppTrackingTransparency, call ATTrackingManager.requestTrackingAuthorization before any data collection, and add NSUserTrackingUsageDescription to Info.plist. The purpose string should clearly explain what data is tracked and why, not a generic short message.

Does this audit work with React Native or Flutter projects?▼

Yes, the audit supports Swift, Objective-C, React Native, and Flutter projects. It scans source files, dependency manifests like Podfile and Package.swift, and Info.plist regardless of the framework wrapping the native layer.

Why does the ATT dialog appear on every app launch after an update?▼

This happens when the prior production binary's tracking metadata conflicts with the updated build, leaving the ATTrackingManager authorization state inconsistent. Test ATT behavior both on fresh installs and on updates from the live App Store binary before submission.

What are the limitations of this ATT audit?▼

The audit is read-only and performs static analysis only; it cannot verify runtime behavior such as whether requestTrackingAuthorization actually executes before analytics events fire. You must still verify initialization order in AppDelegate manually.