NativeBase: Style property 'top' is not supported by native animated module

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

I upgraded module to 2.12.2 but now my Form crashes all the time with Style property 'top' is not supported by native animated module error. If Item has floatingLabel property it crashes.

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

Node v10.16.0
npm 6.9.0
native base 2.12.2
react v16.8.3
react-native v0.59.9

Expected behaviour

Item floatingLabel shouldn’t crash

Actual behaviour

Item floatingLabel crashes

Steps to reproduce

Here is the snippet directly from documentation that crashes with Style property 'top' is not supported by native animated module

 <Form>
	<Item floatingLabel>
	  <Label>Username</Label>
	  <Input />
	</Item>
	<Item floatingLabel last>
	  <Label>Password</Label>
	  <Input />
	</Item>
</Form>

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

I only tested Android

Any other additional info which would help us debug the issue quicker.

None.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 12
Comments: 23 (2 by maintainers)

Most upvoted comments

seems like reverting to native-base@2.12.1 remove the warning and make the floating labels working again. only tested on android.

aufamiri on Jul 22, 2019

Crash is still happening with 2.13.0 This time it doesn’t show any error but instead it waits and waits and finally crashes. Can someone please get the bottom of this?

Here is minimum code for a crash. Just add Icon and it crashes with ‘Maximum number of …’

      <Content padder>
        <Form>
	<Item floatingLabel>
          <Icon name='mail' style={{ color: 'gray' }} />
	  <Label>Email</Label>
	  <Input />
	</Item>
	<Item floatingLabel last>
		 <Icon name='mail' style={{ color: 'gray' }} />
	  <Label>Password</Label>
	  <Input />
	</Item>
</Form>
      </Content>

tosbaha on Jul 24, 2019

This repo turned to a heap of bugs lately. I will be dropping it as it requires more maintenance time than it saves

tokict on Sep 30, 2019

Please check out our latest release v2.12.5.

Thank you!

PlabanJr on Aug 16, 2019

I am also facing the same issue. I am on RN version 0.59. I didn’t get any such error earlier, being on the same version. It happened today all of a sudden.

AsthaAmeta on Jul 24, 2019

I am using native base@2.12.1 with react-native-@0.59.9 I am working on a project more than a month with same version but it suddenly give this error while I have found that the prop floating label causing this issue

On Mon, Jul 22, 2019 at 9:44 PM José Silva notifications@github.com wrote:

@blankonn https://github.com/blankonn Are you sure? Because I’m using native-base@2.12.1 with react-native@0.60.4 and floatingLabel and inlineLabel are both not working.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/GeekyAnts/NativeBase/issues/2786?email_source=notifications&email_token=AD7KQPRZ5WLPUEQGUBOK37LQAXPX3A5CNFSM4IFAGAHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2QOS5Q#issuecomment-513862006, or mute the thread https://github.com/notifications/unsubscribe-auth/AD7KQPSNZYRK3R45JOSQO6LQAXPX3ANCNFSM4IFAGAHA .

mubashiralisiddiqui on Jul 22, 2019

OMG I was JUST coming here to report this EXACT same bug! Everything for me is the same except I’m using react-native@0.60.3 and native-base@2.12.1.

Also just to add insult to injury: the inlineLabel property does not work and behaves like fixedLabel

josecarlosns on Jul 18, 2019