Bug #77142 [Fbk->Opn]: exif_read_data

Edit report at https://bugs.php.net/bug.php?id=77142&edit=1 ID: 77142 Updated by: cmb@php.net Reported by: alerinpoland at gmail dot com Summary: exif_read_data -Status: Feedback +Status: Open Type: Bug Package: EXIF related Operating System: Ubuntu PHP Version: 7.2.12 Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2019-03-25 00:56:00] alerinpoland at gmail dot com View: https://www.pic2map.com/vcvemm.html File: https://drive.google.com/file/d/1Dte3rjfICNj8-ZYSbHX3qFgNURwYjbGU/view?usp=sharing ------------------------------------------------------------------------ [2019-03-24 19:01:20] kalle@php.net Could you please re-upload the file somewhere? ------------------------------------------------------------------------ [2019-01-16 10:34:40] server at masa10 dot info I also faced the same problem. As a result of examining this bug, I found out that there is a problem with Exif of the Huawei product. The problem lies in the datatype of the Document Name field of Exif. Whereas Exif standard requires ASCII type, Huawei product writes with UNDEFINED type, so an error occurs. Therefore, we forcibly change the data type of DocumentName item from ASCII to UNDEFINED with Exif data editing software. By doing so, even PHP7.2/7.3 can successfully read Exif of Huawei product. This issue has already been reported to Huawei. ------------------------------------------------------------------------ [2018-12-26 08:03:17] tedferenc at hotmail dot com Also fails on Linux 7.2.13 ------------------------------------------------------------------------ [2018-12-23 08:35:57] tedferenc at hotmail dot com Fails on Linux PHP version 7.2.11 and 7.2.10. On 7.2.10 exif_read_data gives this error "corrupt EXIF header: maximum directory nesting level reached" on 7.2.11 that error does not exist but still no GPS data, exiftool does display it camera is Panasonic DMC-TZ70 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=77142 -- Edit this bug report at https://bugs.php.net/bug.php?id=77142&edit=1