Your boss told you to use xyz technology? You (and others, if necessary) should have convinced him otherwise. If you can't and his decision is a bad one, you have to be the one that says no. That's right -- it's your job on the line, not his. If you signed up to be vp of IOS software, you're in the wrong if something is broken in IOS software. That's why you need to learn to say "no", not only to clients, but to coworkers as well. If that's absolutely not possible, it's time to put on your big boy/girl pants and take the blame because you couldn't fix a problem that you knew existed.
If you're in a situation where different people are telling you different things, then it sounds like you get to decide the specific implementation. It's even probable that those different people telling you different things are really giving you their unsolicited opinion, rather than micromanaging your career.
I think it's cowardly to avoid responsibility for what you sign your name to.
The fact of the matter is that you can do your job extremely well, do everything right by any rational measure, have a strong political position, and yet still get screwed by unanticipated or uncontrollable external and internal forces, up to and including nonsense of others on the executive team, especially in an organization with a poor/weak/incompetent CEO or equivalent.
It happens all the time.
It's pretty easy and cheap to make a blanket "it's always your fault" statement, but back here in the real world it's typically much more nuanced and complicated.
As far as having multiple people telling me what to do, I was mostly referring to my time in the military. Take my word for it, I wasn't expected to choose a specific implementation (unless it was theirs), and they were definitely not offering friendly advice!
There is an even larger difference between being a person who is capable of recognizing when their employer is wrongfully blaming something on them and the person who constantly blames things on other people.
I don't know if applies in this situation or not. For all I know this guy could have personally written bad code for maps. The point is, universal statements such as "there is never it's not my fault at the executive level" are just plain false. It is an executive's fault if his subordinates do shitty work, but if the executive's boss ordered something that was impossible to accomplish with a given set of time, manpower, and resources then there is a good possibility that it isn't his fault. He might have to take the fall for it, but at the end of the day if that's what happened, then he knows he did the best he could and therefore shouldn't give a shit what anyone else thinks.
I love my job, I also loved having the opportunity to provide leadership and guidance for others. It is because of the love I had for my job that I would accept responsibility only for the things that are actually my fault(which includes the actions of my subordinates.) I understand that as a supervisor there's always the chance that I would get fired, demoted, or otherwise punished for a superior's mistakes, but that doesn't make it my fault or responsibility unless I actually made a mistake.
Steve Jobs can say "there is no it's not my fault" because at Apple, the buck stopped with him. I don't recall hearing anyone ever telling Steve Jobs that he couldn't do something, or overriding his design decisions. For lower levels of leadership, such as I experienced, there were about 50 different people who would constantly tell me what to do, even though only one person was actually tasked with doing so. Sometimes, my orders were poorly thought out. Sometimes they even contradicted orders given by other people. In situations like these, as I stated before, only a coward would accept the blame without evaluating the specific situation beforehand.