To report an iOS bug, first choose the right recipient. Apple platform issues can go through Feedback Assistant for eligible developers and beta-program participants. A problem limited to a third-party app usually belongs with its developer. For an app you are testing through TestFlight, use its beta-feedback option.
Whichever route you use, include the device, software versions, steps, expected result, and actual result. A short, reproducible report is more useful than a long complaint or a guess about the underlying code.
Where to report an iPhone or iOS bug
| Situation | Reporting route | Purpose |
|---|---|---|
| An Apple platform, API, or developer-tool issue | Feedback Assistant, using an eligible account | Send technical feedback to Apple |
| General iPhone product feedback | Apple’s iPhone feedback form | Share product comments with Apple |
| You need help with your device now | Apple Support | Get troubleshooting or service assistance |
| Only a third-party app is affected | The app’s App Support link or developer | Reach the team responsible for that app |
| You are testing a TestFlight app | Send Beta Feedback in TestFlight | Send evidence to the beta app’s developer |
How to report an iOS bug to Apple
Check access to Feedback Assistant
Apple’s Feedback Assistant access guide lists Apple Developer registration, the Apple Beta Software Program, and AppleSeed for IT as eligible account routes. If you are not affiliated with those programs, use the relevant product-feedback route instead.
iOS betas include the Feedback Assistant app. See the Apple beta-program FAQ for its availability. You do not need to install a beta simply to give general iPhone feedback.
Prepare and submit the report
- Open Feedback Assistant or its website, and sign in with your eligible account.
- Start new feedback and choose the topic that best matches the issue.
- Complete the form’s questions with a specific title, environment, steps, expected result, and actual result.
- Attach relevant evidence and review the information before sending.
- Keep the assigned feedback ID with your team’s tracking record.
Apple’s developer feedback guide explains diagnostic collection, report IDs, and follow-up. Report promptly so useful information is not lost. If someone else may have reported the same issue, Apple still encourages you to submit your own evidence.
Product feedback and immediate help
The iPhone product-feedback form accepts comments about the product. Apple says it cannot respond to each submission individually. Use Apple Support when you need troubleshooting or service; do not rely on a feedback submission as an appointment or support case.
How to report a bug in a third-party iOS app
If one app is affected and other apps work, start with its developer. In the App Store, open the app’s product page, scroll to Ratings & Reviews, and select App Support. Follow the developer’s instructions for submitting the problem.
Apple’s app-developer contact guide explains this route. If the app did not come from the App Store, contact the developer directly through its official support channel.
Include the app version and the action that failed. “The app does not work” gives the team very little to investigate. “Export closes the app after I choose PDF in this report” identifies a specific task and result.
How to send TestFlight beta feedback
- Open TestFlight and select the app you are testing.
- Tap Send Beta Feedback.
- Choose whether to include a screenshot, then add your comments and reproduction details.
- Review and submit the feedback.
See Apple’s TestFlight instructions for screenshot, crash, and feedback options. This route helps the app developer investigate its beta; it is separate from reporting an Apple platform issue.
Copyable iOS bug-report template
Title: [Action] produces [unexpected result] in [app or feature] Device model: iOS version and build, if available: App name and version/build: Date and time observed, including time zone: Relevant setup: [permissions, account state, network, or settings] Steps to reproduce: 1. Start from [known state]. 2. Perform [specific action]. 3. Observe [result]. Expected result: Actual result: Frequency: [observed attempts, not an estimate] Impact: [task blocked or data affected] Workaround, if tested: Evidence: [screenshot, recording, or requested diagnostics] Related feedback or support ID:
Keep unknown fields marked unknown. Separate what you observed from what you suspect. For an intermittent failure, record the conditions and the attempts you actually made rather than claiming it happens every time.
Example: a report an app developer can reproduce
Illustrative example, not an actual incident:
Title: Export closes the app after selecting PDF Environment: [device model], [iOS build], [app version] Starting state: Signed in to a test account with a saved report. Steps: 1. Open the saved report. 2. Tap Export. 3. Select PDF. Expected: A PDF is created or an explanatory error appears. Actual: The app closes before a file appears. Frequency: Observed in 2 of 3 attempts on the same device. Impact: The user cannot share the report through this workflow. Evidence: Short recording showing the steps; event time noted.
The sample does not diagnose a memory problem or claim that iOS caused the failure. It gives the receiving team a testable sequence. Compare it with our bug-report examples and adapt our general reporting templates for other environments.
Attach evidence that answers the question
A screenshot suits an incorrect layout or message. A short screen recording suits a sequence, a timing issue, or behavior that disappears quickly. Show the relevant starting state and the failure, then add the written steps so the reader does not need to infer them from video.
Use test data where possible, and keep unrelated messages or account information out of attachments. Apple’s iPhone screen-recording instructions explain the built-in recorder and note that some apps restrict recording.
For Apple diagnostics, follow the requested instructions or the relevant Apple profiles-and-logs guide. Do not attach an unrelated collection of files just because a report accepts uploads. Relevant context is more useful than volume.
Follow up and track the issue
Record the recipient, submission date, reference ID, affected versions, owner, and next action in your team’s issue tracker. Link the report manually unless your team has verified an integration for that workflow.
Check for requests for more information and respond with the missing evidence. When a proposed fix becomes available, repeat the same reproduction steps and record the tested version and outcome. A submitted report is evidence that you raised the issue; it is not evidence that the issue has been fixed.
Frequently asked questions
Can I report an iOS bug without joining a beta program?
General product feedback is available through Apple’s iPhone feedback form. Feedback Assistant has its own account eligibility requirements, including the developer route. For help with a device problem, use Apple Support.
Should every iPhone app bug go to Apple?
No. Start with the app developer when the problem is limited to that app, or use TestFlight feedback for an app you are beta testing. Choose the recipient who can investigate the affected software.
Will submitting a detailed report guarantee a fix?
No. Clear evidence helps investigation, but a report does not establish the cause, priority, or release date of a fix. Track the response and verify any proposed resolution.
What if I cannot reproduce the bug again?
Report the event you observed, its time, environment, and available evidence. State that it has not reproduced in later attempts rather than inventing a reliable sequence.
