Email photo as attachment, not embedded, in iOS 14

I'm in the same boat as everyone else - this update is a retrograde step and if anyone at Apple is listening, please revert back to sending images as attachments - without having to record a video. Thank you

I too am really irritated by this unannounced change. I am a photographer and need to have control of my images. If this had been announced, the outcry would have nipped it in the bud. But, I would have saved no end of time wasted wondering what I was doing wrong. Smarten up, Apple - I have loved my iPhone for years but this is enough to send me elsewhere.

[Edited by Moderator]

Again.

An opposing viewpoint is not spam.

Apple's awareness is not really in dispute.

Just thought you should know what we're facing here.

Which, for clarity, is the reality of this community not being the proper place for this conversation.

Feedback for Apple goes here >>> http://www.apple.com/feedback/

Just thought you should know what we're facing here.

So let's sum up where this issue stands. The following is not in dispute...

** An iOS change was made that alters how attached images are seen at the receiver's end.

** This change has angered and frustrated many users. Likely many more then have spoken up here.

** Despite 50+ plus pages of "me too" & "yeah.. can't you see how upset i am" & "make him stop saying that", the issue is not yet resolved.

** It is maddening to some of you that Apple won't answer your "why" questions.

** It is maddening to some of you that Apple won't "fix it NOW!!!!!!!"

Conclusions?

The issue will not be resolved here. Nobody from Apple will come here and update the community on what Apple's plans are.

Despite insistent demands to the contrary, that won't happen. Why? The purpose of this Apple managed community is not to debate policy and decisions made or not made. I am confident that Apple is aware of the feelings being shared. I am also confident Apple will not engage on policy and decisions made here and I am grateful they don't.

The feeling of "not being heard" is moot. There is a huge difference between being heard and getting an answer.

Apple may very well do nothing. Apple may make another change that restores the functionality being discussed.

If you want to continue believing that posting what you post, that often gets removed, is furthering your cause... carry on.

As a graphic professional, I depend on being able to attach multiple images in my workflow. This is ridiculous apple. Should I just throw your devices away?

I CANNOT add ONE IMAGE AT A TIME.

This is CRAZY

konrad138 wrote:

As a graphic professional, I depend on being able to attach multiple images in my workflow. …

I CANNOT add ONE IMAGE AT A TIME.

This is CRAZY

Who said you need to «add ONE IMAGE AT A TIME»?

Admittedly, that very tiny subset of email clients (consisting of a single email client and its derivatives, so far as anyone’s reported research has found) does prevent users from performing bulk attachment operations (such as bulk-saves), under many circumstances. So, such email clients may cause you to need to «add ONE IMAGE AT A TIME», at the receiving end.

However, that very tiny subset of email clients is not under Apple’s control.

Apple you really ruined a good think you had. I am beyond frustrated with the way attachments work on my phone now. Fix this immediately it is dumb and annoying and whoever thought it was a good idea should be fired because this wastes so much of my time.

I agree! I have a business account with 50 phones, most of them send in their receipts via the phone. Saw a smart-*** Apple Tech correct everyone saying they are not embedded and ignored the question.

1st - changing pictures to embed in the emails is a pain. Change back to an attachment.

2nd - Apple also has changed their file format from JPG to HEIC, which Windows cannot open in its native photo viewer. WHY?

Samsung is an option Apple, we do not have to stay with you.

CRBbama wrote:

I have the same issue. Very frustrating that this capability was eliminated. I need this capability or a different phone.

If you read here, you’ll find all there is to find on workarounds and how to contact the owners of the errant programs, as well as contacting Apple.

Hint: the «capability» has never been «eliminated». All email clients—with the exception of a very tiny subset—allow all their users the ability to perform bulk attachment operations (such as bulk-saves) for all emails generated by Apple Mail.

The exception is that very tiny subset of email clients that exhibit an apparent inability to provide their users with the ability to perform bulk attachment operations (such as bulk-saves) under certain International Internet Standards’ compliant conditions.

(If you are experiencing this issue, you, apparently, use one or more email clients from that very tiny subset [consisting of a single email client and its derivatives].)

I don't believe you're listening properly to the complaints, since I know you are capable of reading beyond the level of the superficial, or pedantic, or the command-line. There's a problem with the way that a subset of users receive attachments from those using Apple Mail that didn't used to present as a problem. The update amounted to a downgrade for users expecting to be able to communicate with clients in the way to which those clients were accustomed, and hoped not to have to contact the clients to tell them to contact the developers to have them change their software so that this upgrade wouldn't create unfortunate hurdles. That's a terrible ask, and from any individual customer, would have the result of changing absolutely nothing, which the customer would know.

You might find some solace in stating that -- technically -- attachments are attachments, or that the subset should be written off as adhering to outdated specifications. I wouldn't agree that such a subset being affected by this change should be of no concern and should be of no consideration for those of us who proudly expect our apple software to minimize challenges in communication so that business can be conducted properly -- for the mere fact that they represent a minority of users, or even in such cases that they, hypothetically, might represent a very small minority. It's still a hurdle where no hurdle existed before.

In my specific case, as I think I commented before, the subset of such users who are represented among my customer base is not an irrelevant subset whatsoever, but probably represent a majority. It's true that many are older or less technically savvy, but this is not a sector of users I care to write off as unworthy of proper functionality, or who I should tell: why doncha just call bill gates about it then?

That would be absurd, and I think you'd agree that your dug-in heels have put you into a very absurd position where you'd rather not *hear* what people are saying, and would rather see no problem at all than to acknowledge a problem that, evidently, does exist, for however small and irrelevant you believe the subset to be. There might then be a more useful and substantial discussion at hand, for the very small subset of users who are taking the time to contribute here.

As I pointed out, axelnelson, this «hurdle» has «existed» many, many times «before.»

Many, many times before the iOS 14 update.

It has occurred many, many times throughout the years!

Since the root problem is a reticent manufacturer of a very tiny subset of email clients (consisting of a single email client and its derivatives), that hasn’t updated their standards compliance for more than a decade, it sure seems to be high time that said manufacturer be held accountable for the problems their lack of standards compliance has caused their users.

At the very least, their lack of standards compliance shouldn’t be holding the rest of the world back!

Back when I worked within the corporate and governmental sectors, I always researched out the root causes of issues we were having, and always went to the responsible parties to get things corrected.

While I did, indeed, have times when one company would blame another (such as a large data mining company that blamed an issue on Microsoft Windows [a very minor player, as far as the data mining company was concerned]), I would always pursue and research the issue until I knew what was actually going on.

(In the case of that data mining company, I was able to demonstrate that the issue was only in how they were coding their software for Microsoft Windows. They then had a corrected version of their software to me within a month.)

The best thing about getting the root cause corrected is that it helps the greatest number of people!

For instance, by getting that data mining company to correct their code, all their Microsoft Windows users were benefitted!

So why are you bothering to respond then?

In the seemingly futile belief that eventually contributors will read and heed.

Venting ends at some point. This discussion has passed that point.

Meaningless beating of the dead horse does not add to the value of this community and IMO, harms it.

New users coming here looking for answers see these multiple page discussions that do not cause change and likely do not return.

Forgive me for trying to prevent that from happening.

Those who enjoy a good online fight should go elsewhere.

I am going to be seeking alternatives if this doesn’t get fixed. My workflow has been hampered. Apple devices are suppose to work for me, not me work for apple’s whims in changing software

Ok. Best of luck.

konrad138 wrote:

I am going to be seeking alternatives if this doesn’t get fixed. My workflow has been hampered. Apple devices are suppose to work for me, not me work for apple’s whims in changing software

Do as seems best for you.

I have exact the same problem since i use iOS 14 and it is totally frustrating an i "downgrade" in my opinion. And in my opinion an update should be an improvement. I need this feature a lot for my daily work and anyway sending an email as plain text in 2020/2021 is a disgrace. Considering that apple always advertise with their innovation.