You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assessing the HEIC files uploaded with Seafile, file structure is not HEIC instead they are JPEG files with HEIC file extension. Using these files in other applications as HEIC results with an error, and files can be used as JPEG instead.
So Seafile iOS app does not upload the original raw HEIC images directly, rather still processes them as JPEG and uploads them as JPEG just with HEIC extension.
Assessed the files with several other tools as well, below is a summary.
The file starts with a JPEG header and includes typical JPEG metadata, including EXIF data. Extended analysis shows no HEIC-specific markers, confirming that the file is entirely a JPEG despite its .HEIC extension. Thus, the file is a misnamed JPEG file.
The text was updated successfully, but these errors were encountered:
With app release version 2.9.31 I observed that the photo upload with disabled option "Upload HEIC" results in files with .JPG file ending and as HEIC file format.
Updated code is in file Pod/Classes/SeafUploadFile.m method convertHEICToJPEGAtURL line 664.
We truly appreciate you pointing this out. In the upcoming version, which will be released shortly, we have addressed the format issue to ensure consistency between the file extension and the actual file format.
Assessing the HEIC files uploaded with Seafile, file structure is not HEIC instead they are JPEG files with HEIC file extension. Using these files in other applications as HEIC results with an error, and files can be used as JPEG instead.
So Seafile iOS app does not upload the original raw HEIC images directly, rather still processes them as JPEG and uploads them as JPEG just with HEIC extension.
Assessed the files with several other tools as well, below is a summary.
The text was updated successfully, but these errors were encountered: