Nativebase: Unsafe legacy lifecycles warring for Pickers

[ismarosmanovic]

I have gone through these following points

• [] Check latest documentation: https://docs.nativebase.io/
• [] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
• [] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
• [] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
• [] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
• [] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

Adding picker component to any page throws following warning:

---

Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.

%s uses %s but also contains the following legacy lifecycles:%s%s%s

The above lifecycles should be removed. Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks, Styled(PickerNB), getDerivedStateFromProps(), ,
UNSAFE_componentWillReceiveProps,

---

node, npm, react-native, react and native-base version, expo version if used, xcode version

native-base: 2.13.5,
expo: 34.0.4

,

Steps to reproduce

Just add Picker to the page.

Is the bug present in both iOS and Android or in any one of them?

Only on IOS

[yitelee]

same here, IOS only

[mccordgh]

same issue as well:
native-base: 2.13.5
expo: 32.0.0

The picker still seems to work as normal, I just get the warning every time I navigate to that screen.

[halstjas]

I have also noticed this with the version of react-native-keyboard-aware-scroll-view v0.8 which is being bundled with the latest version of native-base which is using react deprecated lifecycle method componentWillReceiveProps can you please update to use library to latest v0.9.1 which resolves this issue.

[GitHubGreg]

Same here (same as OP).

[dsusviela]

Same

[siliconavengers]

same. We hope someone will submit a PR for this warning.

[sankhadeeproy007]

Can we try it with the latest version 2.13.7 and see if the issue still persists?

[mccordgh]

@sankhadeeproy007 Still having the issue with 2.13.7

package-lock.json:

in-app screenshot:

warning from terminal:

[09:52:54] Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.

%s uses %s but also contains the following legacy lifecycles:%s%s%s

The above lifecycles should be removed. Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks, Styled(PickerNB), getDerivedStateFromProps(), ,
  UNSAFE_componentWillReceiveProps,

[Brayden967]

Exact same problem for me, any updates?

[sankhadeeproy007]

Fixed in 2.13.8