William Kucharski wrote:
1. You have unrealistic expectations as to how interactions with Apple Engineering will go.
Basically it's usually:
Apple Engineering reaches out to ask for more data.
2. You provide the data.
You will be thanked and will hear nothing more1. until a fix is announced at some future date.
Apple will not keep you informed, tell you what they are thinking or otherwise reach out to provide updates except maybe to ask you to test a possible fix. That's simply Apple's culture; even other groups within Apple aren't always updated as to what other groups are working on except on a need-to-know basis.
What you call "going MIA" is the way interactions with Apple Engineering work.
Particularly if it's something they can reproduce in-house, there's no need on their part for further interaction.
Thank you for elucidating the way ENGINEERING (in contrast with Apple Support) collects and uses information they collect in VERY UNUSUAL contacts with end-Users. When a User is contacted by Engineering to collect information in this way, it is because users seem to have a unique problem never seen before, and the Engineers do not understand why it should be happening.
Those Engineers (possibly even the original board designers) will now go back to Engineering labs and attempt to reproduce the problems under similar conditions, with half-a-million-dollars worth of instruments and multiple high-powered experts on hand to measure exactly what is happening, and figure out WHY. They may make field trip or ask for additional samples from current production. They may pry the tops off chips and look at them under a microscope. Whatever it takes to find out WHY.
Then the Engineers will need to determine a fix or work-around, and test it thoroughly. This is an open-ended activity, and Users will NOT be notified of its progress.
In cases like this, Users who provided information DO NOT generally hear back directly, EVER. When the Engineers find the problem, the fixes/work-arounds could be anything. These fixes will be integrated into production in ways determined by standard procedures for changes.
The most obscure would be to introduce changes into the design in current production, and possibly issue a silent "Technical Bulletin" such that Users whose Macs exhibit this problem AND are presented for service are to have boards swapped. If all units that exhibit these symptoms are currently user warranty, there may be no separate program at all.
One of the least obscure would that be a software update is issued so that Users whose Macs are kept up-to-date would find their problems lessen after some (unspecified) update.
Occasionally, the only thing that is changed are specifications or instructions, such that certain activities are no longer supported, or must be done is a certain way in future.