Question 1

What does Testara check?

Accepted Answer

Testara inspects your build and metadata against App Store Review Guidelines — privacy strings and tracking disclosures, SDK and Required Reason API usage, purchase and subscription flows, metadata accuracy, ATS exceptions, and common completeness issues that lead to rejection.

Question 2

How accurate is the analysis?

Accepted Answer

Findings are mapped to specific guidelines with a severity and confidence level. Audits are advisory — they surface likely issues before you submit, but a clean report isn't a guarantee Apple will approve your app.

Question 3

Do you store my source code?

Accepted Answer

We process your submission only to generate your report. Uploaded builds are removed from processing storage after signals are extracted, and we keep only the report data needed to show your audit — not long-term copies of your build.

Question 4

Which platforms and frameworks are supported?

Accepted Answer

Testara focuses on native and cross-platform iOS builds. It detects common SDKs, Info.plist keys, entitlements, and privacy manifest signals from your uploaded simulator build (a zipped .app).

Question 5

What kind of build do I upload?

Accepted Answer

A zipped iOS Simulator .app build. In Xcode, build for a Simulator destination, find the .app in Products, compress it to a .zip, and upload that.