Tell the OP it isn’t possible in an answer and get downvoted
I'm not sure why you're operating under the presumption that saying "No" and/or giving a short answer automatically means a down vote. This is not the case and I can site you several personal examples:
It's perfectly fine to say "no" and providing a succinct answer is always best.
Post an alternative that is easier and built in to the iOS system and
There's nothing wrong with providing an alternative and it is highly encouraged to do so. What I see wrong (IMO) with your answer is that it is literally a copy and paste of the Apple support document you link to in the beginning. If you were going for "easier" a simple link to the support document would have sufficed.
To me, this practice evokes an image like that of a student who copies and pastes 9 pages of source in a 10 page paper and cites it to remain compliant and "complete" the requisite assignment. Block quoting what amounts to the entire answer is what leads to this perception.
So I’m a bit stuck. What should be done?
What would have made this a much better answer is if you provided the salient details (probably 4 or 5 bullet points) you wrote with a link to the full source.
A tech writer at Apple did a great job writing up that support document. I up voted the question as it's a good one, albeit the answer is probably not what the OP wants to hear. Your answer however, couldn't get an up vote from me because there was no originality to it (i.e. you translated it to lay terms so we could all understand it, or you summarized it so we didn't have to scroll 3 pages to get the solution, etc.).
Just my 2¢