KeyboardAvoidingView Warnings

[Ethan0007]

Hi,

I'm using 0.43 react-native it shows warnings when I used KeyboardAvoidingView in my login form.

Please be advised.

#Thanks

[DealPete]

Why was this closed? I'm getting the warnings too. From looking at the source, it appears that KeyboardAvoidingView uses deprecated react-native features.

[Ethan0007]

@DealPete sir, i have a temporary fix on this by adding the this line of code:
console.disableYellowBox = true

[carlesnunez]

Same problem here.

Disabling yellow box is not the clean way OFC, we need some feedback here please.

[yidc]

Is this a bug report?

Yes

Have you read the Bugs section of the Contributing to React Native Guide?

Yes, not stating anything about KeyboardAvoidingView

Environment

react-native -v: v0.45.1
node -v: v6.11.0
npm -v: v5.0.3
yarn --version (if you use Yarn): v0.24.6
Target Platform: iOS
Development Operating System: macOS Sierra
Build tools: VisualStudio Code v.13.1
Steps to Reproduce

1. Start any react-native project that uses KeyboardAvoidingView component inside
2. react-native run-ios --configuration Debug
3. then the warning message is displayed at the screen bottom

Expected Behavior

No warning message related to using KeyboardAvoidingView component should appear

Actual Behavior

Reproducible Demo

https://gist.github.com/spencercarli/dc5d8ea9eafb8a0aaa8f83b2f08d874d#file-keyboardavoidingview-js

1. start a react-native project with this .js file
2. react-native run-ios --configuration Debug
3. then the warning message is displayed at the screen bottom

[hramos]

It looks like the description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

Feel free to open a new issue with the additional information provided. Thanks!

[yidc]

Another similar thread has mentioned that this will be fixed on 0.46, so I will just ignore this from now...

[Ethan0007]

Hi,

I think this is related to this issue and its already fixed in this release.

#14381
a975c1e