Developers’ Frustrations with Apple’s Bug Reporting System

Apple’s bug‑reporting platform, Feedback Assistant, is drawing sharp criticism from the developer community. A seasoned iOS/macOS developer has detailed a three‑year saga of ignored bug reports, forced “verification” requests, and premature closures that leave critical issues unresolved. The story highlights growing frustration over what many see as a broken quality‑control loop in Apple’s software development process.

What Happened?

In March 2023 the developer filed FB12088655 – a privacy‑related bug where a network‑filter extension leaked TCP connections and IP addresses. Despite providing detailed reproduction steps and an Xcode project, Apple remained silent for three years. Only weeks ago did the company ask the reporter to “verify” the issue on the macOS 26.4 beta 4 build, threatening to close the report if no response arrived within two weeks.

The developer, who does not run beta builds year‑round, was forced into a costly “wild‑goose chase.” Independent testing by the Little Snitch team confirmed the bug persisted in the beta, and it remained reproducible after the public release of macOS 26.4 on March 25 2026.

More Unresolved Issues

Another report, FB22057274, concerns “pinned tabs” in Safari where slow‑loading links open in the wrong tab. Apple marked the case as “Investigation complete – Unable to diagnose with current information,” yet the developer never received a request for additional data. The bug continues to affect users, underscoring a pattern of premature closures.

Why Developers Are Upset

• Time wasted: Developers invest hours reproducing bugs, only to receive vague or no feedback.
• Beta verification pressure: Apple’s demand for verification on beta OS versions forces developers to maintain multiple test devices.
• Artificially low bug counts: Closing reports without fixing them may give Apple an inaccurate picture of software quality.
• Inconsistent communication: Evasive answers and threats to close tickets erode trust.

Industry Reaction

While the developer’s personal boycott of Feedback Assistant never gained traction, the broader community is voicing concerns on forums, Reddit, and at recent WWDC sessions. Some suggest a revamp of the platform, including transparent status updates, mandatory response windows, and a public dashboard of open bugs.

What’s Next?

Apple has not issued an official statement regarding these specific cases. However, the company’s recent developer news releases hint at upcoming improvements to beta testing workflows, which could indirectly address the verification bottleneck.

For developers seeking alternatives, third‑party bug‑tracking tools (e.g., Jira, GitHub Issues) remain viable for internal reporting, but they lack the direct line to Apple’s engineering teams that Feedback Assistant provides.

Read the Full Original Account

The detailed narrative, including step‑by‑step reproduction guides and correspondence with Apple, is available in the original blog post: “Apple randomly closes bug reports unless you ‘verify’ the bug remains unfixed”.

Related Coverage on ubos.tech

Stay updated on this developing story and other developer‑focused news:

• Apple Bug Report Issues – Full Analysis
• Top Developer Tools to Watch in 2026
• WWDC 2026 Highlights: What’s New for Developers?

Keywords: Apple bug reports, Feedback Assistant, macOS beta verification, developer frustration, software quality, Safari pinned tabs bug, WWDC 2026, iOS development, macOS 26.4, bug‑tracking platform.