Apple Closes macOS Bug Reports Without Verifying Fixes
Developer Jeff Johnson has exposed Apple's practice of formally closing macOS bug reports without actually fixing the issues. The company requires reporters to confirm the defect in beta versions, ignoring any lack of response and marking tickets as "resolved".
Network Data Leak Case
In March 2023, Johnson filed report FB12088655 about IP addresses and TCP connections leaking through macOS network filters. The report included:
- Detailed repro steps.
- A test Xcode project.
- A public description of the issue.
Apple accepted the report but didn't respond for nearly three years. In March 2026, support asked him to check macOS 26.4 beta 4. Johnson refused to test betas, saying he didn't want to act as a free QA engineer.
Support didn't clarify if the fix was in beta 4 and gave him two weeks to respond. Without confirmation, the ticket would be closed as resolved. Johnson's tests on the release version of macOS 26.4 confirmed the bug persisted, but Apple didn't have internal testers verify it.
Systemic Issue with Report Handling
Johnson describes a recurring pattern:
- Report submitted with full repro steps.
- Apple ignores it for months or years.
- Requests reconfirmation in a beta version.
- Closes it without a response if there's no reply.
Recent example: A 100% reproducible bug closed with "diagnosis failed" status. Reopening got no support response in two weeks.
The developer suspects success metrics at Apple where the number of open tickets affects team KPIs. This incentivizes closing reports regardless of whether they're fixed.
Consequences for macOS Developers
This policy demotivates external contributors. Mid- and senior-level developers spend time on detailed reports but face ignoring or endless reconfirmation loops.
- Security risks: Leaks like FB12088655 go unfixed, threatening privacy.
- OS quality: Inconsistent handling erodes trust in the platform.
- Alternatives: Johnson recommends public posts instead of Feedback Assistant.
Apple's internal QA could handle repros themselves, but practice shows otherwise.
Key Takeaways
- Apple closes macOS bug reports without confirming fixes, demanding reconfirmation from reporters in betas.
- Example: Three-year-old report FB12088655 on IP/TCP leaks in network filters remains unresolved in macOS 26.4.
- Policy boosts stats: Closed tickets = success, regardless of quality.
- Developers waste time as free testers.
- Recommendation: Publish details publicly to pressure the company.
— Editorial Team
No comments yet.