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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ANDROID] Heading is undefined after RN upgrade #12

Open
joegoodall1 opened this issue Jun 19, 2017 · 5 comments · May be fixed by #13
Open

[ANDROID] Heading is undefined after RN upgrade #12

joegoodall1 opened this issue Jun 19, 2017 · 5 comments · May be fixed by #13

Comments

@joegoodall1
Copy link

joegoodall1 commented Jun 19, 2017

After upgrading from RN0.39->0.44, heading was coming back as undefined on Android.

This appeared to be because instead of using data.heading (as it says in the README.md) it was just data.

So in case anybody else has the same problem the fix was using this
heading = Platform.OS === 'ios' ? data.heading : data instead of heading = data.heading

@FarhanKhalid
Copy link

+1 Having this issue with iOS also. Creating a project with 0.45 and importing this leads to an
undefined is not an object (evaluating 'RNSimpleCompass.start') from the source code provided.

@juergengunz
Copy link

@FarhanKhalid did you solve this issue?

@aaronbuchanan
Copy link

Looking forward to an update here, been a while since this was reported, anyone made any progress on tracking this down?

@FarhanKhalid
Copy link

@juergengunz No unfortunately I tried but wasn't really able to find a solution. I ended up using an older version of RN for this. The latest one that is working for me is 0.41. Since all my other libraries are compatible I am just going to continue using this version for now.

@zsajjad
Copy link

zsajjad commented Jan 18, 2018

I have updated the react-native version and fixed this issue of different behaviours on android and iOS. Check my fork https://github.com/zsajjad/react-native-heading

@zsajjad zsajjad linked a pull request Jan 18, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants