Skip to content
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

Can't open iOS 18 generated photos #363

Open
hadess opened this issue Oct 1, 2024 · 4 comments
Open

Can't open iOS 18 generated photos #363

hadess opened this issue Oct 1, 2024 · 4 comments

Comments

@hadess
Copy link

hadess commented Oct 1, 2024

Using the current GIMP Flatpak, and opening files generated by an iOS 18 device, I get either:
Loading HEIF image failed: Invalid input: Unspecified: Metadata not correctly assigned to image
or
Loading HEIF image failed: Invalid input: Unspecified: Too many auxiliary image references
as error messages.

iOS 18 support is one of the things that the 1.18 branch of libheif adds:
https://github.com/strukturag/libheif/releases/tag/v1.18.0

735387a says libheif is "abandoned" forcing < 1.18.0 versions, but doesn't link to why newer versions aren't considered (either here, or in the GNOME GitLab).

@brunvonlope
Copy link
Collaborator

brunvonlope commented Oct 1, 2024

libheif module stopped to be updated in the stable flatpak probably due to API incompatibilities. See: #338 (comment)

We use the most recent libheif on the beta one.

@hadess
Copy link
Author

hadess commented Oct 1, 2024

libheif module stopped to be updated in the stable flatpak probably due to API incompatibilities. See: #338 (comment)

I couldn't find an upstream bug report, or anything else that would explain what this "incompatibility" was. Do you have a reference for it?

@brunvonlope
Copy link
Collaborator

brunvonlope commented Oct 1, 2024

I couldn't find an upstream bug report

Long response: in the linked MR I observed that building libheif with the version mentioned in the MR description was making GIMP unable to export to HEIC and AVIF. First, I just ignored the bug but them flathub bot was becoming annoying so in a further MR I "abandoned" the module to avoid flathub creating new automatic MRs.

I don't know the reason for it so I can't explain "why". If I know, I would pushed a fix. The "API" thing mentioned in this issue is merely a guess. And I didn't opened any issue about this.

@hadess
Copy link
Author

hadess commented Oct 11, 2024

The beta worked for my needs. I would say that we should leave this open until beta is the stable branch, so it registers as a known issue, and we can work on backporting whatever fixes are necessary if somebody wants it fixed properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants