Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImageManipulator.manipulateAsync "Calling bridge.imageLoader is deprecated" warning on RN 0.61.* #6018

Closed
sezginriggs opened this issue Oct 17, 2019 · 3 comments 路 Fixed by #6400

Comments

@sezginriggs
Copy link

馃悰 Bug Report

Environment

iOS, bare React Native 0.61.2, expo-image-manipulator 7.0.0

Steps to Reproduce

The following call to ImageManipulator.manipulateAsync creates warning: "Calling bridge.imageLoader is deprecated and will not work in newer versions of RN. Please update to themoduleForClassAPI or turboModuleLookupDelegate API."

const rotateResult = await ImageManipulator.manipulateAsync( this.state.photoPreviewImageUri, [{ rotate: 90 }], { compress: 1, format: ImageManipulator.SaveFormat.JPEG } );

Expected Behavior

Actual Behavior

ImageManipulator.manipulateAsync creates warning: "Calling bridge.imageLoader is deprecated and will not work in newer versions of RN. Please update to themoduleForClassAPI or turboModuleLookupDelegate API."

Reproducible Demo

@sezginriggs sezginriggs changed the title ImageManipulator.manipulateAsync warning on RN 0.61.* ImageManipulator.manipulateAsync "Calling bridge.imageLoader is deprecated" warning on RN 0.61.* Oct 17, 2019
@cruzach
Copy link
Contributor

cruzach commented Oct 18, 2019

Hi! We recommend using the version of RN pinned with the most recent Expo SDK when in a bare project (right now that's RN 0.59). As for newer RN version, your mileage may vary

We are working on upgrading to RN 0.61 for our next SDK release, so stay tuned for that.

@rogercsg
Copy link

rogercsg commented Dec 4, 2019

i am getting same error:

react-native-cli: 2.0.1
react-native: 0.61.5
Screenshot 2019-12-04 at 3 27 44 PM

@lukmccall
Copy link
Contributor

Hi everyone, I think it'll be fixed by this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants