Skip to content
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.

fix for breaking iOS header change in RN 0.40.0 #544

Merged
merged 1 commit into from
Jan 6, 2017

Conversation

danieldkim
Copy link
Contributor

For the breaking "iOS native headers moved" change in RN 0.40.0. Fixes #541. Addresses facebook/react-native#11725.

@rt2zz rt2zz merged commit 048e741 into react-native-camera:master Jan 6, 2017
@rt2zz
Copy link
Collaborator

rt2zz commented Jan 6, 2017

🥂

@danieldkim
Copy link
Contributor Author

Thanks! 🥂

@rt2zz
Copy link
Collaborator

rt2zz commented Jan 6, 2017

@danieldkim is this change backwards compatible with older react-native versions?

@danieldkim
Copy link
Contributor Author

danieldkim commented Jan 6, 2017

@rt2zz I haven't tested that yet, tbh. however, the description of this change in the RN release notes suggests not ...

@danieldkim
Copy link
Contributor Author

i'll do a quick test ... hold, please

@danieldkim
Copy link
Contributor Author

@rt2zz it's not. generates a compiler error in Xcode with 0.39.2.

@danieldkim
Copy link
Contributor Author

Relevant discussion at facebook/react-native#11614. It looks like the RN team has decided not to support the old import style leaving it to library developers to deal with branching (if they choose).

@michalmmm
Copy link

Thanks a lot!

@rt2zz
Copy link
Collaborator

rt2zz commented Jan 6, 2017

Thanks for looking into that @danieldkim. Looks like v1 is coming up :D

@merapi
Copy link

merapi commented Jan 6, 2017

guys, you integrated breaking change into master without changing version... (my project stopped working)

@rt2zz
Copy link
Collaborator

rt2zz commented Jan 6, 2017

@merapi are you installing react-native-camera from github master? this is risky, we are back to shipping semi-regular releases so I would recommend install v0.4

I suspect there are a large number of people in your situation however, so lets do this: I will make a new branch next with this change, and npm publish v1.0.0-alpha1

rt2zz added a commit that referenced this pull request Jan 6, 2017
@danieldkim
Copy link
Contributor Author

@rt2zz OK, I've been pointing my package.json at master to get the latest and greatest. master should now only get critical bug fixes and I should track the next branch for shiny new stuff?

@danieldkim
Copy link
Contributor Author

I mean I have no choice since I am on RN 0.40.0, so if that isn't the case my only option to make sure I always get the latest shiny new is to regularly sync to my fork, which would seem kinda backward.

@rt2zz
Copy link
Collaborator

rt2zz commented Jan 6, 2017

@danieldkim ya this is non-ideal but most of the ecosystem is not rn 0.40 ready yet (maps, branch off the top of my head), so I think we are going to see more users point to master on <0.40 than vice-versa. Going to be pain either way.

In the short term I am going to merge all new features against #next branch, so I think if you want to more or less continue how things were I would point you installation to lwansbrough/react-native-camera#next. Hopefully this will be short lived.

@danieldkim
Copy link
Contributor Author

@rt2zz great, thanks that'll make things easier for me. fyi, maps has pushed their fix for this out.

@ksrawat
Copy link

ksrawat commented Feb 27, 2017

@danieldkim is it possible to draw a rectangle/bound line around barcode area when detected? I know we get bound data, could you please simplify this for me if possible. would appreciate this.

hulajesus added a commit to hulajesus/react-native-camera that referenced this pull request Jul 23, 2017
guimello added a commit to OriginalMy/react-native-camera that referenced this pull request Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants