This a great solution, thanks.
I've come across a problem with the ©
Ⓒ & ®
Ⓡ not appearing in "Android 4.4" and "Gmail App IMAP" in Litmus tests. My own native Gmail App IMAP test on a device worked ok but runs a later version of Android than Litmus. Is anyone else seeing this problem on these clients with this solution?
I have a colleague who has the exact same version of the app looking at the same HTML but with no rendering errors. Just so you know not to waste too much time on this at the moment!
I've been in touch with MS support through the android app and have had this response regarding the blue links and other rendering errors:
Upon further research, it seems like you are not the only one who is affected by this problem. I apologize that it is still affecting you. We are currently working on a way to fix this issue. I know this does not resolve your problem however I hope that the knowledge that we are, and have been, actively working on a fix brings your peace of mind. As this is something we cannot unfortunately resolve at this time I am going to close your ticket. Please keep checking for updates to the Outlook Mobile app and if this issue persists after the upcoming update, or if you experience a new issue, please do not hesitate to reach back out to us. Best wishes and thank you for using Outlook Mobile!
Hi Sumi. Thanks for your reply. Unfortunately these approaches no longer seem to work for me (the fix was also really time-consuming when you have many text links with different styles). Also MS fixed this bug in the app with an update about 7 months ago but now it seems to be back again. Are you seeing this link bug in your emails in the outlook android app too?
It seems like this bug has resurfaced :(
I have version 2.1.138 (24th Jan 2017) on android and am facing the blue links among other problems now. The fix to add a span on every link seems like too much of a time sink to do with the volatility of rendering in updates to this app. Also, I've just tried to apply the fix and it's not working for me. Has anyone else got this bug again? Thanks.