Nativebase: `<Content>` components not renders correctly on react-native 0.63.0

[keima]

I have gone through these following points

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

Issue Description

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

node 10.18.0
npm 6.14.3
react-native 0.63.0
react 16.13.1
native-base 2.13.12
XCode 11.5

Expected behaviour

<Content> components renders correctly.

Actual behaviour

<Text>Hi!</Text> is not rendered and output error log below:

Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?
Check the render method of `Content`.

Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.

Steps to reproduce

import React, { Component } from 'react'
import { Container, Content } from 'native-base'

const Foo = () => (
  <Container>
    <Content>
      <Text>Hi!</Text>
    </Content>
  </Container>
)

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

Both.

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

Important

If you want your issue to be looked at quicker, attach a snack reproducible with your issue. Makes it easier for us!

[cristian-rita]

This project is no longer maintained. They don't even make a build from master. Few issues are already fixed there.

[younes200]

Probleme related to change in ScrollView https://github.com/APSL/react-native-keyboard-aware-scroll-view/issues/429 once a PR merge in react-native-keyboard-aware-scroll-view this should be fixed.

[rmgpinto]

@cristian-rita do you recommend other ui lib that's properly maintained?

[codler]

I have the same issue.

[codler]

I have forked the repo to fix this issue.

npm i @codler/native-base

You will need to remove old fonts in Copy Bundle Resources in Xcode after install

[younes200]

Thanks @codler.
Why removing old fonts is required ? I have issues rending font on iOS is it the case for you too ?

[codler]

You will probably get duplicate output file error when building ios, https://medium.com/codespace69/xcode-reactnative-ios-xcode-build-error-with-duplicate-output-file-when-install-new-library-36dfbcb5d223, but if not, then you dont need to do that.

[john-e]

Thanks @codler

[MartinMouritzen]

I guess I didn't do my homework well enough, choosing Native-Base. It does seem a bit abandoned, which makes me sad. I too would like recommendations for UI projects that are maintained.

[spdaly]

@codler Thanks for the effort. Everything worked perfectly.

@MartinMouritzen Agree. I spent A LOT of time looking at a lot of different kits and decided on NB. Unfortunately, this has been my experience with the RN ecosystem. A lot of great libraries/kits/etc that have great promise but fall short.

[muyaszed]

LOL, I don't really realised this repo is kind of abandoned until I had this problem. But really it is quite a nice lib. Somebody should revive this one.

[Aung-Myint-Thein]

I have forked the repo to fix this issue.

npm i @codler/native-base

You will need to remove old fonts in Copy Bundle Resources in Xcode after install

I saw you forked rnkasv too. can I just install it but not the whole native-base? @codler

[vadympetryshyn]

This project is no longer maintained. They don't even make a build from master. Few issues are already fixed there.

Is it really true? New pull requests no longer be merged? I've just started new project with RNB, should I find another UI Kit?

[jacargentina]

@hanykumar https://github.com/APSL/react-native-keyboard-aware-scroll-view/releases/tag/v0.9.2 just released!
Please update dependency and bump for new release ?

[raazatul7]

Is this issue fixed??
Please fix it asap and close it!

[madhumurugan89]

will this issue be fixed ? If not please suggest another UI library for react native

[ilya-bmi]

Please fix the issue!

[Aung-Myint-Thein]

https://github.com/APSL/react-native-keyboard-aware-scroll-view/issues/443#issuecomment-659357780

npm install https://github.com/APSL/react-native-keyboard-aware-scroll-view#v0.9.2

I updated the react-native-keyboard-aware-scroll-view with the command from the comment and <Content> is working again :D Hope this solves you guys too.

[jacargentina]

I've tried @Aung-Myint-Thein but didn't work.

Then i've tried this on my package.json:

  "resolutions": {
    "native-base/react-native-keyboard-aware-scroll-view": "https://github.com/APSL/react-native-keyboard-aware-scroll-view#v0.9.2"
  }

Then yarn install and it worked!
While i wait for a proper native-base release. Cheers!

[Aung-Myint-Thein]

I've tried @Aung-Myint-Thein but didn't work.

Then i've tried this on my package.json:

  "resolutions": {
    "native-base/react-native-keyboard-aware-scroll-view": "https://github.com/APSL/react-native-keyboard-aware-scroll-view#v0.9.2"
  }

Then yarn install and it works!�
While i wait for a proper native-base release. Cheers!

Weird. It is not working for me after fresh npm install. I tried the resolutions method and it is still not working for me. Which React Native, Native Base versions are you using? @jacargentina ?

[jacargentina]

@Aung-Myint-Thein i'm using yarn, not npm (i dont think npm supports the resolutions feature); BTW i'm with rn 0.63 and latest published native-base

[yogesh1623]

Please fix this issue Asap!

[JerakRus]

@sankhadeeproy007
is the repository really failing anymore? and will this critical issue be fixed?

[sankhadeeproy007]

Guys, is there a PR for this anywhere?
I'll do a release quickly if I there's one.

[ankitghosh]

This has been fixed after the latest update! You guys can update the nativebase package and it will work

[sankhadeeproy007]

Thanks to @codler for their help in fixing this.

[Aung-Myint-Thein]

It is working now in my dev but my release apk is crashing upon start with

Name FATAL EXCEPTION: mqt_native_modules
Reason java.lang.ClassCastException: com.facebook.react.bridge.ReadableNativeMap cannot be cast to java.lang.String

Is it happening the same for you guys?..

[nozbwang]

please fix it asap, thank you.
It spends me a lot of time finding my problem is caused by this lovely native-base package. I have to roll back to older native-base version (v2.6.1) so i can continue my work.

[oriharel]

If this repo is not being maintained anymore, maybe Paper?

[Ar7profacex]

@codler Thank you very much, it worked perfectly, greetings from Chile

[impactcolor]

I dumped content

...

To
<>
....

[IamMasterWayne]

+1