If you have an issue on the public release of yosemite, you can very well talk about it on this list. But you’re mentioning NDA so there’s no real way to figure whether someone can help since we aren’t getting the detail of the issue on the public yosemite release. Since this issue is not on el capitan, as you mention it, there’s no need to talk about it. But since it’s in a public yosemite release, what’s stopping you from talking about it, you dig?
In any case, if you aren’t sure about what you did while talking to Apple representatives, maybe you should consider figuring it out for yourself, as this is more of an existential or human interaction question you have after having done this. Think about it: if you spend a lot of time calling Apple instead of just filing a bug report, you’re only getting a potential support ticket sent to the engineers. If you report the bug through feedback assistant, it goes directly to their bug queuing system, which saves third parties moving the issue up the ladder, and will have someone on it, the more similar bug reports, the more important it will be flagged as being. I should mention that if you’re a developer, you don’t have unlimited direct call services. So you’re effectively depleting direct support in case you have a real issue with apps you’re developing. As in for you feeling bad about contacting apple, this is something out of my scope of relevance. > On 5/07/2015, at 8:45 AM, Christopher-Mark Gilland <clgillan...@gmail.com> > wrote: > > The issue is, I have el Capitan on one of my macs. The mac however which I > was experiencing the problem with was not on El Capitan. It's on Yosemite. > Not the public beta though. > > What I was saying is, I knew that the problem I was facing had been addressed > in El Capitan, but I was unaware that it had been broken in Yosemite. So, on > my Yosemite system, when I couldn't perform the function in question, I > called Apple Accessibility Support to see if maybe there was something I was > missing. After trouble shooting on my Yosemite system, it was determined > that this was an issue which is broken in Yosemite. i was trying to say, I > was put in an awquard position because I couldn't really say anything about > El Capitan having the issue fixed. For that reason, the rep I spoke with > said he was going to send a request to engineering to see, in Yosemite, if > there was anything we missed. > > In the back of my head, I knew! the issue already had! been fixed with El > Capitan, as I don't experience this problem over there. I was saying, I felt > really bad that this poor guy spent his time submitting that ticket, when the > issue already had been addressed in a future release. I just couldn't say, > wait, sir, stop. It's ok, I'll just wait things out. It's fixed in El > Capitan. I just didn't know if you knew a way to do this over here in > Yosemite. > > Honestly, Had I known in the first place that it wasn't working correctly in > Yosemite, I never would have called them to start with. I would have just > waited things out. I was more just under the impression that maybe in > Yosemite, the steps to achieve the process were a little different. I didn't > realize it indeed was an issue there, and so the reason for my call was to > ascertain if that was indeed the case. Was! it really broken, or did I just > not understand how to do it. It was only then, through that call that I > found out this has been an ongoing issue. By the time I knew this though, > the guy was already writing up a report to engineering. > > Does that make more sense? > > Chris. > ----- Original Message ----- >> From: Yuma Decaux <mailto:jamy...@gmail.com> >> To: macvisionaries@googlegroups.com <mailto:macvisionaries@googlegroups.com> >> Sent: Saturday, July 04, 2015 5:52 PM >> Subject: Re: Boy did I get myself in a predicament earlier today! >> >> You mentioned having an issue with Yosemite. Read your own text below: >> >>>>> I'd be curious how you all would a handled this. I was trying to do >>>>> something in Yosemite earlier today. I can't really go into the >>>>> specifics of what. You'll know why in a second >> >> So I gave you a response in context with yosemite. But now you’re saying >> you’re using el capitan. >> >> Where’s the confusion here? >> >> I’m just giving you some pointers. >> >> >> >>> On 5/07/2015, at 7:23 AM, Christopher-Mark Gilland <clgillan...@gmail.com >>> <mailto:clgillan...@gmail.com>> wrote: >>> >>> The reason I called Accessibility was because I am not running the beta of >>> Yosemite, only that of El Capitan, therefore, I should be covered with >>> their support. Second off, I didn't know if this was a bug, or if it was >>> just me not knowing what I was doing. Thirdly, it generally takes >>> engineering a while to write back. In my case, I needed to try getting an >>> answer as quickly as possible. >>> >>> Finally, is it really a bad thing me calling Apple Accessibility since I'm >>> a dev? Does that fulfit my right to ask them questions? >>> >>> Sorry, but now, I'm very confused. >>> >>> Chris. >>> >>>> ----- Original Message ----- >>>> From: Yuma Decaux <mailto:jamy...@gmail.com> >>>> To: macvisionaries@googlegroups.com >>>> <mailto:macvisionaries@googlegroups.com> >>>> Sent: Saturday, July 04, 2015 5:17 PM >>>> Subject: Re: Boy did I get myself in a predicament earlier today! >>>> >>>> Chris, >>>> >>>> I’m not sure what exactly you are trying to achieve in the context of >>>> contacting apple’s general accessibility desk when you can get on with >>>> the developer program, as you’ve mentioned you have, and start bug >>>> reporting on yosemite’s beta program as some might not make the switch >>>> once it goes public, though this is definetely not what is recommended as >>>> the new OS is mainly focused on performance. >>>> >>>> The best method for reporting each of your bugs is to first fill in the >>>> descriptive form offered by feedback assistant, then add an audio example >>>> to demonstrate the issue. Apple’s engineers will immediately find it very >>>> helpful and understand the problem as you explain the process. The fact >>>> that you are sending a feedback form and not talking to a lower level >>>> apple support tech will increase your chances of having the issue resolved. >>>> >>>> Cheers, >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>> On 5/07/2015, at 7:05 AM, Christopher-Mark Gilland <clgillan...@gmail.com >>>>> <mailto:clgillan...@gmail.com>> wrote: >>>>> >>>>> First off, before I say anything, let me start by wishing everyone a very >>>>> very! happy, and safe forth. God bless America! >>>>> >>>>> OK, anyway, here is my concern. I'd be curious how you all would a >>>>> handled this. I was trying to do something in Yosemite earlier today. I >>>>> can't really go into the specifics of what. You'll know why in a second. >>>>> Come to find out, this something worked just fine in Mavericks, but >>>>> apparently Apple broke Voiceover accessibility in this one area within >>>>> Yosemite. Well, the thing is, I didn't realize that it had been busted >>>>> in Yosemite. I thought, like mavericks, it still worked, as this isn't >>>>> exactly the most common feature in the OS that I've had to access. The >>>>> thing is, I am an Apple developer. On one of my test machines, I'm >>>>> running the developer beta preview of El Capitan. In El Capitan, the >>>>> issue I was facing has been fixed. I just happened at the time to be at >>>>> my Yosemite production machine instead. So, I called Apple Accessibility >>>>> to see if maybe I was missing something. It was then determined that >>>>> this has been broken since the official first release of Yosemite. >>>>> >>>>> Well, obviously, I'm on NDA, and from what Developer Support has told me, >>>>> most of the senior advisors in the Accessibility department are not >>>>> devs, therefore, it is advised not to discuss with them any of the stuff >>>>> that is covered under NDA. This means, I couldn't exactly say, no big >>>>> deal, it's fixed in El Capitan. I'll just wait until it's released, and >>>>> all will be golden. The advisor starts to open a ticket feedback case >>>>> request to engineering to figure out if this issue can be fixed in a >>>>> future OSX release. I felt so! bad! On the one hand, I knew he was >>>>> waisting his time doing this, as it has! been fixed, but, yet, I really >>>>> couldn't say anything. >>>>> >>>>> This made me really uneasy. I hate waisting people's time. So, what >>>>> should I have done? I wound up just letting him create the ticket, but I >>>>> feel really bad doing so and bothering engineers with something which >>>>> already has been addressed. >>>>> >>>>> Chris. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "MacVisionaries" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send an >>>>> email to macvisionaries+unsubscr...@googlegroups.com >>>>> <mailto:macvisionaries+unsubscr...@googlegroups.com>. >>>>> To post to this group, send email to macvisionaries@googlegroups.com >>>>> <mailto:macvisionaries@googlegroups.com>. >>>>> Visit this group at http://groups.google.com/group/macvisionaries >>>>> <http://groups.google.com/group/macvisionaries>. >>>>> For more options, visit https://groups.google.com/d/optout >>>>> <https://groups.google.com/d/optout>. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "MacVisionaries" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to macvisionaries+unsubscr...@googlegroups.com >>>> <mailto:macvisionaries+unsubscr...@googlegroups.com>. >>>> To post to this group, send email to macvisionaries@googlegroups.com >>>> <mailto:macvisionaries@googlegroups.com>. >>>> Visit this group at http://groups.google.com/group/macvisionaries >>>> <http://groups.google.com/group/macvisionaries>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "MacVisionaries" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to macvisionaries+unsubscr...@googlegroups.com >>> <mailto:macvisionaries+unsubscr...@googlegroups.com>. >>> To post to this group, send email to macvisionaries@googlegroups.com >>> <mailto:macvisionaries@googlegroups.com>. >>> Visit this group at http://groups.google.com/group/macvisionaries >>> <http://groups.google.com/group/macvisionaries>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to macvisionaries+unsubscr...@googlegroups.com >> <mailto:macvisionaries+unsubscr...@googlegroups.com>. >> To post to this group, send email to macvisionaries@googlegroups.com >> <mailto:macvisionaries@googlegroups.com>. >> Visit this group at http://groups.google.com/group/macvisionaries >> <http://groups.google.com/group/macvisionaries>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to macvisionaries+unsubscr...@googlegroups.com > <mailto:macvisionaries+unsubscr...@googlegroups.com>. > To post to this group, send email to macvisionaries@googlegroups.com > <mailto:macvisionaries@googlegroups.com>. > Visit this group at http://groups.google.com/group/macvisionaries > <http://groups.google.com/group/macvisionaries>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
