Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.anything.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

When something works in the builder preview or Expo Go but breaks in TestFlight, the answer is almost always in your device’s logs. This page covers how to pull them. The recommended path is Apple’s Console app on a Mac. If you don’t own a Mac, the on-device options below get you the same information. Console.app ships with macOS. It streams live logs from any iPhone or iPad you plug in. The steps below get you from raw stream to the exact slice you’ll paste into the builder.
1

Plug your iPhone into the Mac

Lightning or USB-C. Unlock the phone and tap Trust if prompted.
2

Open Console and pick your phone

Spotlight (cmd-space) and search Console. In the left sidebar, click your iPhone under Devices.
3

Sort by time, oldest first

Click the Time column header until newest entries land at the bottom. This matches the order you’ll experience the bug, so the failure shows up at the end of your stream.
4

Filter to your app

In the search bar at the top, type process:YourAppName and press Enter. Use your app’s display name (the one on the iPhone home screen) without spaces. For auth bugs, add a second term: subsystem:com.apple.AuthenticationServices. Each term should appear as a separate pill in the search bar.
5

Start streaming and reproduce the bug

Click Start streaming, then trigger the broken flow on your phone. New lines appear at the bottom in real time.
6

Pause and find the failure line

Click Pause as soon as the bug hits. Scroll to the bottom of the stream. Look for the first red Fault or Error line that lines up with what you saw on screen. Note its timestamp.
7

Select the right slice

Click a log line about 5 to 10 seconds before the error timestamp. Scroll down and shift-click a line 5 to 10 seconds after the error. That’s your slice: the failure plus the context around it. Aim for 30 to 100 lines, not the whole stream.
8

Copy and paste into builder chat

Right-click the selection and choose Copy (or cmd-C). Switch to the builder, open chat in Discussion mode, and paste. Wrap the pasted log in a triple-backtick code block so the agent reads it cleanly. The full prompt template is in Give the logs to the agent below.
Toggle the Errors and Faults filter in the toolbar to hide info-level chatter while you’re hunting for the failure line. Turn it back off before you select your slice, so the surrounding context lines are included in the copy.

​
No Mac? Three options that work from your phone

You don’t need a computer to get useful logs off your device. These options work from the iPhone alone.

​
1. TestFlight feedback (easiest)

This is the fastest path and it’s built into TestFlight.
1

Reproduce the bug in the TestFlight build

Hit the failure on purpose so the system captures it fresh.
2

Take a screenshot

Press the side button + volume up. TestFlight detects the screenshot and offers to send beta feedback.
3

Submit feedback

Tap Share Beta Feedback, describe what happened, and send. TestFlight automatically attaches recent crash logs and device info.
The feedback lands in App Store Connect, and you can forward it to support. Good for crashes and for most “it didn’t work” cases.

​
2. Crash reports from Analytics Data

Every crash on your phone writes a small .ips file you can grab directly.
1

Open Settings

Go to Settings → Privacy & Security → Analytics & Improvements → Analytics Data.
2

Find your app's crash

Scroll for a filename that starts with your app’s name and ends in .ips. The newest entries are at the bottom.
3

Share it

Tap the file, then the share icon in the top right. AirDrop, email, or save to Files.
An .ips file only exists if the app actually crashed. If your bug is “I tap the button and nothing happens,” skip to sysdiagnose below.

​
3. Sysdiagnose (full diagnostic bundle)

A sysdiagnose is the closest thing to “everything Console.app would have shown, packaged up.” It’s heavier (200 to 400 MB) but it captures the full system log around the moment you triggered it.
1

Reproduce the bug

Trigger the failure in TestFlight.
2

Trigger the diagnostic

Immediately press and hold both volume buttons + the side button for about 1.5 seconds. You’ll feel a short vibration. Release. Don’t hold longer or you’ll get the power-off screen.
3

Wait 10 minutes

The bundle assembles in the background. It is not instant.
4

Retrieve it

Go back to Settings → Privacy & Security → Analytics & Improvements → Analytics Data and scroll for a file named sysdiagnose_YYYY.MM.DD_*.tar.gz. Tap it, then share via AirDrop, email, or Files.
Sysdiagnose bundles include broad system data. Only share them with people you trust to triage your app.

​
Reading logs from Windows or Linux

If you want to inspect logs yourself instead of sending them on, both Windows and Linux have options. Windows
  • iMazing has a built-in device console that mirrors Console.app. The free tier is enough to stream logs and export crash reports.
  • The “Apple Devices” app from the Microsoft Store only handles sync and backups. It does not show logs.
Linux (or WSL)
  • libimobiledevice is open source. idevicesyslog streams live device logs over USB. idevicecrashreport -e ./out pulls all crash reports off the phone.
Either tool will read crash reports and live device logs. For the full sysdiagnose .logarchive format, you still need a Mac (or a cloud Mac for an hour).

​
Give the logs to the agent for a fix

Once you have a log, the goal is to get the relevant part in front of the builder agent with enough context that it can identify the cause.
The builder chat doesn’t accept raw log files yet (no .ips, .tar.gz, or .txt drops). You can paste a pastebin or GitHub Gist link and the agent will fetch the URL, but long content often gets truncated on read. Pasting the relevant slice directly into chat is the most reliable path on every plan and every mode.

​
Pull the right slice (not the whole log)

A focused 30 to 100 lines around the failure beats a 10,000-line dump every time. The agent does better work with a small, on-target excerpt. For a Console.app slice, follow the steps above. For other sources:
  • From a .ips crash report: open the file in any text editor. Copy the top metadata block (Exception Type, Exception Codes, Termination Reason) plus the Crashed Thread backtrace. Skip the other threads unless you know they matter.
  • From iMazing on Windows: the device console works the same way as Console.app. Filter by process, reproduce, pause, select the lines around the failure, and copy.
  • From idevicesyslog on Linux: pipe to a file (idevicesyslog > log.txt), reproduce the bug, stop the stream with ctrl-C, then open the file and pull the lines around your failure timestamp.
  • From a sysdiagnose: open system_logs.logarchive in iMazing (Windows) or log show --archive (Mac), filter the same way, and copy the relevant lines. The full bundle is too big to paste.

​
How to frame it in chat

Use Discussion mode so the agent investigates without changing your code. Paste the slice and frame it like this: 
This TestFlight build fails when I tap Sign in with Google.
Web preview and Expo Go work fine. Build number 42.

Steps:
1. Open the app
2. Tap Sign in with Google
3. Browser opens, I pick my account
4. Back in the app, the screen flashes and returns to the login screen

Expected: I land on the home screen, signed in.

Logs from Console around the moment I tapped:

```
<paste the 30 to 100 relevant lines here>
```
Ask the agent what’s failing before asking for a fix. Once you understand the cause, switch to Thinking mode and ask for the specific change. The full triage workflow is in Get help.
If your slice is still too long to paste comfortably, attach a screenshot of the log instead. The chat accepts images, and the agent can read text out of them. Pasted text is still better when you can manage it.

​
What to send to support

If the bug isn’t something the agent can fix from a prompt, email hello@anything.com with:
  • What you did, step by step, and what you expected to happen
  • A screenshot or screen recording of the failure
  • The log file (TestFlight feedback, .ips crash report, or sysdiagnose)
  • Your TestFlight build number (visible in TestFlight under your app’s name)
Email can take attachments that chat can’t, which is the right place for a full .ips file or a sysdiagnose bundle.

Testing

Preview your mobile app on a real device

App Store submission

The full TestFlight and App Store publishing flow

Get help

How we triage and what to send

Verify Apple Developer account

Make sure your account is active and ready