12 ms·

Apple's feedback mechanism is broken

174 points by goranmoomin 4y ago

wilg 4y ago
It's really a terrible experience. Especially since no one else can see it and simply upvote it. Instead everyone has to do the busy work all over again.
junofan 4y ago
Feedback Assistant is not a support channel. It also is not a new name for Radar. You can find support channels under “Requesting Support”: https://developer.apple.com/bug-reporting/ https://developer.apple.com/bug-reporting/ You are not limited to 2 technical support incidents per year. You can purchase more. I think it’s pretty fair.
- suzzer99 4y ago
  Just out of curiosity - how much to they cost?
  - 1123581321 4y ago
    Apple: Additional TSIs are available for purchase in either a 2-pack for 99 USD or 5-Pack for 249 USD (or in local currency where available) in the Code-Level Support section of your account. TSIs purchased separately expire one year from the date of activation. Seems like you save a few pennies per incident with two packs unless you really need an odd number.
    - onionisafruit 4y ago
      What weird pricing. Why not just make them $50 each? Or $49 if they have a policy that prices end with the digit 9.
      - paranoidrobot 4y ago
        Because it raises the barrier to entry and probably has a serious impact on the number of issues raised.
      - Reason077 4y ago
        Forcing multiple-unit pricing likely increases sales. You probably came to the purchase page just needing one. But you’re probably 𝖽̶𝖾̶𝗌̶𝗉̶𝖾̶𝗋̶𝖺̶𝗍̶𝖾̶ motivated enough to pay extra for a bundle of two if you have to! You’ll justify it by telling yourself “I might need the second one later”, but I’ll bet a lot of them end up going unused. Raising the entry price slightly perhaps also makes people think a little harder about whether they really need to use a TSI or whether other support channels (Stack Overflow? Reddit?) might be more appropriate.
        jandrese 4y ago
        But why would you ever buy they 5 pack? Is the purchasing a real hassle? At least with the 2 pack you are probably only going to waste one.
        smalley 4y ago
        I could imagine a corporate customer who might be slightly less cost sensitive but have employees that would prefer not to go through a purchase order approval process multiple times might be where purchases like that get made
  - dfabulich 4y ago
    https://developer.apple.com/support/technical/ https://developer.apple.com/support/technical/ > Additional TSIs are available for purchase in either a 2-pack for 99 USD or 5-Pack for 249 USD (or in local currency where available) in the Code-Level Support section of your account. TSIs purchased separately expire one year from the date of activation.
- iancarroll 4y ago
  I’ve only ever filed one or two of these “technical support incidents” but even though it sucks to pay for support — they have some very good engineers answering these tickets, and in one case they got a bug fix for an API shipped pretty quickly.
whatever1 4y ago
Apple does not need active feedback mechanism. It just needs a list of gotchas to avoid for their next generation of products. Their customers of previous products can go f off or buy the new products.
cambo 4y ago
For all the hate Microsoft gets, this is one area where they've got it right. Microsoft's dev support framework, while not directly interacting with MS engineers (usually), the community of MVPs, Regional Directors, and even now the occasional Dev note in the opensource work MS is doing on github, has lead to a great ecosystem of support. This trickles down to Stackoverflow, the old Alt.Net crowd (and the associated .NET user groups that still persist), and the MS dev blog'o'sphere mean this type of issue is much rarer. *edit: oh and I forgot the UserVoice pages, where the community can vote on issues, and they'll get assessed by the product teams.
- onionisafruit 4y ago
  They eventually got it right. I remember being a sysadmin circa 1999 and having to pay to file a bug report with Microsoft. IIRC if they determined it was a real bug you got your money back.
- gnicholas 4y ago
  I had the exact opposite experience with UserVoice pages, at least the one for Accessibility. Someone requested that MS integrate my startup's reading technology into MS Word/Outlook/etc on the Accessibility UserVoice. This suggestion gained steam and was the top-rated suggestion for years. MS never engaged with the suggestion, and when I later asked an accessibility person why this was, they told me that the UserVoice is staffed by outside contractors, and that it's not one of the more important places they look for feedback. This was consistent with what I saw, which was that they didn't engage with the most popular suggestions on the Accessibility UserVoice — they just ignored them. I think it's pretty lousy that they set up a page to solicit feedback (especially accessibility feedback) and don't pay attention to it. It causes people to waste time describing issues, asking for help, and voting on other suggestions. A year or two ago they got rid of the UserVoice page, and they now tell people to use Twitter to make suggestions.
- gary_0 4y ago
  I posted an obscure MS C++ compiler bug to their Web feedback thing, and it got acknowledged and fixed relatively quickly. Whining and complaining over on the r/cpp subreddit also tends to get the polite attention of the relevant Microsoft people (some of whom are mods).
hamburglar 4y ago
I’ve had the same experience reporting bugs every single time. You never ever get a response and simple bugs languish for literal years with no action. Eventually, they sometimes get fixed after years and you wonder if your report had any connection to it whatsoever. It definitely adds to the “Apple doesn’t give a damn about users or software quality” impression I have gotten more and more over the years
boxed 4y ago
There is something worse than what Casey experienced. I filed a feedback on the Contacts API that you can't add a piece of information to a contact card. Literally. You can only read the entire card, set stuff on it (not ALL the stuff, just some random subset!) and then write it. What happens to all the data you can't set and can't read? REMOVED This means their Contacts API, if used to add any information, leads to data loss. The reply? "Works as designed". I explained to them that this is catastrophic data loss and that how it was designed isn't really relevant. Still got "works as designed".
- 1123581321 4y ago
  That limitation isn’t ideal, but wouldn’t you know it right away with another read, during development before production data involvement?
  - boxed 4y ago
    No, the altered fields are totally hidden from me, so the data loss is too.
- mercutio2 4y ago
  Did you write a sample app? I can’t reproduce what you’re describing.
Rebelgecko 4y ago
Last time I tried to use Feedback Assistant, it was basically impossible to report an issue with the Apple Music app on my Android phone. Scrolling was totally broken in both Chrome and Firefox, so I couldn't scroll through the list of things to file a bug against and find the right one. (I don't know if that bug still exists because now for some reasons apple won't let me access Feedback Assistant unless I give them the CVC from my credit card and my phone number to "verify my account"
zaptheimpaler 4y ago
This seems better than the experience at any other big tech though. Even filing a bug is considerably harder on a Google/Amazon product because there's no unified Feedback Assistant app. The experience of firing a bug report off into a black hole and never knowing if/when it was seen is universal as well. It is frustrating but hardly newsworthy or a surprise.. if you feel all feedback requests should be personally investigated by devs/PMs and replied to, maybe talk to the support teams and get a sense of the volume of these reports? It really is impossible.
- svachalek 4y ago
  I'm not sure what Amazon does but when I worked at Google all effort was basically in battening down the hatches to make sure there was absolutely, positively no way to reach a human being anywhere in the company unless you were a business partner of some kind. I stopped answering the phone because every call was someone randomly typing extension numbers out of sheer desperation.
- plorkyeran 4y ago
  Having no way to file a bug is better than pretending to have one which just gets filed to /dev/null. At least that way I don't waste time writing bug reports.
  - zaptheimpaler 4y ago
    My personal stats on feedback assistant: 6 bugs filed 4 of those were fixed or went away. 2 were marked as closed, 2 are marked open but were fixed anyways. 1 is a bug that still affects me occasionally. 1 was a one-off bug in a rare case that i haven't seen since. So my experience is pretty far from it being /dev/null.
    - plorkyeran 4y ago
      My personal stats: 26 filed. 12 open and still relevant 1 that became irrelevant without ever being fixed (an iOS 7 specific problem). 5 fixed bugs in vim bindings in Xcode. 4 clang/libc++ bugs fixed upstream which eventually got pulled into the Xcode version. 4 other bug fixed Reporting vim binding issues during the Xcode 13 beta was a good use of time, but outside of those I'm 4/21 for reporting something to feedback assistant/radar doing anything.
bumper_crop 4y ago
Independent of Apple, I think we need an industry wide of saying "I'm not an idiot, this bug report is real". I've been on both sides (in a moderately used OSS project). The main problem is that the attending doesn't have a good way to filtering the noise from the signal. As a result, the likes of Apple (and the other FAANGs) implement these aggregate-and-discard blackholes for bug reports. "Only a 0.1% increase in crashes? Ship it" is the way the story goes sadly.
- onionisafruit 4y ago
  Maybe after two years of engineering experience you get one “this is real” token to use on an issue. If you use it and the issue actually is real you get the token back. If not you have to do two more years of engineering work to get a new token.
- reidjs 4y ago
  Maybe the best way to do this is to simply befriend an apple engineer? Admittedly this limits the option only to people who work near Apple buildings
- nemothekid 4y ago
  >The main problem is that the attending doesn't have a good way to filtering the noise from the signal. Even if you could filter the noise; there's still a non-zero chance it won't get prioritized. I imagine in Apple's case you could have very real bug reports that only affect 500,000 people and they can't allocate time to fix this. I think there's a tendency to anthropomorphize companies (and OSS projects) as an all knowing person who can fix every problem and has infinite time. In reality there might be 10 people (or in OSS, just 1 person) in the company uniquely capable of triaging your issue in under an hour. The rest would be just as lost as you would be in a new code base and they have to weigh fixing your bug report vs the other opportunities they have (and I'm sure at Apple, closing Radar tickets wont get you promoted). At least in OSS you can dive in yourself.
- teraflop 4y ago
  XKCD was ahead of you by a decade: https://xkcd.com/806/ https://xkcd.com/806/
lastlineX 4y ago
I reported `/usr/bin/CLANG` odd behavior on case-sensitive data volume due to case-insensitive system volume on Mac OS X. Then they replied with "Work as expected; No plans to make the system volume case-sensitive".
RyJones 4y ago
He's right. I submitted a radar[0] in the Xcode toolchain with a very simple repro and it was never acted on - a compile would fail with an error when there was none. It killed our CI system. [0]: https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a5f18 https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a...
- saagarjha 4y ago
  This sounds like it works as designed, unfortunately.
speedyapoc 4y ago
I’ve rarely had my Radars receive any attention unless they were coupled with a TSI. Probably makes sense based on the volume of bug reports that Apple likely receives. The ones that were accompanied with a TSI received attention in 1-3 weeks which seems pretty quick.
ggm 4y ago
Not disagreeing, but observing Apple has a big scale problem: They sell millions, hundreds of millions of things. They are remarkably small in the clue department, so the clue density remains high (this is the MIT theory of clue: the more people you have the thinner the layer of clue has to spread until almost everyone is virtually clueless) View it from their point of view: a spigot will deliver 20,000 important, believable problems to everyones desk like a mailman opening the letter-to-santa sack in December. Every desk: Which one(s) do you look at first? Note, all of them are from people of good intent, not fools. The fools are railing on bulletin boards. BTW I have met Apple engineers who write things. Important things, like the TCP/IP stack for the iPhone. There are two of them. They can't write amazing code, and triage 20,000 bug/improvement inputs at the same time. Sometimes, they're at standards meeting handling fools like me. Sure, there are ass-hats, but the vast bulk of the time Apple is drowning in good input, and has to triage. The example listed here probably affects 1,000 to 2,000 developers, and a critical bug probably has to affect 150,000 people to get traction. or you can spend $99 and prioritize your problem. I had this problem with Microsoft and X509 about 15-20 years ago, (selection of which client certificate to identify a user when there is a certificate subjectName collision) -There was precisely one expert able to fix it, I was ringfenced from them, talking to a consultant and I had the great joy of hearing how much it would cost him to even TRY to get their attention on this problem, which btw, affects the US Government, so its not like it doesn't have "scale" behind it. This is a problem you get, if you have hundreds of millions of customers.
- manmal 4y ago
  Do you think this problem is intractable? I often wonder how Apple can keep posting these quarterly results of a gazillion dollars and still not reply to my Feedbacks for months or years - of things that are very clearly broken! As a dev, I‘m paying them ca 2k per year in hardware costs. Sure sounds like the incentives to really fix this would be there. Apple often claim they are among the most innovative companies. They don’t seem particularly innovative in this space. Eg. the Feedback app looks like it’s been made by a single person over the span of a week.
  - ggm 4y ago
steelframe 4y ago
For what it's worth, bugs that Apple engineers file inside of the company often go into the proverbial "Bit Bucket." When I worked at Apple many moons ago I experienced a really horrible bug when performing a system update. I meticulously recorded all of the context and submitted it directly to the owning team. That team proceeded to ignore my bug report for over a year and then kick it back to me with, "It's been a while. Maybe it's fixed. Try going through your repro steps again with the same hardware and let us know what happens." By then I had swapped out said hardware with more recent stuff I was doing development on. How many people were impacted by that bug in the meantime? No clue, but I guess it didn't hit Apple's bottom line hard enough to warrant anyone on the owning team even bothering to follow my repro steps themselves.
hericium 4y ago
Only once I've got any response to Feedback. After getting it I never opened another case again. Can't recall what exactly was the issue but after macOS update, some bundled software stopped being so friendly and required more actions to achieve a goal. Some built-in functionality stopped being more useful than 3rd party products. I've opened a case to try to tell Apple in what way their update has broken my productivity, pointed out what was needed to get results before the update and how more labor user had to do after the update. Got the most Apple answer possible: "this works as intended". Just another example of Cook's hostility towards users to make Apple more attractive to investors.
- killerdhmo 4y ago
  Have you tried doing the same for Google? Or any other company at this scale. Even though I pay for Google One/Drive/Whatever they call it now, I routinely have data loss level issues and get the "that is not my problem" response.
simonbarker87 4y ago
This is one of the main reasons I don’t develop for Apple’s platforms any more. I’d love to write Swift and leverage all the technology in their ecosystem but when you hit a wall it hits hard and you waste hours, days or weeks searching and hoping someone else hit the same issue and wrote about it. Their docs are dire, their feedback system is terrible and they’ve made essentially zero improvements in the 7 years since I shipped my first app. Web dev has its own frustrations but at least you can find an answer (or ten) quite quickly when you get stuck. As a side note I had a play with the WeatherKit REST API for fun during WWDC this year and got totally stuck. Had a labs session with two engineers (who were great) and it turned out it was an issue with missing docs and seemingly none standard JWT signing process. Their docs (at the time) made no reference to any of this. So things really haven’t changed.
ronyfadel 4y ago
I can offer some thoughts as to why this is the case: - Apple engineers are literally drowning in Radars. - Your F.A. Radar will arrive so late to an engineer (after being filtered by QA) that the engineer is working on new features and marks F.A. bugs as low priority. - The iOS Simulator is a second class citizen.
- giantrobot 4y ago
  These are likely the exact issues. For the past several years for OS releases Apple sets priority deadlines. There's a date where all P1 bugs need to be closed/moved, and so on until near the scheduled release which is "zero bugs". All that means is bugs that didn't get fixed move into the next OS milestone. These deadlines basically preclude late breaking or low priority bugs to ever make an engineer's schedule. The only way is if an exec pushes on the bug or if it turns out to have higher impact than originally thought. Before Feedback Assistant bugs could come in from AppleCare support or developer relations. These could be some of the worst bugs to get assigned because they would be filled with extraneous details but not a crash or spin trace that would actually be useful.
zionic 4y ago
No shit. Fun fact: 3 major releases of TvOS have functioned such that if you navigate to App Store/search and hit siri “Xyz app” Siri (global) appears and tries to take you to said app. If you want to use dictation, you must swipe down and select the text input field. You know, because navigation to search wasn’t enough context.
rvdl 4y ago
Does anyone have any ideas on how Apple could solve this, without just hiring thousands of people? What process or system could be used to triage and reply to tens of thousands of these types of tickets without a corresponding linear increase in staff?
- yurishimo 4y ago
  They make enough money to hire all those people. Maybe pull in some extra contractors until the queue is manageable and then staying on top of it wouldn’t be as bad?
- cromka 4y ago
  Community. Crowd sourcing. Some transparency – as in “democracy” – in prioritization of the issues.
- knweiss 4y ago
  Feedback and bug reports (exception: security) should be public and users should be able to vote. Apple then could prioritize much better. Also, take a look at their user forums: They are full of bug reports with hundreds of users having the same problems - and nothing happens. I really wish they would react much better with official acknowledgments, references to open bugs, workarounds, etc. It is depressing how much collective time is wasted.
zionic 4y ago
[flagged]
jmbwell 4y ago
It sounds like the same guy who had the workaround also believed using a TSI might have been worthwhile. I see no reason to take his guidance on one point and not the other.
Shank 4y ago
It's definitely broken for one-off reports, but in the last beta period (for iOS/iPadOS 15), they actually made some changes. There are user visible "Resolution" and "Recent similar reports" fields. I actually submitted a few feedbacks and saw them change from "Recent similar reports: none" to "Recent similar reports: more than 10" and then "Resolution" actually did change to "fixed in an upcoming release of iOS". At least two feedbacks I submitted got responses to them, which actually got me an email asking for more information on one. I don't think the system is perfect by any stretch. But it definitely has improved, and Apple does read them. The catch is that for esoteric issues -- especially ones that say "Recent similar reports: none", publicizing them and asking people to submit feedback if they can reproduce the issue will likely help prioritize it. Esoteric crashes /are/ harder to diagnose. Minority issues are also lower on the totem pole for any org. I don't want to excuse Apple here -- it does suck, and it does need to keep improving, but last beta round was seriously an improvement over the past.
nnurmanov 4y ago
Not only Apple, I send this email to EU Commissioner, I heard numerous cases when FB support completely ignored cases. There is even a post on Reddit of a guy, who managed to resolve his case by buying an Oculus gadget. Just today I heard a case with Upwork. I am trying to understand here, what is this? A corporate policy? A resource shortage? When you buy a car and it is broken, you can go to court and seek resolution there, but when you have a social account with a large user base or an Upwork account that brings money, where do you go? Shouldn’t companies have a standard flows to support people? Would you as EU impose some rules?
irjustin 4y ago
Apple's true feedback mechanism seems to be class action lawsuits. It's the only time I've seen consistent change/response.
saagarjha 4y ago
The best way to file feedback is to 1. file a good report in Feedback Assistant, then 2. tweet about it. The second step is crucial.
fritigern 4y ago
michelb 4y ago
I think Apple pushes out whatever is on their internal roadmap, and if it works for most of the users, it's fine. If not a serious issue, it may never be fixed. There are somewhat serious/annoying issues that have been there for multiple years but are mostly relevant for power users, or issues that do not contribute to the bottom line, and thus will never be fixed. Even if their own apps do not work together nicely, tough luck. Hope that your issues will be fixed in the next major OS release. I think that it is a problem with their mode of operating and the fact that fixing the majority of bugs will take longer than pushing out a v1 of a new product or service. Also, fixing these bugs will probably mean that teams have to talk to each other, and I really have no idea if that is a reality at Apple. Given the last few software releases it doesn't seem that way. I have a bunch of issues with Monterey that, while some are VERY annoying, do not prevent me from being productive. I also have zero expectation they will be fixed.
Aqua_Geek 4y ago
My laptop somehow overwrote its primary disk encryption keys (i.e. It basically crypto-shredded all my data). I filed an issue with Apple and was met with radio silence for a year. The response that came back was effectively, “do you still have that device, and is it still broken?”
worik 4y ago
"Documentation that, um, exists; and when it exists, it shouldn’t suck." Wouldn't that be nice! I recently moved from Swift/SwiftUI to Dart/Flutter in my professional life. My hobby times I spend in Rust. Of the three only Rust documentation has code snippets with the standard library documentation. Apple, Google: Bigger than big, why not even try?

174 points by goranmoomin 4y ago

wilg 4y ago

It's really a terrible experience. Especially since no one else can see it and simply upvote it. Instead everyone has to do the busy work all over again.

junofan 4y ago

Feedback Assistant is not a support channel. It also is not a new name for Radar. You can find support channels under “Requesting Support”: https://developer.apple.com/bug-reporting/ https://developer.apple.com/bug-reporting/ You are not limited to 2 technical support incidents per year. You can purchase more. I think it’s pretty fair.

suzzer99 4y ago
Just out of curiosity - how much to they cost?
- 1123581321 4y ago
  Apple: Additional TSIs are available for purchase in either a 2-pack for 99 USD or 5-Pack for 249 USD (or in local currency where available) in the Code-Level Support section of your account. TSIs purchased separately expire one year from the date of activation. Seems like you save a few pennies per incident with two packs unless you really need an odd number.
  - onionisafruit 4y ago
    What weird pricing. Why not just make them $50 each? Or $49 if they have a policy that prices end with the digit 9.
    - paranoidrobot 4y ago
      Because it raises the barrier to entry and probably has a serious impact on the number of issues raised.
    - Reason077 4y ago
      Forcing multiple-unit pricing likely increases sales. You probably came to the purchase page just needing one. But you’re probably 𝖽̶𝖾̶𝗌̶𝗉̶𝖾̶𝗋̶𝖺̶𝗍̶𝖾̶ motivated enough to pay extra for a bundle of two if you have to! You’ll justify it by telling yourself “I might need the second one later”, but I’ll bet a lot of them end up going unused. Raising the entry price slightly perhaps also makes people think a little harder about whether they really need to use a TSI or whether other support channels (Stack Overflow? Reddit?) might be more appropriate.
      - jandrese 4y ago
        But why would you ever buy they 5 pack? Is the purchasing a real hassle? At least with the 2 pack you are probably only going to waste one.
        smalley 4y ago
        I could imagine a corporate customer who might be slightly less cost sensitive but have employees that would prefer not to go through a purchase order approval process multiple times might be where purchases like that get made
- dfabulich 4y ago
  https://developer.apple.com/support/technical/ https://developer.apple.com/support/technical/ > Additional TSIs are available for purchase in either a 2-pack for 99 USD or 5-Pack for 249 USD (or in local currency where available) in the Code-Level Support section of your account. TSIs purchased separately expire one year from the date of activation.
iancarroll 4y ago
I’ve only ever filed one or two of these “technical support incidents” but even though it sucks to pay for support — they have some very good engineers answering these tickets, and in one case they got a bug fix for an API shipped pretty quickly.

whatever1 4y ago

Apple does not need active feedback mechanism. It just needs a list of gotchas to avoid for their next generation of products. Their customers of previous products can go f off or buy the new products.

cambo 4y ago

For all the hate Microsoft gets, this is one area where they've got it right. Microsoft's dev support framework, while not directly interacting with MS engineers (usually), the community of MVPs, Regional Directors, and even now the occasional Dev note in the opensource work MS is doing on github, has lead to a great ecosystem of support. This trickles down to Stackoverflow, the old Alt.Net crowd (and the associated .NET user groups that still persist), and the MS dev blog'o'sphere mean this type of issue is much rarer. *edit: oh and I forgot the UserVoice pages, where the community can vote on issues, and they'll get assessed by the product teams.

onionisafruit 4y ago
They eventually got it right. I remember being a sysadmin circa 1999 and having to pay to file a bug report with Microsoft. IIRC if they determined it was a real bug you got your money back.
gnicholas 4y ago
I had the exact opposite experience with UserVoice pages, at least the one for Accessibility. Someone requested that MS integrate my startup's reading technology into MS Word/Outlook/etc on the Accessibility UserVoice. This suggestion gained steam and was the top-rated suggestion for years. MS never engaged with the suggestion, and when I later asked an accessibility person why this was, they told me that the UserVoice is staffed by outside contractors, and that it's not one of the more important places they look for feedback. This was consistent with what I saw, which was that they didn't engage with the most popular suggestions on the Accessibility UserVoice — they just ignored them. I think it's pretty lousy that they set up a page to solicit feedback (especially accessibility feedback) and don't pay attention to it. It causes people to waste time describing issues, asking for help, and voting on other suggestions. A year or two ago they got rid of the UserVoice page, and they now tell people to use Twitter to make suggestions.
gary_0 4y ago
I posted an obscure MS C++ compiler bug to their Web feedback thing, and it got acknowledged and fixed relatively quickly. Whining and complaining over on the r/cpp subreddit also tends to get the polite attention of the relevant Microsoft people (some of whom are mods).

hamburglar 4y ago

I’ve had the same experience reporting bugs every single time. You never ever get a response and simple bugs languish for literal years with no action. Eventually, they sometimes get fixed after years and you wonder if your report had any connection to it whatsoever. It definitely adds to the “Apple doesn’t give a damn about users or software quality” impression I have gotten more and more over the years

boxed 4y ago

There is something worse than what Casey experienced. I filed a feedback on the Contacts API that you can't add a piece of information to a contact card. Literally. You can only read the entire card, set stuff on it (not ALL the stuff, just some random subset!) and then write it. What happens to all the data you can't set and can't read? REMOVED This means their Contacts API, if used to add any information, leads to data loss. The reply? "Works as designed". I explained to them that this is catastrophic data loss and that how it was designed isn't really relevant. Still got "works as designed".

1123581321 4y ago
That limitation isn’t ideal, but wouldn’t you know it right away with another read, during development before production data involvement?
- boxed 4y ago
  No, the altered fields are totally hidden from me, so the data loss is too.
mercutio2 4y ago
Did you write a sample app? I can’t reproduce what you’re describing.

Rebelgecko 4y ago

Last time I tried to use Feedback Assistant, it was basically impossible to report an issue with the Apple Music app on my Android phone. Scrolling was totally broken in both Chrome and Firefox, so I couldn't scroll through the list of things to file a bug against and find the right one. (I don't know if that bug still exists because now for some reasons apple won't let me access Feedback Assistant unless I give them the CVC from my credit card and my phone number to "verify my account"

zaptheimpaler 4y ago

This seems better than the experience at any other big tech though. Even filing a bug is considerably harder on a Google/Amazon product because there's no unified Feedback Assistant app. The experience of firing a bug report off into a black hole and never knowing if/when it was seen is universal as well. It is frustrating but hardly newsworthy or a surprise.. if you feel all feedback requests should be personally investigated by devs/PMs and replied to, maybe talk to the support teams and get a sense of the volume of these reports? It really is impossible.

svachalek 4y ago
I'm not sure what Amazon does but when I worked at Google all effort was basically in battening down the hatches to make sure there was absolutely, positively no way to reach a human being anywhere in the company unless you were a business partner of some kind. I stopped answering the phone because every call was someone randomly typing extension numbers out of sheer desperation.
plorkyeran 4y ago
Having no way to file a bug is better than pretending to have one which just gets filed to /dev/null. At least that way I don't waste time writing bug reports.
- zaptheimpaler 4y ago
  My personal stats on feedback assistant: 6 bugs filed 4 of those were fixed or went away. 2 were marked as closed, 2 are marked open but were fixed anyways. 1 is a bug that still affects me occasionally. 1 was a one-off bug in a rare case that i haven't seen since. So my experience is pretty far from it being /dev/null.
  - plorkyeran 4y ago
    My personal stats: 26 filed. 12 open and still relevant 1 that became irrelevant without ever being fixed (an iOS 7 specific problem). 5 fixed bugs in vim bindings in Xcode. 4 clang/libc++ bugs fixed upstream which eventually got pulled into the Xcode version. 4 other bug fixed Reporting vim binding issues during the Xcode 13 beta was a good use of time, but outside of those I'm 4/21 for reporting something to feedback assistant/radar doing anything.

bumper_crop 4y ago

Independent of Apple, I think we need an industry wide of saying "I'm not an idiot, this bug report is real". I've been on both sides (in a moderately used OSS project). The main problem is that the attending doesn't have a good way to filtering the noise from the signal. As a result, the likes of Apple (and the other FAANGs) implement these aggregate-and-discard blackholes for bug reports. "Only a 0.1% increase in crashes? Ship it" is the way the story goes sadly.

onionisafruit 4y ago
Maybe after two years of engineering experience you get one “this is real” token to use on an issue. If you use it and the issue actually is real you get the token back. If not you have to do two more years of engineering work to get a new token.
reidjs 4y ago
Maybe the best way to do this is to simply befriend an apple engineer? Admittedly this limits the option only to people who work near Apple buildings
nemothekid 4y ago
>The main problem is that the attending doesn't have a good way to filtering the noise from the signal. Even if you could filter the noise; there's still a non-zero chance it won't get prioritized. I imagine in Apple's case you could have very real bug reports that only affect 500,000 people and they can't allocate time to fix this. I think there's a tendency to anthropomorphize companies (and OSS projects) as an all knowing person who can fix every problem and has infinite time. In reality there might be 10 people (or in OSS, just 1 person) in the company uniquely capable of triaging your issue in under an hour. The rest would be just as lost as you would be in a new code base and they have to weigh fixing your bug report vs the other opportunities they have (and I'm sure at Apple, closing Radar tickets wont get you promoted). At least in OSS you can dive in yourself.
teraflop 4y ago
XKCD was ahead of you by a decade: https://xkcd.com/806/ https://xkcd.com/806/

lastlineX 4y ago

I reported `/usr/bin/CLANG` odd behavior on case-sensitive data volume due to case-insensitive system volume on Mac OS X. Then they replied with "Work as expected; No plans to make the system volume case-sensitive".

RyJones 4y ago

He's right. I submitted a radar[0] in the Xcode toolchain with a very simple repro and it was never acted on - a compile would fail with an error when there was none. It killed our CI system. [0]: https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a5f18 https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a...

saagarjha 4y ago
This sounds like it works as designed, unfortunately.

speedyapoc 4y ago

I’ve rarely had my Radars receive any attention unless they were coupled with a TSI. Probably makes sense based on the volume of bug reports that Apple likely receives. The ones that were accompanied with a TSI received attention in 1-3 weeks which seems pretty quick.

ggm 4y ago

Not disagreeing, but observing Apple has a big scale problem: They sell millions, hundreds of millions of things. They are remarkably small in the clue department, so the clue density remains high (this is the MIT theory of clue: the more people you have the thinner the layer of clue has to spread until almost everyone is virtually clueless) View it from their point of view: a spigot will deliver 20,000 important, believable problems to everyones desk like a mailman opening the letter-to-santa sack in December. Every desk: Which one(s) do you look at first? Note, all of them are from people of good intent, not fools. The fools are railing on bulletin boards. BTW I have met Apple engineers who write things. Important things, like the TCP/IP stack for the iPhone. There are two of them. They can't write amazing code, and triage 20,000 bug/improvement inputs at the same time. Sometimes, they're at standards meeting handling fools like me. Sure, there are ass-hats, but the vast bulk of the time Apple is drowning in good input, and has to triage. The example listed here probably affects 1,000 to 2,000 developers, and a critical bug probably has to affect 150,000 people to get traction. or you can spend $99 and prioritize your problem. I had this problem with Microsoft and X509 about 15-20 years ago, (selection of which client certificate to identify a user when there is a certificate subjectName collision) -There was precisely one expert able to fix it, I was ringfenced from them, talking to a consultant and I had the great joy of hearing how much it would cost him to even TRY to get their attention on this problem, which btw, affects the US Government, so its not like it doesn't have "scale" behind it. This is a problem you get, if you have hundreds of millions of customers.

manmal 4y ago
Do you think this problem is intractable? I often wonder how Apple can keep posting these quarterly results of a gazillion dollars and still not reply to my Feedbacks for months or years - of things that are very clearly broken! As a dev, I‘m paying them ca 2k per year in hardware costs. Sure sounds like the incentives to really fix this would be there. Apple often claim they are among the most innovative companies. They don’t seem particularly innovative in this space. Eg. the Feedback app looks like it’s been made by a single person over the span of a week.
- ggm 4y ago

steelframe 4y ago

For what it's worth, bugs that Apple engineers file inside of the company often go into the proverbial "Bit Bucket." When I worked at Apple many moons ago I experienced a really horrible bug when performing a system update. I meticulously recorded all of the context and submitted it directly to the owning team. That team proceeded to ignore my bug report for over a year and then kick it back to me with, "It's been a while. Maybe it's fixed. Try going through your repro steps again with the same hardware and let us know what happens." By then I had swapped out said hardware with more recent stuff I was doing development on. How many people were impacted by that bug in the meantime? No clue, but I guess it didn't hit Apple's bottom line hard enough to warrant anyone on the owning team even bothering to follow my repro steps themselves.

hericium 4y ago

Only once I've got any response to Feedback. After getting it I never opened another case again. Can't recall what exactly was the issue but after macOS update, some bundled software stopped being so friendly and required more actions to achieve a goal. Some built-in functionality stopped being more useful than 3rd party products. I've opened a case to try to tell Apple in what way their update has broken my productivity, pointed out what was needed to get results before the update and how more labor user had to do after the update. Got the most Apple answer possible: "this works as intended". Just another example of Cook's hostility towards users to make Apple more attractive to investors.

killerdhmo 4y ago
Have you tried doing the same for Google? Or any other company at this scale. Even though I pay for Google One/Drive/Whatever they call it now, I routinely have data loss level issues and get the "that is not my problem" response.

simonbarker87 4y ago

This is one of the main reasons I don’t develop for Apple’s platforms any more. I’d love to write Swift and leverage all the technology in their ecosystem but when you hit a wall it hits hard and you waste hours, days or weeks searching and hoping someone else hit the same issue and wrote about it. Their docs are dire, their feedback system is terrible and they’ve made essentially zero improvements in the 7 years since I shipped my first app. Web dev has its own frustrations but at least you can find an answer (or ten) quite quickly when you get stuck. As a side note I had a play with the WeatherKit REST API for fun during WWDC this year and got totally stuck. Had a labs session with two engineers (who were great) and it turned out it was an issue with missing docs and seemingly none standard JWT signing process. Their docs (at the time) made no reference to any of this. So things really haven’t changed.

ronyfadel 4y ago

I can offer some thoughts as to why this is the case: - Apple engineers are literally drowning in Radars. - Your F.A. Radar will arrive so late to an engineer (after being filtered by QA) that the engineer is working on new features and marks F.A. bugs as low priority. - The iOS Simulator is a second class citizen.

giantrobot 4y ago
These are likely the exact issues. For the past several years for OS releases Apple sets priority deadlines. There's a date where all P1 bugs need to be closed/moved, and so on until near the scheduled release which is "zero bugs". All that means is bugs that didn't get fixed move into the next OS milestone. These deadlines basically preclude late breaking or low priority bugs to ever make an engineer's schedule. The only way is if an exec pushes on the bug or if it turns out to have higher impact than originally thought. Before Feedback Assistant bugs could come in from AppleCare support or developer relations. These could be some of the worst bugs to get assigned because they would be filled with extraneous details but not a crash or spin trace that would actually be useful.

zionic 4y ago

No shit. Fun fact: 3 major releases of TvOS have functioned such that if you navigate to App Store/search and hit siri “Xyz app” Siri (global) appears and tries to take you to said app. If you want to use dictation, you must swipe down and select the text input field. You know, because navigation to search wasn’t enough context.

rvdl 4y ago

Does anyone have any ideas on how Apple could solve this, without just hiring thousands of people? What process or system could be used to triage and reply to tens of thousands of these types of tickets without a corresponding linear increase in staff?

yurishimo 4y ago
They make enough money to hire all those people. Maybe pull in some extra contractors until the queue is manageable and then staying on top of it wouldn’t be as bad?
cromka 4y ago
Community. Crowd sourcing. Some transparency – as in “democracy” – in prioritization of the issues.
knweiss 4y ago
Feedback and bug reports (exception: security) should be public and users should be able to vote. Apple then could prioritize much better. Also, take a look at their user forums: They are full of bug reports with hundreds of users having the same problems - and nothing happens. I really wish they would react much better with official acknowledgments, references to open bugs, workarounds, etc. It is depressing how much collective time is wasted.

zionic 4y ago

[flagged]

jmbwell 4y ago

It sounds like the same guy who had the workaround also believed using a TSI might have been worthwhile. I see no reason to take his guidance on one point and not the other.

Shank 4y ago

It's definitely broken for one-off reports, but in the last beta period (for iOS/iPadOS 15), they actually made some changes. There are user visible "Resolution" and "Recent similar reports" fields. I actually submitted a few feedbacks and saw them change from "Recent similar reports: none" to "Recent similar reports: more than 10" and then "Resolution" actually did change to "fixed in an upcoming release of iOS". At least two feedbacks I submitted got responses to them, which actually got me an email asking for more information on one. I don't think the system is perfect by any stretch. But it definitely has improved, and Apple does read them. The catch is that for esoteric issues -- especially ones that say "Recent similar reports: none", publicizing them and asking people to submit feedback if they can reproduce the issue will likely help prioritize it. Esoteric crashes /are/ harder to diagnose. Minority issues are also lower on the totem pole for any org. I don't want to excuse Apple here -- it does suck, and it does need to keep improving, but last beta round was seriously an improvement over the past.

nnurmanov 4y ago

Not only Apple, I send this email to EU Commissioner, I heard numerous cases when FB support completely ignored cases. There is even a post on Reddit of a guy, who managed to resolve his case by buying an Oculus gadget. Just today I heard a case with Upwork. I am trying to understand here, what is this? A corporate policy? A resource shortage? When you buy a car and it is broken, you can go to court and seek resolution there, but when you have a social account with a large user base or an Upwork account that brings money, where do you go? Shouldn’t companies have a standard flows to support people? Would you as EU impose some rules?

irjustin 4y ago

Apple's true feedback mechanism seems to be class action lawsuits. It's the only time I've seen consistent change/response.

saagarjha 4y ago

The best way to file feedback is to 1. file a good report in Feedback Assistant, then 2. tweet about it. The second step is crucial.

fritigern 4y ago

michelb 4y ago

I think Apple pushes out whatever is on their internal roadmap, and if it works for most of the users, it's fine. If not a serious issue, it may never be fixed. There are somewhat serious/annoying issues that have been there for multiple years but are mostly relevant for power users, or issues that do not contribute to the bottom line, and thus will never be fixed. Even if their own apps do not work together nicely, tough luck. Hope that your issues will be fixed in the next major OS release. I think that it is a problem with their mode of operating and the fact that fixing the majority of bugs will take longer than pushing out a v1 of a new product or service. Also, fixing these bugs will probably mean that teams have to talk to each other, and I really have no idea if that is a reality at Apple. Given the last few software releases it doesn't seem that way. I have a bunch of issues with Monterey that, while some are VERY annoying, do not prevent me from being productive. I also have zero expectation they will be fixed.

Aqua_Geek 4y ago

My laptop somehow overwrote its primary disk encryption keys (i.e. It basically crypto-shredded all my data). I filed an issue with Apple and was met with radio silence for a year. The response that came back was effectively, “do you still have that device, and is it still broken?”

worik 4y ago

"Documentation that, um, exists; and when it exists, it shouldn’t suck." Wouldn't that be nice! I recently moved from Swift/SwiftUI to Dart/Flutter in my professional life. My hobby times I spend in Rust. Of the three only Rust documentation has code snippets with the standard library documentation. Apple, Google: Bigger than big, why not even try?