ScrollView: Unsupported top level event "topScroll" dispatched

[znacloud]

Is this a bug report?

yes

Have you read the Contributing Guidelines?

yes

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 8.4.0
npm: 5.3.0
Watchman: 4.7.0
Xcode: Xcode 8.3.3 Build version 8E3004b
Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react-native: 0.50.0.rc1
react: 16.0.0

Target Platform: Android (8.0.0)

Steps to Reproduce

1. launch a scrollview page which has two Image as child
2. scroll this page
   3.show red box: Unsupported top level event "topScroll" dispatched

[hramos]

Can you reproduce the issue using Snack? This step is necessary for people to be able to see and debug the issue being reported.

[znacloud]

Sorry, the target platform should be Android(8.0.0)

[znacloud]

@hramos Sorry, I'm not familiar with Snack。Here is exception stack:

Unsupported top level event type "topScroll" dispatched
extractEvents
ReactNativeFiber-dev.js:3519:22
extractEvents
ReactNativeFiber-dev.js:3298:71
handleTopLevel
ReactNativeFiber-dev.js:3539:64

ReactNativeFiber-dev.js:3560:55
batchedUpdates
ReactNativeFiber-dev.js:2754:26
batchedUpdates
ReactNativeFiber-dev.js:202:35
batchedUpdatesWithControlledComponents
ReactNativeFiber-dev.js:209:34
_receiveRootNodeIDEvent
ReactNativeFiber-dev.js:3559:50
receiveEvent
ReactNativeFiber-dev.js:3564:60
__callFunction
MessageQueue.js:302:47

MessageQueue.js:116:26
__guard
MessageQueue.js:265:6
callFunctionReturnFlushedQueue
MessageQueue.js:115:17

when I remove key props from Image tag which is child of ScollView, this error dispears and show a WARNING instead.

Warning: Each child in a array or iterator should have unique "key" prop

[ifsnow]

@hramos I am having the same problem. I think horizontal scrollview has a trouble in all cases.
It works well on react-native@0.49.5, but this error has occurred since version react-native@0.50.0-rc.0

The following simple code also causes an error when scrolling. tested on API 23(Android 6.0) and 24(Android 7.0).

import React, { Component } from 'react';
import {
  View,
  StyleSheet,
  ScrollView
} from 'react-native';

export default class ScrollViewTest extends Component {
  render() {
    return (
      <View style={styles.container}>
        <ScrollView horizontal>
          <View style={styles.dummy}></View>
        </ScrollView>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
  },
  dummy: {
    flex: 1,
    width: 1000,
    height: 400,
    backgroundColor: 'red'
  }
});

[codeYDH]

@hramos I am having the same problem.

[kelset]

Same issue here, tested on Android 7.1.2 and got this error for multiple events:

Unsupported top level event type "topScrollBeginDrag" dispatched
Unsupported top level event type "topScroll" dispatched
Unsupported top level event type "topScrollEndDrag" dispatched
Unsupported top level event type "topMomentumScrollBegin" dispatched
Unsupported top level event type "topScroll" dispatched
Unsupported top level event type "topMomentumScrollEnd" dispatched

@hramos I don't think it's replicable with Snack because it's related to RN 0.50

[rabingaire]

I also have the same issue !!! Please fix this fast.

[bvaughn]

I believe this is related to changes on the native (UIManager) side and should be resolved with commit fdf0495.

The underlying cause was due to the way UIManager previously registered "default" event types. It was assumed that the first view manager to be loaded via requireNativeComponent would get the default events mixed in with its view-specific events. Unfortunately it turned out that in some cases, code referenced a view manager via UIManager.* before (or outside of) the first requireNativeComponent call, causing default event-types like "topScroll" to be lost.

The fix (fdf0495) was to refactor the native and JS code to explicitly request default event types.

[Kottidev]

@hramos we need to fix it quickly , many apps use ScrollView with horizontal=true

[ide]

Cherry-picked 1b71e03 into 0.50.2, which is now on npm.

[amirkheirabadi73]

I still have this problem into 0.50.2

[awnali]

i also faced same issue and then changed the react-native version from 0.50 to 0.49.* and everything works.

[PetrVasilev]

Yes! I also have this very bad problem, which killed my app

[kelset]

EDIT: actually I still have the issue, probably I didn't properly re-tested until today.

[Omniwheel]

Still having the issue in 0.50.3.