capacitor: bug: Image is lost if choosing not to edit for Camera plugin on Android

Bug Report

Capacitor Version

💊 Capacitor Doctor 💊

Latest Dependencies:

@capacitor/cli: 2.0.1

@capacitor/core: 2.0.1

@capacitor/android: 2.0.1

@capacitor/electron: 2.0.1

@capacitor/ios: 2.0.1

Installed Dependencies:

@capacitor/electron not installed

@capacitor/cli 2.0.0

@capacitor/core 2.0.0

@capacitor/ios 2.0.0

@capacitor/android 2.0.0

[success] Android looking great! 👌 Found 7 Capacitor plugins for ios: com-darryncampbell-cordova-plugin-intent (2.0.0) cordova-admob-plus (0.35.0) cordova-plugin-appavailability (0.4.2) cordova-plugin-file (6.0.2) cordova-plugin-file-transfer (1.7.1) [success] iOS looking great! 👌

Affected Platform(s)

  • Android
  • iOS
  • Electron
  • Web

Current Behavior

Original Image is not returned when you select a phone from gallery and continue without editing it.

Note: This is almost exactly the same issue as #2020. I see it is working totally fine in case of taking a picture but not in case of selecting an image from gallery.

Expected Behavior

If no edit is performed after selecting an image from gallery, original image should be returned

Sample Code or Sample Application Repo

const image = await Camera.getPhoto({
	quality: 90,
         allowEditing: true,
	resultType: CameraResultType.Uri,
});

console.log(image.webPath); // nothing is returned

Reproduction Steps

Call Camera Plugin code Camera.getPhoto(..) choose option (Select an Image from Gallery) when edit screen pops up, click the X without making any edits No image is returned

Other Technical Details

npm --version output: 6.4.1

node --version output: v10.10.0

pod --version output (iOS issues only):

Other Information

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 19 (3 by maintainers)

Most upvoted comments

this has been fixed in @capacitor/camera, would be available on next release.

I confirm this issue still exist on capacitor 3.0.0

@sandstrom I can confirm this issue still exists in Capacitor 2.4.1