I don't blame you one bit, I'd feel the same way. This is a software and hardware problem. I've worked software long enough to know that FCA will never be able to fix these software bugs. Some unique hardware problems are triggering this particular software bug. If you are familiar with Boolean logic the number of possible paths goes exponential, fast! If the software is not VERY carefully written, organized and commented it becomes a steaming pile of spaghetti-pretzel rat's nest real fast. Then the idiot managers prescribe adding ridiculous amounts of SAR (system analysis and recording) bogging down the processors and making debugging close to impossible. I lived that life for 25 years.
I've experienced two software gremlins in my Rebel so far in just under 5,000 miles. Just sitting at an idle in park the horn goes off and the emergency flashers come on, for no known reason. Somewhere in that huge pile of spaghetti a path was followed to trigger an Auto Fill Assist feature, but why the emergency flashers? Probably no one will ever be able to figure it out. At least these aren't Boeing 737 Maxs, where such glitches can have more serious effects.
Imagine designing an aircraft, the French Airbus, where the pilot and the copilot each have independent side stick controls. Neither can visually see what the other's control stick is doing. If the pilot pushes his stick full forward and the copilot pulls his control full back, there is no feedback to indicate that the two are inputting opposite control commands. And the computer processor makes a decision to hold full back stick as the copilot commands. And a perfectly good plane free falls 50,000 feet into the Pacific Ocean killing everyone on board.
And you take the same plane and do a low pass at an airshow. Applying full power the computer overrides you and says nope, we're going to land. And land you do about a quarter mile past the end of the runway in a heavy forest. The planes explodes in a ball of fire.
