[ 
https://issues.apache.org/jira/browse/CB-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627654#comment-13627654
 ] 

Sébastien BUREL commented on CB-2896:
-------------------------------------

Hello,
I need to get the Exif info on the jpeg at the server side and i fall in this 
bug.
I first tried to find a fix but searching in apple documentation i found 
something simpliest.
I very new to IOS and cordova but i would like to share the way i do it:

instead of
   CDVJpegHeaderWriter* exifWriter = [[CDVJpegHeaderWriter alloc] init];
   NSString* headerstring = [exifWriter createExifAPP1:[info 
objectForKey:@"UIImagePickerControllerMediaMetadata"]];
   [exifWriter spliceExifBlockIntoJpeg:data withExifBlock:headerstring];

i do
  NSDictionary *metadata = [info 
objectForKey:@"UIImagePickerControllerMediaMetadata"];
  if (metadata) {
   CGImageSourceRef sourceImage = 
CGImageSourceCreateWithData((__bridge_retained CFDataRef)data, NULL);
   CFStringRef sourceType = CGImageSourceGetType(sourceImage);
                    
   CGImageDestinationRef destinationImage = 
CGImageDestinationCreateWithData((__bridge CFMutableDataRef)data, sourceType, 
1, NULL);
   CGImageDestinationAddImageFromSource(destinationImage, sourceImage, 0, 
(__bridge CFDictionaryRef)metadata);
   CGImageDestinationFinalize(destinationImage);
                    
   CFRelease(sourceImage);
   CFRelease(destinationImage);
 }

Sebastien

                
> Multipart exif tags are not written correctly
> ---------------------------------------------
>
>                 Key: CB-2896
>                 URL: https://issues.apache.org/jira/browse/CB-2896
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.6.0
>            Reporter: Lorin Beer
>            Assignee: Lorin Beer
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> multi-part (complex) tags are not written correctly. this leads to an exif 
> string which is of the correct size (and therefore is not reported as an 
> error) but cannot be read back out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to