Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@sensiblearts Thank you for providing this PR. I understand your needs to save the original image. However, I am not confident enough to take a public API change that only adds new features to Android right now. I will take some time to review the possibility of doing this on iOS side and maybe provide a solution to benefit both platforms. If you do need this urgently, I suggest you to make the change on your own fork. Or you can use the earlier version of the image picker.

I have created an issue to track this flutter/flutter#30788, you can follow the issue and get updates on progress of this fix.

I will leave this PR open for now, if you'd like to provide the changes on iOS and also adding tests to this change, you are welcome to do so and I am happy to review the changes.

@cyanglaz Thank you for the quick reply.

I will eventually get to iOS version myself, as well as tests, but it will be a month or so.

However, I just discovered that I need to make a breaking change, and I doubt whether it will be general enough to pull; consequently, I am assuming that I will be maintaining my own fork indefinitely.

FYI, here is the breaking change in my fork:

Problem to solve:

• I need both scaled and original files retained
• I need the original filename even if it was selected from a folder

Whereas I can derive the original filename from the scaled filename in case of capture, I cannot do this if the user picks a random file in a folder. Therefore, the simplest way to get this string is to have the plugin return it.

So, I modified image_picker.dart to return a custom class:

class PickedFile {
  PickedFile({this.original, this.scaled, this.video});
  File original;
  File scaled;
  File video;
}

class ImagePicker {
 //...
  static Future<PickedFile> pickImage({
 /...
    final Map<dynamic, dynamic> pickedPath = await _channel.invokeMethod(
      'pickImage',
 //...
   );
    final PickedFile pf = PickedFile(
        original: pickedPath["original"] == null
            ? null
            : File(pickedPath["original"]),
        scaled:
            pickedPath["scaled"] == null ? null : File(pickedPath["scaled"]),
        video: null);
    return pf;
  }

  static Future<PickedFile> pickVideo({
//...
    final Map<dynamic, dynamic> pickedPath = await _channel.invokeMethod(
      'pickVideo',
   //...
    final PickedFile pf = PickedFile(
        original: null,
        scaled: null,
        video: pickedPath["video"] == null ? null : File(pickedPath["video"]));
    return pf;
  }
}

This code is in a separate branch called 'picked_file' and it is solving this problem described above.

Thanks for your time,
DA

@sensiblearts
I am going to close this PR if you don't mind since it is not complete yet. (No iOS implementation). You can follow the issue I created for progress on this. Also you are more then welcomed to open a new PR if you get the iOS code ready! Thank you again for the contribution!