-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple's proprietary file formats behave strangely sometimes (MOV, possibly HEIC, m4v, caf, m4a, etc.) #105
Comments
data?path=Attachments/46/06/3DFC540E-5B42-42D1-A064-02D8740F21F5/63658281952__44A78AC2-8827-4B97-8513-BF81F0227D78.fullsizerender.heic |
So SMServer should automatically convert However, I've noticed a weird issue where some images will show up fine while I'm debugging the app (specifically, when I'm using the version of the app that is transferred over to my phone when I do debugging on Xcode), but then they won't show up at all as soon as I package the app for distribution. It isn't a release vs debug configuration issue, since this issue still persists when I use a release configuration while debugging. It isn't a permissions issue, since it shows up regardless of how the app is installed (e.g. as an app store app or as a system app) and regardless of who's running it ( |
The code for handling attachment requests in WebMessage is basically identical to the same code in SMServer, so they probably suffer from the same issues and it makes sense that the same |
Would you be able to provide an example of a specific |
Any video taken through the Camera roll app will have this issue. I was able to get this fixed with the The |
I'll jailbreak my iPad and use it as an SMServer/WebMessage host device and try testing the HEIC image on there too to see if it's a problem with my iPhone 6S. |
Here's another situation |
^ I received this error when trying to play some MOV videos in FireFox
and then one particular MOV file only played as an audio file.
Here is the link to Aziz's first comment on the issue, and all the comments below that one are helpful/insightful too.
==== Ignore this rant section, it isn't relevant to the issue, I'm just upset. It's at the bottom to not interfere with the ticket ====
In a perfect world, everyone is using industry standards like mp3 and mp4 so that things Just Work™, but at Apple, they like to “ Think Different”. This MOV problem shouldn't exist, and the quotes I used in the last sentence should look upright like "this", just like they do on any device that isn't made by Apple. We shouldn't need to use workaround software to use iMessage on other devices (not to say Apple is the only company guilty of this). I understand that exclusives are good and they serve to sell more products. I wouldn't want Halo Infinite to be playable on a PS5, but if I have something as simple as a Blu-Ray movie disk that contains nothing more than a simple video, that disk should be playable on both an Xbox and a PlayStation (and thankfully it is!). If Apple wants to make their live photos and MeMojis only work as intended on their devices, then fine. And if they want to push for standards such as HEIC, that's fine too. But when they use something proprietary like MOV, there should be enough licensing information available to at the very least ensure that their format will behave like any other video file if it gets sent elsewhere (hmm but if only there were a format that already does that). I have similar things to say about lightning vs USB-C and the proprietary SSD's on the older MacBooks (which are now soldered on so it doesn't make a difference). Anyways, sorry for that. I'm done now 😃
==== Rant over ====
The text was updated successfully, but these errors were encountered: