> ## Content Index > Fetch the complete content index at: https://www.techbetweenthelines.com/llms.txt > Use this file to discover other available public pages before exploring further. # Where Your Apple Bug Report Goes Now: Inside Our Rebuilt Problems Tracker - URL: https://www.techbetweenthelines.com/how-our-apple-problems-tracker-works/ - Published: 2026-10-28T23:22:29.000Z - Updated: 2026-10-28T23:22:29.000Z - Description: Our problems tracker now covers iPhone, iPad, Mac and Apple Watch, turns matching reader reports into cards and Feedback Assistant filings, and tells you when Apple ships the fix. - Author: Justin Scharlemann - Tags: Apple OS 27, iPhone, Mac & iPad, Apple, #toc ## The short version Our [iOS 27 problems tracker](https://www.techbetweenthelines.com/ios-27-problems-and-fixes/) now covers iPhone, iPad, Mac and Apple Watch on one page, with a switch at the top for your device. Every problem carries a label that says exactly what is known, and nothing is marked Fixed until Apple's own release notes say so. Your report doesn't sit in a thread. It's matched to a known problem or grouped with reports like it. When three different readers report the same new problem on different days, it gets its own card. When five readers write it up, we file it with Apple through Feedback Assistant. Tap "Get an email when Apple fixes this" on any card and you'll hear when that changes. Since the report form opened on October 21, readers have sent 56 reports from iPhones, iPads and Macs and tapped "I have this too" 32 times. As of October 28, the board tracks 18 problems, and six are filed with Apple. You don't need an account, an email address or a name to report, and we never publish what you type word for word. ## Why a forum thread isn't enough Every iOS release produces the same thread. Someone posts that their battery is draining or Messages stopped sending photos, a few hundred people reply that they have it too, and the "I have this question too" counter on Apple Support Communities keeps climbing. A week later the thread is buried under the next one. Forums are good at proving you aren't alone, and bad at almost everything after that. Nobody sorts the replies into one problem with a count behind it. Nobody checks whether the next update fixed it. A reply doesn't reach Apple's engineers, because Apple's bug channel is Feedback Assistant, and most people have never opened it. When a fix ships, nobody goes back to tell the people who were waiting. Here's the difference in practice. On October 22, a reader told us Messages had stopped sending photos after the update. More readers reported the same thing over the next few days, and we couldn't find matching iOS 27 threads anywhere else. By October 27 it had a card on the board and a report filed with Apple, five days after the first reader flagged it. We launched the first version of this tracker earlier this month as a board of known problems and a report form. It showed us what was missing. Reports arrived faster than a weekly review could handle, the page only covered the iPhone, and too much depended on someone remembering to check. So we rebuilt it around one rule: a report should always lead somewhere. ## What the tracker does for you ![Live reader data at the top of the Tech Between the Lines problems tracker, with report counts, filings with Apple and known problems by status](https://www.techbetweenthelines.com/content/images/2026/10/tracker-hero.jpg) Live reader data at the top of the tracker, with the device switch below it. Screenshot: Tech Between the Lines ### One page for every device iPadOS 27 and macOS 27 share a lot of code with iOS 27, so the same bug often turns up on more than one device. The page now tracks iPhone, iPad, Mac and Apple Watch together. Pick your device at the top and the board, the reader reports and the totals follow it. Show everything and each device gets its own section, so an iPad problem never gets lost in a list of iPhone ones. ### Labels that mean something Fixed means Apple's release notes or an Apple statement name the fix. Prevented means Apple stops new cases, but devices already affected stay that way. No fix yet means it's widely reported and Apple hasn't addressed it. Unconfirmed takes at least 10 owners describing the same thing in more than one place over at least three days. Watching covers real reports that are still below that bar, and Not a bug is for behavior Apple designed or documented, even when it's annoying. Every card shows its source, so you can see what the label is based on. ### Reports that count The form asks for your device, software version, problem area and one sentence about what happens. That sentence is matched against every known problem by the symptom you describe, so "the keyboard takes forever to show up" and "typing lags in Messages" land on the same card. A new problem is grouped with similar reports under Reader reports, where you can see it counted. ### Cards that add themselves When at least three different readers report the same new problem on at least two different days, the tracker adds a Watching card to the page on its own. The first one went up on October 28: apps that stop connecting over Wi-Fi or cellular after updating, reported by iPhone readers since October 22\. Every automatic card gets reviewed after it appears and can be pulled with one click. ![An automatic Watching card on the problems tracker showing the symptom, where it stands, what to do and the I have this too button](https://www.techbetweenthelines.com/content/images/2026/10/tracker-card.jpg) The first Watching card the tracker added on its own, on October 28\. Screenshot: Tech Between the Lines ### Reports that reach Apple When five readers have written up the same problem, we turn their reports into one Feedback Assistant report with steps and scope, and file it. Anyone else with the problem gets an "add your report" kit with the filing number and text to paste into their own report. Apple groups duplicate reports, so more of them on one issue carries more weight. Six problems were filed on October 27, including Messages photos that won't send, the keyboard being slow to appear and Siri stalling in CarPlay. ### An answer when it's fixed "Get an email when Apple fixes this" puts you on a list for that card. When Apple's notes name the fix, the card flips to Fixed and we email that list. The tracker feeds the rest of the site too. [iOS Health](https://www.techbetweenthelines.com/ios-health/) shows how each update is going from reader check ins, and The Cupertino Chronicles carries a weekly Reader Pulse with what you reported and where it went. ## What we keep and what we don't You never need an account to report. We publish a paraphrased summary, never your words. To allow one "I have this too" per problem and to count different readers for the Watching rule, we keep a scrambled, shortened code made from your connection. It's never shown anywhere and never leaves our system. Public numbers never include report text, and any problem with fewer than three reports is left out of them. ## The technical dive ### Where it runs The tracker runs on four Cloudflare Workers. The main one stores reports and "I have this too" taps, runs the AI tagging and serves the script that turns our Ghost page into the interactive tracker. The other three watch Apple's release notes, keep the software version lists current and handle upkeep like the Should I Update? card. The problem cards and write ups live in Ghost, so the page still shows every problem as a plain board if the script ever fails to load. ### How a report moves Cloudflare Turnstile checks each report first, which stops most automated spam without making you solve a puzzle. Then an AI model reads it. It throws out jokes, spam and complaints about a single third party app, holds reports too vague to act on, writes a short headline and summary, and compares the symptom to every card on the board. A second, stricter pass runs every six hours on reports the first pass couldn't place. It attaches a report to an existing card only when it's very confident, and merges reader groups that describe the same problem in different words. It never touches a report that already matched, and every change it makes can be undone. ### Evidence from outside our site Reader reports are one source, and the Unconfirmed bar needs more than one kind. Every six hours the tracker reads the MacRumors forums for iOS 27, iPhone, iPadOS 27, iPad and macOS 27, keeps threads that describe a specific bug, and groups them by problem with an owner estimate and how long it has lasted. Apple Support Communities blocks automated reads, so it gets checked by search in a weekly review. Everything feeds a list of flags: a card that looks ready to move up, a reader problem ready to file, a write up going stale, an Apple update that might fix something. On Apple's usual release days, Monday through Thursday, the tracker checks Apple's release notes every hour from late morning through mid afternoon Mountain time. When a new version lands, it compares the notes with every open problem, and the board and our release explainer get updated the same day. ### People still make the calls Flags are leads, and a person decides. A weekly review works through every flag, rechecks the sources and either updates the page or proposes changes for approval. Moving a card to Unconfirmed, removing one and marking something Fixed all need evidence a person has read. The only automatic step is adding a Watching card from reader reports, and its wording follows the same rules as everything else: no reader quoted word for word, and no advice beyond harmless steps like restarting and reporting the problem to Apple Support. ### The code lives in version control All of the code sits in a private GitHub repository: the Workers, the page code, the database setup and the instructions for every scheduled job. A nightly job copies the custom code from our Ghost site into it, so any change shows up as a dated difference we can review or roll back. Every change is checked for leaked keys and for code that doesn't match what's live, and nothing goes live without approval. ## Where this is going A tracker that fades after launch week isn't worth much, so the plan from here is about making the data useful well beyond this page. ### An open dataset We already publish an anonymized copy of the tracker data every day: counts of reader reports by problem, device family, software version and day, under a CC BY 4.0 license so anyone can use it with credit. It stays private until it holds a few hundred reports or iOS 27.3 ships, because a dataset with three issues in it would mislead more than it informs. Once it opens, journalists, developers and anyone curious can check our numbers instead of taking our word for them. ### A monthly State of iOS 27 With enough data behind it, we'll publish a monthly look at what readers reported, what Apple fixed and how long the fixes took. ### An open version of the setup We plan to publish a cleaned up version of the tracker code, so other sites and communities can see exactly how it works and build their own. ### More iPad and Mac coverage The iPad and Mac sections are small today because those reports are just starting to come in. They'll fill in the same way the iPhone side did, one report at a time. We use AI throughout this, and we say so on the site. It sorts reports, writes summaries and drafts filings. The labels, the bar and the call on what Apple has actually fixed stay with people. If something on your iPhone, iPad, Mac or Apple Watch broke after an update, [report it on the tracker](https://www.techbetweenthelines.com/ios-27-problems-and-fixes/) or tap "I have this too" on the card that matches. The next big test is iOS 27.3\. When it ships, every open card gets checked against Apple's notes the same day, and the people waiting on those fixes hear about it.