UNNotificationAttachment convenience init method seems to be checking for supported file types based on the extension of the file URL provided as a constructor parameter. This seems to be sub-optimal at best and incorrect at worst.
Is this is a known issue for which a bug already exists?
The best way to ensure a problem is known and that a bug exists is to file one yourself.
Bug Reporting: How and Why? has tips on creating a successful bug report.
Even if the issue were to be known, additional bug reports let our teams to gauge the impact of an issue and help prioritize a fix for it.
