If you've reached this page, it's probably because your "parent-based and owner-based contexts differ".
As we've been iterating on React's "context" feature, we've discovered that the parent-based relationship is more useful than the owner-based relationship, so we're migrating to use a parent-based hierarchy.
In short, the owner of a component is whomever creates the component, while the parent of a component is whomever would be the containing ancestor in the DOM hierarchy. To learn more about the owner relationship, see the docs here: http://facebook.github.io/react/docs/multiple-components.html
In many cases, the owner and the parent are the same node, in which case, no further action is necessary. However, if your owner and your parent differ, you should ensure that the context variables you're using aren't going to break when we switch from owner-based contexts to parent-based contexts. If you're seeing the warning, your component may not be ready for the switch.
NOTE: semantically-equal context variables... In some rare cases, you might have a getChildContext function which is not idempotent or which returns objects using value semantics. For instance, if your getChildContext() returns a random number, you might get a warning like:
Warning: owner-based and parent-based contexts differ (values: '0.91666' vs '0.37677')
...
Such cases are not necessarily a bug, but are probably bad practice. Our recommendation is that you fix these situations to ensure getChildContext returns the same value (triple equals equality) for a particular set of inputs (props/context). That said, as long as your context variables are semantically equivalent, you should be able to update to 0.14 without things breaking.
Frankly I see this as a bug in React and the way it handles context - as this is undocumented at this stage, fair enough - however the behaviour I am seeing is as follows:
TopLevelPage has a context containing the object "branding".
TopLevelPage has a ListView component (React-Native) - which from a high level can be used to render collections.
ListView has a callback which renders components, in this instance Card.
At this stage within the closure we have the correct context and you can see the property branding.
Once the Card component has been created - we lose context and branding becomes undefined - for the sanity of the api I believe the child component should inherit the context within which it is created.