TIF file be damaged with getting info of XmpSchemes

GroupDocs.Metadata Product Family
1

We have wrote the test code as below, we only try to get the value with ‘schemes.DublinCore.Source’ and save the format to the destination path, and we not get any exception, but the TIF file is damaged. (We are using the latest API 17.9.0)

using GroupDocs.Metadata;
using GroupDocs.Metadata.Formats.Image;
using GroupDocs.Metadata.Xmp;
using System;
using System.Windows.Forms;

namespace MetadataTest
{
class Program
{
static void Main(string[] args)
{
string licenseFilePath = @“C:\Users\User\Desktop\MetadataTest\MetadataTest\MetadataTest\License\GroupDocs.Metadata.lic”;
string sourcePath = @“C:\Users\User\Desktop\MetadataTest\MetadataTest\MetadataTest\Source\Flowerboy_orginal.tif”;
string destinationPath = @“C:\Users\User\Desktop\MetadataTest\MetadataTest\MetadataTest\Destination\Flowerboy_orginal.tif”;

        License lic = new License();
        lic.SetLicense(licenseFilePath);

        TiffFormat format = new TiffFormat(sourcePath);
        if (format == null)
        {
            return;
        }

        try
        {
            XmpSchemes schemes = format.XmpValues.Schemes;
            if (schemes == null)
            {
                return;
            }

            if (schemes.DublinCore.Source != null)
            {
                string str = schemes.DublinCore.Source;
            }

            format.Save(destinationPath);
        }
        catch(Exception e)
        {
            MessageBox.Show(e.InnerException.Message.ToString());
        }
    }
}

}

damaged.PNG (29.8 KB)
test tif.zip (886.5 KB)

2

@Glority_Developer,

Sorry to hear that you are facing such an issue. We have logged this issue in our internal tracking system under ID "METADATANET-1932"and will let you know once the issue is resolved.

4

@rida.fatima Thanks for reporting it to the internal tracking system. We are close to the release date of our product. Do you have any idea when this issue will be fixed? Or how we can see the status of this issue in the internal tracking system, so I can know the progress of this issue?

5

@Glority_Developer,

We apologize for the inconvenience but unfortunately you cannot see the status of the issues. All the issues reported by you are expected to be fixed by the next monthly release of the API. We have asked our product team about the expected date for the next release and will inform you accordingly.

6

@Glority_Developer
In addition to the above mentioned reply, You can also look into our Priority support service if your tasks need immediate attention.

7

Please also check this issue after you finish the “METADATANET-1932” issue.

8

@Glority_Developer,

Thanks for your response. We are delighted to inform you that issue filed as METADATANET-1925 will be fixed in GroupDocs.Metadata for .NET 17.10 which is expected to be released on 2nd October. When the release will be onboard, we’ll notify you here.

9

@Glority_Developer,

The issue you have found earlier (filed as METADATANET-1932) has been fixed in this update.

10

Thanks. We have verified in v17.10.1, it is fixed.

11

@Glority_Developer,

Thanks for the confirmation.