You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to RN0.29 and RN0.30 I started getting this unhelpful exception:
'One of the sources for assign has an enumerable key on the prototype chain'
I traced this back to the use of spread syntax in jsx component calls. The error would go away if I specified the individual attributes explicitly. Props in this case is a regular object supplied through an enclosing method (not a jsx this.props)
No, I never actually understood the exception just that it worked before and didn't anymore,but thanks for the suggestion. It might be related to changes that have been made in ReactNative Experimental which was changed significantly between the versions I upgraded and is the primary content for the object where I'm running into the exception.
After upgrading to RN0.29 and RN0.30 I started getting this unhelpful exception:
'One of the sources for assign has an enumerable key on the prototype chain'
I traced this back to the use of spread syntax in jsx component calls. The error would go away if I specified the individual attributes explicitly. Props in this case is a regular object supplied through an enclosing method (not a jsx this.props)
I'm not sure why this suddenly stopped working. Only seems to happen in some cases. Any suggestions?
The text was updated successfully, but these errors were encountered: