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

You're attempting to include a mixin that is either null or not an object #120

Closed
gkrinc opened this issue Nov 15, 2016 · 7 comments
Closed

Comments

@gkrinc
Copy link

gkrinc commented Nov 15, 2016

When importing:

import TableView from 'react-native-tableview';

I'm getting this warning:

ExceptionsManager.js:82Warning: ReactClass: You're attempting to include a mixin that is either null or not an object. Check the mixins included by the component, as well as any mixins they include themselves. Expected object but got undefined.

Versions

  • react-native: 0.35.0
  • react-native-tableview: 1.6.0
@roysG
Copy link

roysG commented Nov 20, 2016

+1

@PaulRBerg
Copy link

+1

@aksonov
Copy link
Owner

aksonov commented Nov 21, 2016

Does it work with earlier RN versions? @nyura123 could you check?

@iRoachie
Copy link
Collaborator

No progress on this?

@chetstone
Copy link
Contributor

chetstone commented Nov 30, 2016

@aksonov I've had this issue with RN 0.32 and 0.33. I worked around it by removing the require of NativeMethodsMixin, which is apparently unused.

Weirdly, though, yesterday I cloned my project to another machine and that machine doesn't need that workaround, it works with b85f0d4. I cannot figure out why. The code should be identical on both machines. The new project had a new install of all node modules, but when I removed and reinstalled all node modules on the old machine, it didn't change the behaviour --- it still needs the workaround.

UPDATE: Now the installation on the new machine is acting the same as the old -- it needs the workaround. Weird caching issue? Or just me being confused?

I see another project had to remove NativeMethodsMixin but then they had to add it back in. Go figure.

@iRoachie
Copy link
Collaborator

iRoachie commented Dec 8, 2016

@chetstone The warning goes away for me when removing the require native mixins. Can we just make the change? I wouldn't want to do an entire fork just for one line.

I made a pr. pull #127

@iRoachie
Copy link
Collaborator

Resolved in #129

@iRoachie iRoachie closed this as completed Dec 4, 2017
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

No branches or pull requests

6 participants