React-native: Error : 'ScrollView' has no propType for native prop 'RCTScrollView.onScrollAnimationEnd' of native type ' BOOL'

[jpca999]

I'm stuck on this error.

{
"name": "app-20",
"version": "0.0.0",
"description": "Hello Expo!",
"author": null,
"private": true,
"main": "node_modules/expo/AppEntry.js",
"dependencies": {
"axios": "^0.16.2",
"expo": "^20.0.0",
"latlng-to-zip": "^0.0.1",
"lodash": "^4.17.4",
"react": "16.0.0-alpha.12",
"react-addons-update": "^15.6.0",
"react-native": "^0.47.2",
"react-native-calendar": "^0.12.3",
"react-native-calendars": "^1.5.8",
"react-native-communications": "^2.2.1",
"react-native-easy-toast": "^1.0.6",
"react-native-elements": "^0.16.0",
"react-native-flexbox-grid": "^0.3.1",
"react-native-google-place-autocomplete": "^0.3.0",
"react-native-indicator": "^0.6.7",
"react-native-loading-spinner-overlay": "^0.5.2",
"react-native-maps": "^0.16.2",
"react-native-modal": "^3.1.0",
"react-native-modal-datetime-picker": "^4.11.0",
"react-native-multiple-select-list": "^1.0.4",
"react-native-progressive-input": "^1.0.3",
"react-native-segmented-control-tab": "^3.2.1",
"react-native-signature-pad": "^0.0.8",
"react-navigation": "^1.0.0-beta.11",
"react-redux": "^5.0.6",
"redux": "^3.7.2",
"redux-form": "^5.0.1",
"redux-persist": "^4.9.1",
"redux-thunk": "^2.2.0"
}
}

{
"expo": {
"name": "thapp",
"description": "thapp",
"slug": "thapp",
"privacy": "unlisted",
"sdkVersion": "20.0.0",
"version": "1.0.5",
"orientation": "portrait",
"primaryColor": "#cccccc",
"icon": "./assets/icons/app.png",
"loading": {
"icon": "./assets/icons/loading.png",
"hideExponentText": false
},
"packagerOpts": {
"assetExts": ["ttf", "mp4"]
},
"ios": {
"bundleIdentifier": "com.thapp.exp",
"supportsTablet": true
},
"android": {
"package": "org.thapp.exp",
}
}
}

I also tried replacing react-native package with "react-native": "^0.47.2", But didnt work.

Is this a bug report?

(write your answer here)

Have you read the Contributing Guidelines?

(Write your answer here.)

Environment

Steps to Reproduce

(Write your steps here:)

1.
2.
3.

Expected Behavior

(Write what you thought would happen.)

Actual Behavior

(Write what happened. Add screenshots!)

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

[courage-liberty]

me too.
It is an error in FlatList.

Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in.

Check your code at App.js:8.
    in App (created by AwakeInDevApp)
    in RCTView (at View.js:113)
    in View (created by AwakeInDevApp)
    in AwakeInDevApp (at registerRootComponent.js:33)
    in ExpoRootComponent (at renderApplication.js:35)
    in RCTView (at View.js:113)
    in View (at AppContainer.js:100)
    in RCTView (at View.js:113)
    in View (at AppContainer.js:121)
    in AppContainer (at renderApplication.js:34)

import React from 'react'
import { FlatList, StyleSheet, Text, View } from 'react-native'

export default class App extends React.Component {
  render () {
    return (
      <View style={styles.container}>
        <FlatList
          data={[{key: 'a'}, {key: 'b'}]}
          renderItem={({item}) => <Text>{item.key}</Text>}
        />
      </View>
    )
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: '#fff',
    alignItems: 'center',
    justifyContent: 'center'
  }
})

[philipjc-apacio]

Feels like this has just decided to break on me this morning, right before a deadline. Any help, please??

[chrise86]

This occurs for me when using the CLI to build and run the app, however it does not happen when running via Xcode.

[philipjc-apacio]

This is happening while using Expo and create-react-native-app

[courage-liberty]

My issue is like the EXPO client, too.

[nokwin]

Found the possible solution!

1. Bump expo version in package.json to 21.0.2
2. Bump react-native version in package.json to 0.48.4
3. Remove node_modules
4. npm install or yarn install
5. Change sdk version in app.json to 21.0.0
   ...
   ScrollView is working AGAIN! :)

[giulianok]

Same here. I created a new fresh app using create-react-native-app. The following dependencies have been installed

"dependencies": {
  "expo": "^20.0.0",
  "react": "16.0.0-alpha.12",
  "react-native": "^0.47.0"
}

I started getting that error, infinitely, causing the browser consume a lot of memory.

I've tried updating to 0.48.4 with this command react-native-git-upgrade 0.48.4, it installs the react native v0.48 but it doesn't update package.json and/or app.json.

Finally, I end up with the same solution as @nokwin:

"dependencies": {
  "expo": "21.0.2",
  "react": "16.0.0-alpha.12",
  "react-native": "0.48.4"
}

And make sure you have the following sdkVersion in app.json

"expo": {
  "sdkVersion": "21.0.0"
}

[PabloTeari]

I had the same problem, solved! Thank You @nokwin @giulianok.

[andrespch]

thaaanks @nokwin

[marcfielding1]

Hmm thats not solving it for me, anybody else stuck?

[andrespch]

did you update to xcode 9 @marcfielding1 ? I think I needed to yarn cache clean after changing (and installing) the dependencies to get it to work

[marcfielding1]

Hmm I'm using NPM actually, let me try cleaning that cache out... Ah actually I'm on node 8 so npm self cleans.

[marcfielding1]

Ahh hold on xCode 9! Need to do system update, back in a while.

[andrespch]

hm I actually asked you because I only got this issue after updating to xcode 9, so if you had not updated yet, that might be a sign that your issue is a different one, and that's why this solution is not working.

[marcfielding1]

Ok so for me, it's actually an issue with the Google Places Autocomplete package. If I remove that now it's good, tis still very odd it just suddenly started of out nowhere.

[courage-liberty]

I tried it, but opening project of expo client has become the time-out.
Because I have not yet updated iOS, it may be a cause.

[rubencodes]

OH MY GOD this worked! Thanks y'all, this issue popped out of nowhere for me as well and right on a demo day 😵 Better late than never!

[igorbrandao]

I confirm that @nokwin / @giulianok solution works
Thank you so much for figuring this out! Started to flip when I updated expo and got this error earlier today...

[courage-liberty]

Person of expo saying "repairs it early" in Slack.
I wait for a while.

[thelostspore]

Does anyone know why this happened and can anyone agree on a remedy? I've tried all solutions proposed up to this point and still see the error. E.g. updated app.json, cleared all possible caches (npm start -- reset-cache, rm -rf .expo, rm-rf node_modules), restarted packager, pinned dependencies to versions recommended, even uninstalled the Expo Client app and reinstalled). Using xcode 9 & ios 11. Also on deadline, depending on this tool. Any help is much appreciated.

[andrespch]

what's exactly the error you are getting? @thelostspore

[thelostspore]

@andrespch A very similar error to the one posted (native code & js code out of sync). I've seen similar issues and SO's and I'm mostly curious about the root cause...seems like this has occurred for other minor version updates of react-native. I've managed to get my app running but I couldn't pinpoint the exact remedy.

Does anyone know if react-native 0.48.4 now only works with expo sdk 21.0.2? If so the CRNA Versions readme could probably use a note. (Also, I wonder if RN 0.48.0 works fine with expo sdk 21.0.0 and if there is a compelling reason to update to latest patch versions).

[Martian2Lee]

@nokwin Thanks bro!

[mik-rom]

I have this same error and I don't use expo. Anyone found a solution?

[sujitpk-perennial]

Most of faced issue with expo. I am not using expo. It was working for me. Suddenly it starts showing this danger red screen. I am using

Xcode: 8.0
iOS: 10
npm: 5.5.1

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.