text:
ScrollView: Unsupported top level event "topScroll" dispatched

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

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

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

Sorry, the target platform should be Android(8.0.8)

@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 <unknown>     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 <unknown>     MessageQueue.js:116:26 __guard     MessageQueue.js:265:6 callFunctionReturnFlushedQueue     MessageQueue.js:115:17

@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'
  }
});

@hramos I am having the same problem.

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

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

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

Cherry-picked https://github.com/facebook/react-native/commit/1b71e03932f44e212b297b2c1e02100b6de74b93 into 0.50.2, which is now on npm.

I still have this problem into 0.50.2

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

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

Updating to 0.50.3 fixed it for me - thanks for the quick fix!

Still having the issue in 0.50.3.

Here too, upgrading to 0.50.3 don't solved the problem for me.

I'm also facing the same error "unsupported top level  event type "topScroll" dispatched" when using scrollEnabled: true for TabNavigator in react-navigation which internally is a ScrollView
This error occurs in latest react-native@0.50.3 but works fine in react-native@0.49.0 (which is expo's latest supported version). Hence no issues in snack / can't show demo in snack @hramos

0.50.3 hasn't solved the problem for me either.
I'm also finding that while I can still work on the emulator (as long as I don't scroll) the signed APK I'm building crashes when run on a device. Has anyone else experience this or is it an unrelated problem?

You can use ViewPagerAndroid instead of ScrollView but this works only with Android devices.

Seeing this bug on iOS as well on 0.50.3

Thanks @Rom96, that's a great temporary workaround for me as I'm only working on Android 👍

Hi @booleanBoy / @rambabusaravanan / @donnes / @Omniwheel
I'm confused by the fact that you're still seeing this issue and I'd like to get a little more background on what you're doing.
Taking ScrollView and the "topScroll " event type as an example. ScrollView registers its native code using requireNativeComponent which mixes in a set of shared, default event types which in this case includes the "topScroll" event (among others). Provided you're accessing ScrollView from the react-native-implementation then I think this should just work.
Are you by chance loading the view some other way? eg directly accessing UIManager["ScrollView"]?

Same issue.
Unsupported top level event type "topScrollBeginDrag" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topScroll" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topScroll" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topScrollEndDrag" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topMomentumScrollBegin" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topScroll" dispatched
ExceptionsManager.js:65
Unsupported top level event type "topMomentumScrollEnd" dispatched
ExceptionsManager.js:65

@Amurmurmur Please see my question above your comment.

Same issue using react-native 0.50.3 and
https://github.com/react-native-community/react-native-tab-view
With scrollEnabled true.
Problem does not appear with 0.49.3

@bvaughn I use FlatList the following way:
  render () {
    let items = this.props.children

    return (
      <FlatList
        style={styles.list}
        data={items}
        onMomentumScrollEnd={this.onScrollEnd}
        keyExtractor={(item) => items.indexOf(item)}
        pagingEnabled
        horizontal
        renderSeparator={() => null}
        showsHorizontalScrollIndicator={false}
        showsVerticalScrollIndicator={false}
        directionalLockEnabled
        renderItem={this._renderItem} />
    )
  }

I noticed this when fooling around with react-navigation (w/ RN 50.0.3). Can reproduce by doing a simple Tab Navigator and doing a press and hold + drag gesture on a Tab. It's pretty easy to setup (I can paste code if needed) so hopefully that helps with reproducing.

@bvaughn As I mentioned before, the following simple code still has an error when scrolling. tested on API 23(Android 6.0) and 24(Android 7.0).
I think horizontal scrollview has a trouble in all cases
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'
  }
});

Same issue. I changed the react-native version in the package.json file and now it works fine:
"react-native": "^0.49.5"

I am getting this error when trying to drag up my bottom tabbar, which shouldn't result in anything happening at all!

I am getting this error when trying to drag up my bottom tabbar, which shouldn't result in anything happening at all!

Same issue.
 "react-native": "^0.50.3"

Same issue on
"react-native": "^0.50.3"
using a horizontal Scrollview for my carousel

Any updates with this issue?
I really need it to be done asap.

I'm also having this issue. There is a modal on the same page that is triggered by a button. If I open the modal and then close it, the Unsupported top level event type "topScrollBeginDrag" dispatched no longer appears and my caurosel works as expected.

We as well experience the same error with v0.50.2. We implemented a pageable horizontal ScrollView. iOS-Simulator works fine. Only Android-Simulator breaks on interaction.

@Sergeypt423 Agreed we are supposed to launch our app by the end of the month and it would be very nice to have it fixed by then T_T

Same issue. Use 0.50.3 version, and only on Android this problem (((

same issue

me too with
"react": "16.0.0",
"react-native": "0.50.3",

temporary solution:
I changed the react-native version in the package.json file and now it works fine:
"react-native": "0.49.5",

me too with
"react": "16.0.0",
"react-native": "0.50.1",

Just to set expectations, I am not aware of anyone looking into this issue. Having been in similar situations in the past, two things that have worked well to get unblocked are forking+fixing the issue locally and contracting an expert.

same issue
"react": "16.0.0",
"react-native": "0.50.3"

Just to set expectations, I am not aware of anyone looking into this issue.

This is mostly true. Dmitry and I have talked about it a few times but neither of us have had time to look into it yet. It's on my wish list for things I'd like to find time to do but I don't know when that will happen yet.
If someone in the community has bandwidth to look into it - that would be ideal.

@bvaughn @ide
I have found the cause of error in react-native@0.50.3 and how to fix it. However, I realized that there was no problem in current master branch, so I think it doesn't make sense to solve the issue in 0.50.3 branch.
current status

ReactNativeRenderer-dev.js : no problem (master)
ReactNativeFiber-dev.js : error (v0.50.3)

the cause of error
Horizontal scrollview uses AndroidHorizontalScrollView instead of RCTScrollView. The problem is that AndroidHorizontalScrollView does not register custom direct events (topScroll, topScrollBeginDrag, ...).
The events should be registered during the initialization of the three modules(RCTScrollView,
AndroidHorizontalScrollView, AndroidHorizontalScrollContentView), but it seems to be a problem.
Adding the following code to ReactHorizontalScrollViewManager solves the problem.
@Override
public @Nullable Map getExportedCustomDirectEventTypeConstants() {
  return createExportedCustomDirectEventTypeConstants();
}

public static Map createExportedCustomDirectEventTypeConstants() {
  return MapBuilder.builder()
    .put(ScrollEventType.SCROLL.getJSEventName(), MapBuilder.of("registrationName", "onScroll"))
    .put(ScrollEventType.BEGIN_DRAG.getJSEventName(), MapBuilder.of("registrationName", "onScrollBeginDrag"))
    .put(ScrollEventType.END_DRAG.getJSEventName(), MapBuilder.of("registrationName", "onScrollEndDrag"))
    .put(ScrollEventType.MOMENTUM_BEGIN.getJSEventName(), MapBuilder.of("registrationName", "onMomentumScrollBegin"))
    .put(ScrollEventType.MOMENTUM_END.getJSEventName(), MapBuilder.of("registrationName", "onMomentumScrollEnd"))
    .build();
}

I think it is necessary to improve the initialization part of ScrollView. I will work on this later.
I hope this helps.

@ifsnow I have modified the file in my node module however the error remains. do I have to recompile from the src?

@MedericPixium Check out this manual first.

Thanks for digging into this issue and sharing your findings, @ifsnow ❤
I'm still concerned that it addresses a symptom without understanding the underlying cause though. As I mentioned in a previous comment, events like "topScroll", "topScrollBeginDrag", etc. are actually supposed to be available for all view manager types by default because of how this code works.
Maybe I'm misunderstanding your comment?

I just ran the open-source RNTester app on Android but was unable to reproduce the error being reported. I ran it from both master and the 0.50-stable branch (where 0.53 was released from). Adding this to the fact that internally (at Facebook) we aren't seeing this problem- and I'm not sure of how best the proceed.

Well i think there’s really something off. I‘m seeing this one very often:
Unsupported top level event type "topTouchStart" dispatched Unsupported top level event type "topTouchStart" dispatched
I believe it‘s not so specific to ScrollView, but more related to a behavioral change of the validation / Check Code (maybe with React 16 or an assert that didn“t fire before?)

@bvaughn I also wonder why suddenly there is a problem. Unfortunately, at least in my environment, errors still occur. I looked a little bit further and hope it helps.
Below is the process I understood.

Creates native component using requireNativeComponent, then createReactNativeComponentClass is called internally.
https://github.com/facebook/react-native/blob/v0.50.3/Libraries/ReactNative/requireNativeComponent.js#L196

View’s config is saved in internal map to load lazy.
https://github.com/facebook/react-native/blob/v0.50.3/Libraries/Renderer/ReactNativeFiber-dev.js#L2966

View is created and is registered events when creating instance. (createInstance)
https://github.com/facebook/react-native/blob/v0.50.3/Libraries/Renderer/ReactNativeFiber-dev.js#L3054

Take a closer look

Sample code that causes the problem.

render() {
  return (
    <ScrollView horizontal>
      <View style={styles.dummy}></View>
    </ScrollView>
  );
}

The process of creating a view

createReactNativeComponentClass : RCView
createReactNativeComponentClass : RCTImageView
createReactNativeComponentClass : RCTTextInlineImage
createReactNativeComponentClass : RCTScrollView
createReactNativeComponentClass : AndroidHorizontalScrollView
createReactNativeComponentClass : AndroidHorizontalScrollContentView
createInstance : RCView
7-1. call getViewConfig() of createReactNativeComponentClass
7-2. try to register default event types, but UIManager.ViewManagerNames is undefined, so the default events are not registered.
https://github.com/facebook/react-native/blob/v0.50.3/Libraries/ReactNative/requireNativeComponent.js#L62
createInstance : AndroidHorizontalScrollContentView
createInstance : AndroidHorizontalScrollView

RCTScrollView is not called because it is not created. It has override method to register events(topScroll,...).
Why UIManager.ViewManagerNames is undefined seems to be a clue to solving.

7-2. try to register default event types, but UIManager.ViewManagerNames is undefined, so the default events are not registered.

Ooh! Thanks @ifsnow! That is actually useful info. Let me chat with Dmitry about it.

The default event types should be registered in case UIManager.ViewManagerNames is undefined. The else clause there merges in events from a ViewManager and UIManager.genericBubblingEventTypes/genericDirectEventTypes which are default and exported with UIManagerModule creation.

@bvaughn @comfly That’s right. This is an important part. I think I found a clue to solving this mystery.
There are no 5 events(topScroll, …) in getDirectEventTypeConstants of 0.50.3 branch.
0.50.3 branch
https://github.com/facebook/react-native/blob/v0.50.3/ReactAndroid/src/main/java/com/facebook/react/uimanager/UIManagerModuleConstants.java#L83
master branch
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/uimanager/UIManagerModuleConstants.java#L78

Ooh snap! So the native code is trailing behind in this branch!
We added those events types after (ca834f9 when we realized that several viewmanagers didn't explicitly define them.

cc @grabbou Can we get that change (ca834f9) cherry-picked into the 0.50 branch and released as 0.50.4?

Going to do that right now.

Just tested 0.50.4 and the error is no more.
Thanks @bvaughn & @grabbou !

Perfect, Thanks! Funny thing that I've just encountered this issue for the first time like 30 minutes ago, googled for this issue, and saw that it's going to be released pretty much now hahah :)

could anyone please explain this case?In react-native 0.54

@mc-tracker Reset cache.
Please run:
npm start -- --reset-cache

@Amurmurmur rebuild apk resolved it , thanks anyways

Thank you, updated to 0.54 and fixed it

@bvaughn Thank‘s for this fix! But it seems something is still off on a different place: i‘m seeing this issue with topTouchStart

@K-Leon "topTouchStart" (TouchEventType.START) is specified as one of the default bubbling event types (see getBubblingEventTypeConstants). This means it should always be mixed in, by one of the following code paths:
Are views are being lazy-loaded?

Yes:
requireNativeComponent >
UIManager.getDefaultEventTypes >
UIManagerModuleConstantsHelper.getDefaultExportableEventTypes >
UIManagerModuleConstants.getBubblingEventTypeConstants.

No:
requireNativeComponent >
UIManager.genericBubblingEventTypes >
UIManagerModuleConstants.getBubblingEventTypeConstants

Quickly spot-checking the v0.50.4 branch, all of the above codepaths seem to be in-sync with master.

Did you try resetting cache (as specified above)?
npm start -- --reset-cache

Yea version v0.50.4 fixed the issue :+1:
In my case to get it work, i had to remove to android/app/build folder first to remove already built apks.

I've just started a new project with React Native 0.50.4. I see the error on iOS every time pressing Back button in toolbar or performing swipe-back gesture in NavigatorIOS component.

Can I fix this the way it fixed in Android? Can't find the place with UIManager constants in iOS sources though.

I'm not very familiar with the native iOS code. But it looks like RCTComponentData.m gathers native events and exposes them to RCTUIManager.m which passes on to JS. I added some logging to requireNativeComponent just to double check the event types it gets, and it shows that RCTScrollView specifies topScroll as one of its directEventTypes. Seems like it should work fine?

If someone is facing the same problem in expo, try updating expo SDK to 23 and the expo app too. I didn't update the app and lost a lot of time on that.

Just created a new project with react-native init and get this error

react-native: 0.51.0
react: 16.0.0
device: Nexus 5 API 23 (AVD)

@bvaughn I'm still seeing it on android - event after cache clear. I can only reproduce it in production - i've still no idea where it is triggered. Even though this crash is new and currently the most "popular".

still happen in RN 0.51

My app was working fine until I updated to Expo 2.2.0 on my phone and now I get this error

Still happening for 0.51.0. Confirming that moving to ^0.49.5 does the trick.
It seems like it's for all sorts of components, e.g. happened to TouchableOpacity for me.

@ifsnow; now that you can @override whatever function you're overriding, what do the rest of us mere mortals do to fix our issue the with the red horror screen from an app update. In my case, all I did was add a StatusBar component without any code yet!.... go figure, add one problem, get may problems back.... as usual, an app update that shows up as an error for the rest of us.....

@marc9000 @dcu-sharepoint @nhoxbypass I don't get any more errors in RB 0.51.
Could you show me the code that caused the problem? or Try the code below in your new project.
In my case, It works well in RB 0.51(Android 6.0)
import React, { Component } from 'react';
import {
  View,
  StyleSheet,
  ScrollView,
  TouchableOpacity,
  Text,
  StatusBar
} from 'react-native';

export default class App extends Component {
  render() {
    return (
      <View style={styles.container}>
        <StatusBar
          backgroundColor="blue"
          barStyle="light-content"
        />

        <TouchableOpacity>
          <Text>Click</Text>
        </TouchableOpacity>

        <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'
  }
});

Hi! I use RN --V0.51 and get the same error with the following code:
javascript
<View>
                <ScrollView
                    horizontal={true}
                    style={{marginBottom: 3}}
                    showsHorizontalScrollIndicator={false}
                >
                    <View style={styles.circleMargin} >
                    <Text style={styles.categoryText}> Drinks </Text>
                        <TouchableOpacity onPress={() => setCategory("drinks", selectedCategory)} >
                            <View style={styles.circle} >
                                <Entypo
                                    name="drink"
                                    size={categorySize}
                                    color={ (selectedCategory === "drinks") ? selectedColor : iconColor}
                                    style={styles.categoryIcon} />
                            </View>
                        </TouchableOpacity>
                    </View>
                 </ScrollView>
            </View>

Is my issue related to this?  I am in 0.51 and when I build an app for production I get a crash on startup (my first screen has a ScrollView with no parameters).
I traced the error to: Subscribable.js:
the this.subscribableSubscriptions is null, and it shouldn't be.  That is why the crash comes on the ForEach.
Here is the current code...
  componentWillUnmount: function() {
      this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
     this._subscribableSubscriptions = null;
  },

When I modify the code to this, the crash goes away...
componentWillUnmount: function() {
  console.log(`Subscribable - error location? ${this._subscribableSubscriptions}`)
  if (false) {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
  }
    this._subscribableSubscriptions = null;
  },

What do you think?

@cyphire The same problem here. Release app without any big changes from my side started to throw the same error:
ReactNative: TypeError: undefined is not an object (evaluating

'this._subscribableSubscriptions.forEach')

This error is located at:
  in ScrollView
in t
in t
in RCTView
in r
in Connect(r)
in RCTView
in a
in n
in t
in RCTView
in RCTView
in t, stack:
componentWillUnmount@210:183
<unknown>@153:2884
<unknown>@41:51861
mountClassInstance@41:51916
<unknown>@41:58934
beginWork@41:58969
q@41:88677
ee@41:89278
ne@41:90352
ue@41:92806
ae@41:92107
enqueueSetState@41:25532
setState@48:846
onStateChange@303:5122

Decreased the version of React native to 0.49.5 and it works now.
@cyphire Do you think we should create an issue ?

I was going to, almost had it finished, but wanted to explore the root causes of it.
Do you happen to use ignite?  I was wondering if it was some middleware or other issue.
It seems to me that there might be issues with anything which uses keyboard events (dismissing the keyboard) and ScrollView.  I moved my code to FlatList instead, but same error - I guess they are all based on ScrollView.  Did you also use  keyboard events to get this error?   The problem is definitely failing in the Scribbable.js module - but that's not the problem, it's whatever tries to create the events..
Here is what I was going to post:  If you want to update the below and post it that would be fine, either  way.

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Windows 10
Node: 8.9.1
Yarn: 1.3.2
npm: 5.5.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version  3.0.0.0 AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0
Steps to Reproduce

When building the app in normal debug mode, no issue.
In the "android" directory, I ran "gradlew assembleRelease".
This created the correct SIGNED app-release.apk in the apk directory.
Installed the app-release.apk in both the emulator on computer as well as an LG V20 device.
Both the emulator and the device crash on startup.

Expected Behavior

I expected that the release version would work as the debug version did.
Actual Behavior
Here is where the error occurs: in Subscribable.js
(..\node_modules\react-native\Libraries\Components\Subscribable.js)
This is the original code.
  componentWillUnmount: function() {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
    this._subscribableSubscriptions = null;
  },

Here is where i removed the failing call.  I have confirmed that this._subscribableSubscriptions returns a null and crashes when the forEach() is called.
  componentWillUnmount: function() {
  console.log(`Subscribable - error location? ${this._subscribableSubscriptions}`)
  if (false) {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
  }
    this._subscribableSubscriptions = null;
  },

Following removing the offending code, the app no longer crashes on startup.
FROM LOGCAT:
11:01:04.208  5499  5499 D ReactNative: ReactInstanceManager.ctor()
12-25 11:01:04.212  5499  5499 D ReactNative: ReactInstanceManager.createReactContextInBackground()
12-25 11:01:04.212  5499  5499 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundInner()
12-25 11:01:04.213  5499  5499 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundFromBundleLoader()
12-25 11:01:04.213  5499  5499 D ReactNative: ReactInstanceManager.recreateReactContextInBackground()
12-25 11:01:04.213  5499  5499 D ReactNative: ReactInstanceManager.runCreateReactContextOnNewThread()
12-25 11:01:04.246  5499  5515 D ReactNative: ReactInstanceManager.createReactContext()
12-25 11:01:04.389  5499  5515 D ReactNative: Initializing React Xplat Bridge.
12-25 11:01:04.394  5499  5515 D ReactNative: Initializing React Xplat Bridge before initializeBridge
12-25 11:01:04.413  5499  5515 D ReactNative: Initializing React Xplat Bridge after initializeBridge
12-25 11:01:04.414  5499  5515 D ReactNative: CatalystInstanceImpl.runJSBundle()
12-25 11:01:04.454  5499  5524 D ReactNative: ReactInstanceManager.setupReactContext()
12-25 11:01:04.454  5499  5524 D ReactNative: CatalystInstanceImpl.initialize()
12-25 11:01:04.459  5499  5524 D ReactNative: ReactInstanceManager.attachRootViewToInstance()
12-25 11:01:04.927  5499  5522 I ReactNativeJS: Running application "BinStuffer" with appParams: {"rootTag":1}. DEV === false, development-level warning are OFF, performance optimizations are ON
12-25 11:01:04.995  5499  5522 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-25 11:01:04.995  5499  5522 E ReactNativeJS:
12-25 11:01:04.995  5499  5522 E ReactNativeJS: This error is located at:
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in ScrollView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in n
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in n
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in n
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in r
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in Unknown
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in a
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in n
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:04.995  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-25 11:01:05.003  5499  5522 E ReactNativeJS:
12-25 11:01:05.003  5499  5522 E ReactNativeJS: This error is located at:
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in ScrollView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in n
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in n
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in n
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in r
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in Unknown
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in a
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in Connect(t)
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in n
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in RCTView
12-25 11:01:05.003  5499  5522 E ReactNativeJS:     in t
12-25 11:01:05.336  5499  5499 D ReactNative: ReactInstanceManager.detachViewFromInstance()
Reproducible Demo

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

I'm using NavigatorIOS and also same problem when goes back.

I have created an issue:
https://github.com/facebook/react-native/issues/17358

Thanks Brian. Actually there is already an issue:
https://github.com/facebook/react-native/issues/17348
On Tue, Dec 26, 2017 at 11:40 PM Brian B. Canin notifications@github.com
wrote:

I have created an issue:
#17358 https://github.com/facebook/react-native/issues/17358
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/16522#issuecomment-354015888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEXdyPUvNfaSDOJ4af5SIaeteZtz3-jVks5tEWfJgaJpZM4QEhWw
.

Closed my issue for the other one.

Brian B. Canin    brian.canin@gmail.com
858-945-5601 (cell)
On Tue, Dec 26, 2017 at 5:13 PM, avshenuk notifications@github.com wrote:

Thanks Brian. Actually there is already an issue:
https://github.com/facebook/react-native/issues/17348
On Tue, Dec 26, 2017 at 11:40 PM Brian B. Canin notifications@github.com
wrote:

I have created an issue:
#17358 https://github.com/facebook/react-native/issues/17358
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/facebook/react-native/issues/16522#
issuecomment-354015888>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AEXdyPUvNfaSDOJ4af5SIaeteZtz3-jVks5tEWfJgaJpZM4QEhWw>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/16522#issuecomment-354018586,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUnhm6Ls_T-lv4nG4ZOQ2FCh61-14UXks5tEW-RgaJpZM4QEhWw
.

Hey guys, you can try to follow this instruction ( https://facebook.github.io/react-native/docs/upgrading.html ) to set your project to 0.49.5, then this error will disappear.
Remember, let your version number are match each other. (https://github.com/react-community/create-react-native-app/blob/master/VERSIONS.md)
After change the version number, run 'npm install' on command line in your project directory.

same error for me...
and works after set my project to 0.49.5.
but, some other packages got error,  SafeAreaView undefined .

@hugtrueme How are you guys downgrading? I've been trying to downgrade to 0.49.5 form 0.54.0, but when I do the whole app fails to start on my Android emulator.
My package.json:
{   "name": "ssnitmobileapp",   "version": "0.0.1",   "private": true,   "scripts": {     "start": "node node_modules/react-native/local-cli/cli.js start",     "test": "jest"   },   "dependencies": {     "react": "16.0.0-beta.5",     "react-native": "0.49.5",     "react-native-elements": "1.0.0-beta2",     "react-native-maps": "^0.20.1",     "react-native-vector-icons": "^4.5.0"   },   "devDependencies": {     "babel-jest": "22.4.1",     "babel-preset-react-native": "4.0.0",     "jest": "22.4.2",     "react-test-renderer": "16.0.0-beta.5"   },   "jest": {     "preset": "react-native"   } }

I'm working on a Expo-generated app and got the message message about unsupported top level event type. The the app started back up when I restarted the app on the Expo console.

@andersonaddo, sorry for late, i posted my package.son & app.son on here.
https://github.com/facebook/react-native/issues/16522#issuecomment-368242086

I'm having this issue on react-native 0.52.0.  Below is my package.json.  The error occurs when I tap the back button.
  "name": "App",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "react-native-scripts": "1.11.1",
    "jest-expo": "25.0.0",
    "react-test-renderer": "16.2.0"
  },
  "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
  "scripts": {
    "start": "react-native-scripts start",
    "eject": "react-native-scripts eject",
    "android": "react-native-scripts android",
    "ios": "react-native-scripts ios",
    "test": "node node_modules/jest/bin/jest.js"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "expo": "^25.0.0",
    "react": "16.2.0",
    "react-native": "0.52.0"
  }
}```

Same issue on  react-native 0.54.0， appreciate any help or advice as to solve this headache!

After I added  a
<ScrollView />

into layout , the problem solved!

+1 I'm having the same issue - would greatly appreciate any help!
Is there any way of fixing this without having to downgrade to 0.49.5? Because I need to run at least 0.50.3 due to some other project dependencies

Reopening as I noticed people are claiming this is still an issue in v0.54.0 (current stable).
Let's limit new comments to those with information pertaining to v0.54.0. If you are not running v0.54.0 or newer, please abstain from commenting on the issue.

@hramos what information do you need? As I'am experiencing this issue as well, in a really simple app. Downgrading to react-native version 0.49.5 worked fine, but in the latest 0.54.2 it was broken for me.
All I did was create an app with react-native init,  remove the scaffolding done by init and outputted some text. I'am running the app on the iPhone 6 Simulator as well as on a Google Pixel emulator, both were causing the same problem.

@pascalporedda if your repro steps match the original post, then I don’t think an update is necessary, other than perhaps mentioning its present in 54.2. If you have additional information on how this can be reproduced, that would help.
Ideally, if someone digs deep into the root cause, that’s the sort of information that would be helpful in this thread.
If your repro steps do not match the original, then I would report it as a new, distinct issue.

After upgrading to v0.54.0, this error didn't trigger any more - thanks @hramos! :)
To give some more context, I'm setting the horizontal prop to true in the ScrollView component, this specific error was triggering on Android before when I was running v0.50.3.

We still encounter this issue with 0.55.4. We created a new project with react-native init ExampleApp, and then added two simple screens for NavigatorIOS to navigate between. We get the Unsupported top level event "topScroll" dispatched when the back button of the navigator is clicked. If we wrap the screens with ScrollView it works.

We are seeing this error in rect-native 0.55.4.
For us, removing the key prop from child views did the trick, but it's hackish and triggers the missing key warning.

Hello,
I use 0.56 and still see this issue on iOS. I am using NavigatorIOS - this issue is still not solved, is it?

So do I with NavigatorIOS. The red screen with the same error occurs when I go back to the previous view.

I'm seeing this in react-native ^0.56.0.  Is the workaround still to wrap the NavigationIOS component in a ScrollView?

version: 0.57.1, when you popBack with using NavigationIOS, this error happens.

If your need are urgent and want to accomplish single page, you can solve it with using ScrollView and disable its scroll with scrollEnabled='false' for a temporary a way of running from the error.
<ScrollView scrollEnabled='false'>
          <SafeAreaView>
            <View>
                <Text>Current Scene: {this.props.title}</Text>
                <Button
                    onPress={this._onForward}
                    title="Tap me to load the next scene"
                  />
            </View>
      </SafeAreaView>
      </ScrollView>

Is the root cause the same for other this kind of errors? I get one with gestures with both react-navigation and my own code. Both iOS and Android. This is a show stopper, as the app does not work at all anymore.
"react": "16.8.6",
"react-native": "0.59.2",
"react-native-gesture-handler": "1.1.0",
"react-navigation": "3.5.1",

authors: 4thjuly AliSarraf Amurmurmur JoseVf K-Leon Kottidev MedericPixium Narutuffy Omniwheel PetrVasiliev Rom96 Sergeypt423 amirkheirabadi andersonaddo asgvard avshenuk awnali booleanBoy bvaughn chikarao chrispaynter cleandersonlobo clewiston codeYDH comfly cyphire dcu-sharepoint ddman dody87 donnes elbsurfer eliakorkmaz eroosenmaallen grabbou grath10 hramos hssrrw hugtrueme iCodePup iRoachie ide ifsnow igrishaev kelset kingofglory lee-d legion-zver marc9000 mc-tracker meinto meurling mhemrg mtmcfarl nhoxbypass nimamyscreen oonxt pangpond pascalporedda rabingaire rambabusaravanan rolignu2 shawngustaw tapz wnr znacloud


text:
Android[ClipboardManager] with event addPrimaryClipChangedListener

Use https://github.com/react-native-community/discussions-and-proposals to propose changes or discuss feature requests. This helps us ensure bug reports and regressions are given the priority they require.
You may also use https://discuss.reactjs.org/ for discussions on topics that are not necessarily served by the Bug Report template.

For Discussion

I have  using Clipboard wirh listen event  change data   ?

Hey, the Discussion template is meant for long-form discussions about React Native. This looks like a request for help. Please take a look at http://facebook.github.io/react-native/en/help.html for a list of help resources.

source: gharchive/issue

authors: hramos isthaison

repo: facebook/react-native

license: MIT

license_type: permissive

license_source: github-api


text:
[0.60.0] Fresh install : 'cxxreact/ModuleRegistry.h' file not found

When running an iOS fresh app with react-native 0.60.0 the build failed with this error:
'cxxreact/ModuleRegistry.h' file not found
macOS Mojave 10.14.5
xCode 10.2.1
React Native version:
react-native-cli: 2.0.1
react-native: 0.60.0
Steps To Reproduce

react-native init projectname
open . xcworkspace
hit run
=> error:
'cxxreact/ModuleRegistry.h' file not found

or

react-native init projectname
react-native run-ios
=> error:
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening testproj060.xcworkspace. Run CLI with --verbose flag for more details. ** BUILD FAILED **

+1

+1

👋 as pointed out by @murrayee 	it's likely that you didn't have cocoapods installed - or something went wrong during linking. I just tried to do the same flow you described and I can't reproduce it - I'll close this for now.

i already had cocoapods installed.
Doing a brew install cocoapods and redo a pod install fix it, thanks

@murrayee I did what you told. But it showed '[!] No `Podfile' found in the project directory.'.
What should I do next?

@dragooncjw you need to execute pod install inside ios/ folder. Did you try that? 🤔

i try this same flow but i can't solve it

authors: betopompolo dragooncjw gongshouhui kelset lizhengjin murrayee psyzz


text:
pointerEvents={'none'} does not work on Android

Bug
I try to use pointerEvents={'none'} on Image component, but it does not work on Android. It is effective on iOS.
React Native version:
 React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
      Memory: 141.91 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.1.0 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 24, 26, 27, 28
        Build Tools: 26.0.2, 27.0.3, 28.0.2, 28.0.3
        System Images: android-24 | Google APIs Intel x86 Atom, android-27 | Intel x86 Atom_64, android-28 | Intel x86 Atom_64
    IDEs:
      Android Studio: 3.0 AI-171.4443003
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.9 => 0.59.9
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Steps To Reproduce
export default class GeneralBackground extends PureComponent {

    render() {
        return (
            <View style={styles.container}>
                {this.props.children}
                <Image
                    source={myImage}
                    style={styles.image}
                    pointerEvents={'none'} // Does not work on Android.
                />
            </View>
        );
    }

}

const styles = StyleSheet.create({
    container: {
        flex: 1,
        backgroundColor: Colors.theme
    },
    image: {
        width: 160,
        resizeMode: 'stretch',
        alignSelf: 'center',
        position: 'absolute'
    }
});

I expect that this.props.children like Button component can be work but not Image above.  But it can work on iOS via testing, Android failed. Did I use it by mistake? I think it maybe a bug.
Anybody knows that?  Thanks a lot in advance.

Hi @Amos729,
It seems that the pointerEvents prop is not available on the Image component: searching pointerEvents on https://facebook.github.io/react-native/docs/image yielded nothing.
I believe it's only available for View components: https://facebook.github.io/react-native/docs/view#pointerevents
Doing something like that
<View style={styles2.image} pointerEvents={'none'}>
   <Image source={myImage} />
</View>

made a children Button clickable on Android.
Hope that helps!

@RobinCsl  I tried what you said just now. It's really useful both Android and iOS platform.
Thank you so much.

For the record, same problem with TextInput but also solved with a wrapping view with pointerEvents={'none'}

authors: Amos729 RobinCsl jjercx lchenfox


text:
Broken Cyrillic symbols support in TextInput with custom fonts. RN 0.62[iOS]

Description
In iOS, when I type any Cyrillic letter in TextInput with custom font family that doesn't have Cyrillic symbols support then text in input starts flickering(see gif below).
At every odd symbol in TextInput, all Cyrillic symbols just disappear
This issue appears in 0.62. On version 0.61 and below it works fine

React Native version:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Memory: 42.68 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.17.0 - ~/.nvm/versions/node/v10.17.0/bin/node
    Yarn: 1.19.2 - /usr/local/bin/yarn
    npm: 6.11.3 - ~/.nvm/versions/node/v10.17.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5977832
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.5 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Init RN 0.62.* project npx react-native init AwesomeProject
link some font that doesn't support Cyrillic symbols
Use that font in TextInput
Write any Cyrillic text in the input

Expected Results
A font that doesn't support Cyrillic shouldn't flicker in TextInput, as it was in RN 0.61 and below
Snack, code example, screenshot, or link to a repository:
You can try these fonts from my example:
Modak
Pacifico
<Text style={styles.footer}>Modak: Doesnt support cyrillic</Text>
<TextInput style={{fontFamily: 'Modak'}} placeholder="Modak Font" />
<Text style={styles.footer}>Pacifico: Support cyrillic</Text>
<TextInput style={{fontFamily: 'Pacifico'}} placeholder="Pacifico Font" />

I have the same issue

Hi also having the same issue. Interesting thing is that when I set multiline then it works without flickering.

I wanted to ask if you still experience this issue.
I'm planning to do 1-2 months of opensource and I'm preparing a list of tasks.
I have been contributing to facebook/react-native for 4 years and I specialize on the Text/TextInput components.
Thanks a lot


text:
[Android] ScrollView onScroll event is not smoothly when page changed with "pagingEnabled" even though using native animated driver.

Description
ScrollView onScroll event is not smoothly when page changed with "pagingEnabled" even though using native animated driver. Android so far.
Version
0.66.3
Output of npx react-native info
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Memory: 6.50 GB / 15.80 GB
Binaries:
Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 28, 29, 30, 32
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 30.0.3, 32.0.0, 32.1.0
System Images: android-30 | Google Play Intel x86 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version     2021.1.0.0 AI-211.7628.21.2111.8193401
Visual Studio: Not Found
Languages:
Java: 1.8.0_60 - /c/Program Files/Java/jdk1.8.0_60/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.66.3 => 0.66.3
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

open the snack
run on android
try to drag to change page.
the red view will shake.

However, it will work fine if I disable pagingEnabled
Snack, code example, screenshot, or link to a repository
The example is here

Hello @bolan9999, I can't see any shaking in the suggested snack. Could you please update the snack so the problem is more evident.

@bolan9999 I've updated the snack a little bit, so it easier to see that something is actually scrolling. https://snack.expo.dev/uLA_LneN8
I can't see any shaking. Could you please record a video that shows the problem?

??? why did you update it like this ?
The point is the transform on the red view...................

Are you sure you ran it on Android? Swipe to switch page and then focus on the red view, is is shaking when page changed (note it appears only 0.1 second)..   For some reasons ,I can not upload video.

The red view follows the x offset of the scrollview, but it is not smoothly when swiping.

If you do not know what I say, you can set pagingEnabled=false,  compare the red view's effect.


text:
[TextInput] lineheight cuts off content on iOS

Description
The TextInput on iOS cuts off content at dashes (-) if it has the lineHeight style applied to it. This happens when content is to long and therefore isn't completely visible in the input without moving through it.
If the lineHeight isn't applied it is not cut off at the dash (-) and the content will end with ellipsis (...).
We tried removing everything from the input and found out in that way it was the lineHeight that causes this issue.
This only happens on iOS and not on Android.
React Native Version
0.71.13
Output of npx react-native info
System:
    OS: macOS 14.0
    CPU: (10) arm64 Apple M1 Pro
    Memory: 55.56 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    Watchman: 2023.10.02.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.13.0 - /Users/thomaslamars/.rvm/gems/ruby-2.7.5/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 2022.2 AI-222.4459.24.2221.9971841
    Xcode: 15.0.1/15A507 - /usr/bin/xcodebuild
  Languages:
    Java: 18.0.2.1 - /Library/Java/JavaVirtualMachines/jdk-18.0.2.1.jdk/Contents/Home/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: ^0.71.13 => 0.71.13
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce
It is reproducible by making an TextInput with just lineHeight on it with the styling.
Than as value pass a really long string or type a really long string with dashes.
Get out of focus with the input and see that the value in the input gets truncated.
import { TextInput, SafeAreaView, StyleSheet } from 'react-native';

export default function App() {
  const value = "Thisisareallylong emailwithdashes-init@thawdisisasnackwhichisanexample.com"

  return (
    <SafeAreaView style={styles.container}>
      <TextInput value={value} style={{ lineHeight: 20 }} />
    </SafeAreaView>
  );
}

Snack, screenshot, or link to a repository
Snack url
Reproducible on Snack with expo 49 and react native version 0.72.4
https://snack.expo.dev/l0o3kNldL

@TLaMars thanks for the issue. Are you using the old architecture or the new one?

@cipolleschi we are using the old architecture

Adding screenshots for clarity, thanks for the Snack!

iOS
Android

@frankcalise , Did you find any solution? I am also facing the same issue.

My issue was happening due to textAlign: 'center' . I was able to resolve it with a this little hack.

When line height is given I do face this same issue on iOS.

authors: TLaMars abhinandhand akumarclick cipolleschi frankcalise


text:
Text in FlatList is not selectable on Android

Description
Bug previously opened here.
It was claimed to be fixed here but still reproduces on 0.75.4
Steps to reproduce
Try to select text in provided reproducer, it won't work for item in flat list. Note that sometimes it will work after a hot reload.
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 *
 * @format
 */

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

function App(): React.JSX.Element {
  return (
    <SafeAreaView>
      <Text style={styles.text} selectable>I am selectable</Text>
      <FlatList data={[1]} renderItem={ListText}/>
    </SafeAreaView>
  );
}

const ListText = () => {
  return <Text style={styles.text} selectable>I am not selectable</Text>;
};

const styles = StyleSheet.create({
  text: {
    fontSize: 20,
    padding: 10,
  },
});

export default App;

React Native Version
0.75.4
Affected Platforms
Runtime - Android
Output of npx react-native info
info Fetching system and libraries information...
System:
  OS: macOS 15.0
  CPU: (12) arm64 Apple M3 Pro
  Memory: 206.94 MB / 36.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.9.0
    path: ~/.asdf/installs/nodejs/20.9.0/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.1.0
    path: ~/.asdf/plugins/nodejs/shims/npm
  Watchman:
    version: 2024.08.19.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.3
    path: /Users/johanlndll/.gem/ruby/3.1.4/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.0
      - iOS 18.0
      - macOS 15.0
      - tvOS 18.0
      - visionOS 2.0
      - watchOS 11.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.21829.142.2421.12409432
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 3.1.4
    path: /Users/johanlndll/.rubies/ruby-3.1.4/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
Does not crash.

Reproducer
https://github.com/LA-Johan/list-select
Screenshots and Videos
https://github.com/user-attachments/assets/480fb515-b207-4774-b5a2-78127afd9268

@fabOnReact Can you please re look in this issue. Fix provided by you here, somehow is not working in latest release for old and new arch both.

Hi, I'd like to work on this issue. Please assign it to me :)

@shubhamguptadream11  @fabOnReact  @MobinAkhter  I'm currently facing this issue on my company's application for React Native 0.72.0. Same exact situation, occurs only on android, doesn't function on first load but hot reloads fix it.
I'm new to React Native development, how long does it typically take an issue like this to be assigned? I'm surprised we have a volunteer above but no follow up.

authors: LA-Johan MobinAkhter shubhamguptadream11 tradejak


text:
Error building dependency graph when using packager

I'm having some issues running the packager.  When using 'npm start' I get the following: https://gist.github.com/DeeBrad/7f1d57600a37f6112daa. I have tried deleting node_modules and running npm install again, but that didnt solve it. Any help would be great!

Try
rm -fr $TMPDIR/react-*
watchman watch-del-all
npm start --reset-cache

@facebook-github-bot no-reply

authors: DeeBrad chirag04 jsierles


text:
RCTNetworkTask (RCTURLRequestDelegate) is nil when fetching data

Hi, I'm trying to integrate React Native into an existing iOS app right now, and we're seeing issues where all XMLHttpRequest calls aren't returning any responses (whether success, error, or timeout).
I've traced down the issue to the following area:
https://github.com/facebook/react-native/blob/060664fd3d9331f062696e68179bac9cd4544a06/Libraries/Network/RCTHTTPRequestHandler.m#L96
Modifying the code a little bit, here's what I'm seeing in my debugger:

It looks like the RCTURLRequestDelegate is always nil at that point, so URLRequest:didReceiveResponse: is never being called, so nothing is ever returned back through the JavaScript bridge.
The other NSURLSession delegates are being called though, however.
This is occurring in version 0.25.1 on iOS, built on OS X - I've tested this with both manually linking the React Native libraries and installing through CocoaPods as well.  I've also seen this in 0.21 as well.
I'm trying to find a minimal repro case for this bug, but I'm having difficulty root causing what's causing this issue.  It seems as if the _delegates NSMapTable is releasing the delegate values early, though I'm not sure how that's happening.
Let me know if there's any additional information I might be able to help provide.

@facebook-github-bot label iOS

I think you point to the problem here - without a minimal repro case I don't think anyone else will be able to make much progress here. Practically in order to achieve a minimal repro I think you have to do something like, start with your project, get rid of half your code, repeat if needed and see at what point the bug goes away. Anyway, I am going to close this issue but if you do find a minimal repro then please feel free to open a new issue.

authors: AndrewJack clarle lacker


text:
Enable custom source file extensions through cli args or rn-cli.config.js

Ping @cpojer - This is the replacement PR for #11932
Motivation (required)
Allow the packager to load files from other compile-to-JS languages without developers having to specify file extensions in require calls.
Approach
Add an optional getSourceExts method to rn-cli.config.js, like the existing getAssetExts. Set defaults of 'js' and 'json' (as were being used before) and make sure the options are propagated through to the packager appropriately, then use them in module resolution.
Extensions specified by getSourceExts do not override the defaults but are combined with them, otherwise first-party react-native code would not be loaded.
Test Plan (required)
Tests for the changes to node-haste are included. I couldn't find any integration tests for rn-cli.config.js or the cli config opts anywhere, so I figured it wouldn't be necessary to add those. If that is required, it would be dope if someone with the appropriate knowledge could help direct that effort.
Here is a repo that shows it working: https://github.com/ds300/TestCustomSourceExts
Cheers

It was just renamed to sourceExts for consistency
On 28 Apr 2017 1:18 am, "Christoph Pojer" notifications@github.com wrote:

@cpojer commented on this pull request.
In packager/src/node-haste/index.js
https://github.com/facebook/react-native/pull/13689#discussion_r113830303
:

@@ -51,7 +51,6 @@ import type {HasteFS} from './types';
type Options = {|
+assetDependencies: Array,
+assetExts: Array,

+extensions: Array,

Why was this removed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/pull/13689#pullrequestreview-35253143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABL1qQKws0378hYSRGSmPzS4vL1Sk-PKks5r0TA2gaJpZM4NKkf6
.

I updated the TestCustomSourceExts repo to have incremental commits so people can see exactly what changed from a regular old blank react-native app.

I'll ship that tomorrow morning London-time.

4a86f93982ede66a993a72e31cadb85d9bd4b3a3 is the upgraded version I landed. @ds300  Do you want to check it out in https://github.com/ds300/TestCustomSourceExts and verify it covers what you need?

@jeanlauliac I'm getting this error after switching to your branch. The cause wasn't obvious from initial inspection.
Error: Cannot find module '/Users/dshe/code/TestCustomSourceExts/node_modules/react-native/local-cli/core/rn-cli.config.js'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.loadFile (/Users/dshe/code/TestCustomSourceExts/node_modules/react-native/local-cli/util/Config.js:137:24)
    at getCliConfig (/Users/dshe/code/TestCustomSourceExts/node_modules/react-native/local-cli/core/index.js:44:14)
    at Object.<anonymous> (/Users/dshe/code/TestCustomSourceExts/node_modules/react-native/local-cli/core/index.js:50:18)
    at Module._compile (module.js:541:32)
    at loader (/Users/dshe/code/TestCustomSourceExts/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/dshe/code/TestCustomSourceExts/node_modules/babel-register/lib/node.js:154:7)

Your changes look sensible to me otherwise. This is probably related to other changes that have happened in the meantime. I'll try to take a proper look on Sunday evening UK time.

I've been eager to use this for a while and have been kicking the tires a bit.
With a yarn install the iOS app works and the Android app does not.  To resolve this, I reverted to react-native@0.44.0 to build the Android shell and then restored the patch.
With this environment everything seems to work great except for source maps -- they are off by a few lines.

(Breakpoint should be on debugger;)

@jmfirth I think that's an orthogonal issue. This PR doesn't say anything about how source transformation should happen. And in particular the transformer I wrote for the test repo is extremely simplistic and doesn't compose the tsc source map with the babel one. So if you are using that, the discrepancy you observe makes sense.

@jeanlauliac the issue was obvious after all. There has been a breaking change in handling the --config cli option: https://github.com/facebook/react-native/blame/4a86f93982ede66a993a72e31cadb85d9bd4b3a3/local-cli/core/index.js#L44
Now the path given to --config must be absolute, or else it is evaluated against the __dirname of local-cli/core/index.js.
cc @davidaurelio this seems like a bad design decision to me, since it makes it super awkward to have a config file in a multi-dev project, unless I'm missing something.
But also that's beside the point for this PR. Making the path absolute makes the problem go away, and now I get a new error, but I also get that same error if I run a blank RN project against master, so it is likely to be unrelated.
In other words, I'm happy with your changes @jeanlauliac :+1:

Hey @ds300, that was the case before that changeset as well. I agree it is awkward. Correct me if I am wrong, but I think my changeset did not change behavior at all:
before, both config file and __dirname were passed to Config.loadFile, and that function would call path.join if the config file was not an absolute path. Now, we call path.resolve with both relative and absolute paths at the call site, which should have the same behaviour, right?

Feel free to send a PR that changes the base of the resolution to process.cwd(). That seems a lot better.

Oh, true, @davidaurelio my apologies. I didn't look too closely at the history. Will investigate tonight to find out exactly when support for relative paths was removed and why.

Closing, let's open separate task or PRs to address the other issues.
On an unrelated note, I'm disappointed in myself that I didn't properly give you credit for the changeset. Even though I rebased and changed a few things, you provided most of the idea. I will be careful to maintain a correct Authored-by field next time I merge a PR.

Slightly confused with what's happening with this PR. Has it been released with 0.45 ?

@johnnycopperstone yep.

source: gharchive/pull-request

authors: davidaurelio ds300 jeanlauliac jmfirth johnnycopperstone


text:
Fixes #21167

Fixes #21167
Unfortunately, when position is animated, bleeding occurs but that's ok

Because of

Configuration for rule "prettier/prettier" is invalid:
Value "fb" should be object.

when I ran eslint SwipeableRow.js I'm now catching errors by trial and error 😂

It's deprecated now


text:
[CI] fix test_android RootViewTest after latest refactor

Summary
This small PR fixes the RootViewTest failing on the CI:

https://app.circleci.com/pipelines/github/facebook/react-native/8048/workflows/452151df-9700-4cb8-9654-b5afbba03a56/jobs/188238/steps,
https://app.circleci.com/pipelines/github/facebook/react-native/8014/workflows/41b14ece-3fb9-44da-b8e5-320845c5dbe9/jobs/187824/steps.

The test started to fail after latest EventEmitters refactor, which took place in this commit:

https://github.com/facebook/react-native/commit/708038d80ed5793ae97bc49802bffef23df72bc3#diff-96085f5785576d57cbb29894083a9d82a4352bc05d435f46e7d9c58cbaf0ce8b

The reason for fail is that the change has introduced new targetSurface field, which was not added to the touch arguments map dump in the test.
CC: @JoshuaGross
Changelog

[Android] [Fixed] - fix RootViewTest after targetSurface addition
Test Plan
CI run which should not fail at "Run Tests: Android Unit Tests" step in test_android pipeline.

The issue has been fixed in commit https://github.com/facebook/react-native/commit/5ca832b4aa241fea4a42038eaea3b21dac379419.


text:
Update SegmentedControlIOS.ios.js

Updating the comments to clarify that the selectedIndex prop is not just for pre-selecting an index, but that it can also be used to programmatically change the value of the selected index.

Hey @pedramsaleh, thanks for submitting this!
What about we simplify the prop description a bit and add a usage example at the top with a simplified version of what I linked on Stack Overflow?
For the prop desc you could just remove the 'pre-selected' wording that is confusing and just say the 'selected index'.
For the example you could add the note about changing the selectedIndex programmatically after the code example.
Code example could look like this:
<SegmentedControlIOS
  values={['One', 'Two']}
  selectedIndex={this.state.selectedIndex}
  onChange={(event) => {
    this.setState({selectedIndex: event.nativeEvent.selectedSegmentIndex});
  }}
/>

(Note about using setState to change the selected value programically)
You can add it in the comment at the top of the component and use markdown for header/code blocks
(see https://github.com/facebook/react-native/blob/master/Libraries/Components/StatusBar/StatusBar.js#L75 as an example of this)

OK, I simplified the description of selectedIndex and added the example at the top, with an explanation beforehand.

I set the description of selectedIndex to "(pre)selected" to indicate that preselecting is an option, as well as programmatically updating on the fly.

Thanks! This is great, just fix the little typo and this is good to go :)

Haha!  Can't believe I didn't catch that.  OK, fixed.

Thanks for improving the docs @pedramsaleh and thanks for the review @janicduplessis!
@facebook-github-bot shipit

authors: janicduplessis mkonicek pedramsaleh


text:
Android WebView “tel:” links show web page not found - issue fixed

Submitting PR #6810 -  Android WebView “tel:” links show web page not found - issue fixed.
'tel:' link web page not loading:

After Fixing the issue:

By analyzing the blame information on this pull request, we identified @mkonicek and @nicklockwood to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

I don't think checking for tel: is the right way to do it. What about mailto:, or any custom schemes?
I think we should check if the URL is not http: or https:, then handle it. It'll probably suffice to just use a Intent.ACTION_VIEW for all URLs. In case of tel:, it won't dial the number, but will probably open the dialer with the number.

@satya164
public boolean shouldOverrideUrlLoading(WebView view, String url) {
        ReactContext reactContext = (ReactContext) view.getContext();
        if(url.startsWith("http")|| url.startsWith("http")) {
          return false;
        } else {
          Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(url));
          intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
          reactContext.startActivity(intent);
          return true;
        }
    }

Is this Correct? shall i proceed?

It should be url.startsWith("https") || url.startsWith("http"), otherwise looks correct. Please also test that the code works.

Also, do you need to cast this to ReactContext - (ReactContext) view.getContext();? It should work without casting.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


text:
Some Boolean attributes should be rendered even when set to false

If dont want an image to be draggable, you set its draggable attribute to false. But this doesn't work with xhp-lib because any boolean parameter which is set to false will not be rendered. So, the following will not work as expected.
<img draggable={false} src="img.png" />

More info here: http://stackoverflow.com/a/27034312/2330318

It looks like the problem is actually that draggable is enum { 'true', 'false' }, not bool :(
Reference: http://w3c.github.io/html/single-page.html
2.4.2. Boolean attributes
A number of attributes are boolean attributes. The presence of a boolean attribute on an element represents the true value, and the absence of the attribute represents the false value.
If the attribute is present, its value must either be the empty string or a value that is an ASCII case-insensitive match for the attribute’s canonical name, with no leading or trailing whitespace.
The values "true" and "false" are not allowed on boolean attributes. To represent a false value, the attribute has to be omitted altogether.
5.7.7. The draggable attribute
All html elements may have the draggable content attribute set. The draggable attribute is an enumerated attribute. It has three states. The first state is true and it has the keyword true. The second state is false and it has the keyword false. The third state is auto; it has no keywords but it is the missing value default.

Thanks :)

authors: fredemmott raeesiqbal

repo: facebook/xhp-lib

license_source: bigquery


text:
Robyn on Databricks: Getting Started

Project Robyn
Describe issue
Useful to have a few steps on how to get Robyn working on Databricks.
Not covered in current documentation.
Databricks
Databricks allows one to alternate between R and Python cells.  In this use we are using R as the default language for the notebook.
First install reticulate:
install.packages('reticulate')

Then with reticulate install nevergrad in the local python environment.  (Note: you do not need to create a virtual environment, and in fact doing so may cause a range of issues and difficulties, such as failure to find python3.8-venv, etc.  We have learned none of this is required, and you simply use reticulate to install nevergrad and you're in business):
library(reticulate)
country = dbutils.widgets.get('country')
py_install("nevergrad")
reticulate::py_config()

From here on you can install R packages and finally the Robyn package using remotes::install_github as found in the getting started document.
One drawback to this approach is that the install_github takes a long time, for us about 36 minutes.
We are looking towards some sort of image solution to make this faster, but we are also want the flexibility to get the latest Robyn code.
We do run this additional step to assert our library version of Robyn itself:
library(Robyn)
pkg_version = packageVersion('Robyn')
if (pkg_version != '3.4.8.8') {
  writeLines(as.character(pkg_version))
  stop('Wrong pkg version')
} else {
  writeLines('Libraries loaded. Robyn package version tested')
}

Hi, just to contribute to this issue and save some people some time. DataBricks has problems with reading folders in DBFS with spaces, so default folder names such as "2022-01-17 11.07" are hardly accessible by scripts inside notebooks. If you change spaces for underscores, everything will go smoothly

I did not have a problem with databricks when putting double quotes around the file names, same as when using shell commands.  However, there are advantages to avoiding spaces I would agree.

I did not have a problem with databricks when putting double quotes around the file names, same as when using shell commands. However, there are advantages to avoiding spaces I would agree.

Totally agree, my comment was regarding extracting files from DBFS via links in web browsers (in my case spaces in catalog names were a problem).

We have a new innovation to accelerate R Robyn development in databricks.
This is to build the code from Robyn once and cache it as a library.
Problem: The problem databricks users may encounter (we did) is that when a cluster starts up it does not have Robyn nor other R libraries installed.  The process takes over 40 minutes each time we startup.
Summary: The solution is to build the libraries, push them over to dbfs, and then add a dbfs library path to that directory on startup of your Robyn notebook.  The Robyn notebook does not have to install.packages() but merely use the library.
Reference concept: https://github.com/marygracemoesta/R-User-Guide/blob/master/Developing_on_Databricks/package_management.md#custom-packages
dbfs=databricks file system
Details:
Notebook 1: Install Libraries
Create a library path where you isntall libraries
%sh
mkdir /usr/lib/R/robyn-lib-path

Add this new directory to libPaths:
.libPaths(c("/usr/lib/R/robyn-lib-path", .libPaths()))

Run installation of packages you wish to have pre-installed
We reviewed our libPaths first:
.libPaths()

Then we installed a bunch of packages we wanted in place:
install.packages('remotes')
install.packages('plyr')
install.packages('dplyr')
install.packages('rlist')
install.packages('stringr')
install.packages('rlist')
install.packages('ggplot2')
install.packages('patchwork')
install.packages('scales')

(not sure which of these are absolutely required for robyn)
Finally we installed a specific github version.  For us, we are installing a fork and using a branch on that fork (ref) so our command looks like:
remotes::install_github('joangcc/Robyn/R', ref='free_intercept')

You would instead reference the Robyn repo in the first argument, and use ref if you have a branch
Verify the libraries installed:
%sh
ls -l /usr/lib/R/robyn-lib-path

Copy installations to dbfs so they can be saved across cluster runs.
Consult your local admin about paths you might use.  These happen to be paths we created on /dbfs.
Since you may deploy different versions of Robyn over time and want them simultaneously available, I would suggest putting the branch and version name in the directory as we have done:
%sh
mkdir /dbfs/robyn/robyn_free_intercept_3.4.8.10
cp -R /usr/lib/R/robyn-lib-path /dbfs/robyn/robyn_free_intercept_3.4.8.10
ls -l /dbfs/robyn/robyn_free_intercept_3.4.8.10

(this command took us 30' when we did the install, but it's only required once)
Verify that the files have been copied:
%sh
ls -l /dbfs/robyn/robyn_free_intercept_3.4.8.10/robyn-lib-path

Modify Robyn notebook to use these pre-installed libraries

Remove all install.packages and install_github corresponding to above packages
Note that if you do want to install packages, you should do that before adding to libPaths below

For us, we did not include reticulate above, so in our Robyn notebook we setup reticulate and then we adjust the libPaths.
After you have installed all packages in Robyn other than the preinstalled ones, adjust libPaths with a command appending your target directory to libPaths:
.libPaths(c("/dbfs/robyn/robyn_free_intercept_3.4.8.10/robyn-lib-path", .libPaths()))

At this point the R library() functions will be looking in this library path and find the preinstalled R packages.  This saves copying them to the local cluster and building related code.
Maybe in a later version we will include reticulate in the pre-installs; here I am documenting what worked quickly and well for us so others can avoid the headaches we had with slow startup time.

Hi @extrospective,
I just want to say thanks so much for both your pre-install advice and your reticulate advice.
I was going round in some serious circles getting reticulate to install nevergrad within a virtual environment and stumbling upon your post was a god-send!
I really appreciate you taking time to offer advice to the community!

Hi @extrospective. Thank you for sharing this, it was really useful. Do you have any tips on the configuration for the Databricks cluster?

authors: DaveJacques alberthupa extrospective syadalam4

repo: facebookexperimental/Robyn


text:
Dynamic hyperparameter setting

Hi Robyn team, we are actually developing a shiny tool on robyn package for our academic research purpose. We wanted to understand MMM dynamics and budget allocation and for this we are using Robyn package. When we used robyn code its giving us good results, but our need is to build a shiny app for this, so to have more dynamic approach and UI/UX functionality. So we are trying to give user to pick dynamic variables from dataset, and set these variables in robyn hyperparameters. However hyperparameters is using a list , and our variables when we concatenate alpha, gamma, theta becomes a vector of character as shown below, Can you please help us in setting up these variables as list or method how we can get these as list in hyperparameter function.

Thanks in advance.

can you share the code you're using to do this now?

Hi @kyletgoldberg, thanks for the reply.
After appending varaibles with  ( _Alpha,_Gamma,_Theta) and range values, I used the following code for a1 and b
a1 <- c("DOB_Alpha=c(0.5,3)","DOB_Gamma=c(0.5,3)","DOB_Theta=c(0.5,3)","Age_Alpha=c(0.5,3)")
b <- list(DOB_Alpha=c(0.5,3),DOB_Gamma=c(0.5,3))

it looks like you are storing the values as a long string rather than setting the values of the variable for a1. why doesnt b work?

Please reopen if this issue reoccurs.


text:
react-scripts build error

'm trying to deploy a React project using AWS CodeBuild/CodeDeploy. When I run npm run build locally on my Mac it's working fine (using WebStorm terminal). When the CodeBuild run the same command it's failing with an error that a file not found. The error is:
react-scripts build
/codebuild/output/src110814127/src/node_modules/.bin/react-scripts: 1: /codebuild/output/src110814127/src/node_modules/.bin/react-scripts: ../react-scripts/bin/react-scripts.js: not found
I need to mention that at first there was an error of access denied and I fixed it by adding the following command to buildspec.yml :
install:
commands:
chmod a+x node_modules/.bin/react-scripts
I tries to delete node_modules and reinstall npm and upgrade to the latest npm. Nothing helped.
The code was deployed before to another BeanStalk from a Windows OS and now I'm trying to push the same code to another BeanStalk from a Mac OS. Thought to mention because I saw some issues regarding this.
I also tried to install Yarn but it didn't help so I uninstalled it.
Attached is the CodeBuild log.
Thanks,
Tomer
CodeBuild_Log.txt

Hi, we're not experts in AWS CodeBuild; sorry!
I suggest you file this question on something like Stack Overflow.

Did you find a solution? I'm having the same problem when deploying using Bitbucket pipeline.
Can you add the Stack Overflow link here?

I didn't get any answer in Stack Overflow either.
Eventually I found a workaround:
I'm using AWS CodeCommit as a git server. I manually deleted the CodeCommit repository, deleted from my copy the libraries : node_modules & build. run "npm install --save" , and then pushed to the new repository. I used AWS CodePipeline to compile and push to the AWS ElasticBeanStalk. When the new repository didn't contain the node_modules and build folders, the 1st pipeline created them and then the error disappeared. There is probably a better elegant way to do this using Git commands but these steps worked for me. Anyway, it's not a React issue, just a deployment issue.

authors: Timer brahimmouhamou turpazt

repo: facebookincubator/create-react-app

license: mit


text:
docs: update jest-enzyme section

since CRA now uses the latest version of Jest under the hood,
jest-enzyme v3.2.0 is now also working perfectly fine
I've made a PR to update their docs too
https://github.com/blainekasten/enzyme-matchers/pull/99
package.json

.test.js file

note: I intentionally make the test failed (string vs number)

Thanks.


text:
ContiguousAllocation & Allocation constructor not compatibility with folly benchmark

Problem description
@xiaoxmeng  @oerling
Hi , I meet a compile error when write benchmark , seems  because of the change of
std::vectormemory::Allocation allocations_;

In file included from /usr/local/include/folly/Benchmark.h:19:
In file included from /usr/local/include/folly/BenchmarkUtil.h:20:
In file included from /usr/local/include/folly/lang/Hint.h:22:
In file included from /usr/local/include/folly/Traits.h:22:
In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/functional:62:
In file included from /usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/vector:66:
/usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/stl_uninitialized.h:137:7: error: static assertion failed due to requirement 'is_constructible<facebook::velox::memory::ContiguousAllocation, const facebook::velox::memory::ContiguousAllocation &>::value': result type must be constructible from value type of input range
static_assert(is_constructible<_ValueType2, decltype(*__first)>::value,
^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/stl_uninitialized.h:325:19: note: in instantiation of function template specialization 'std::uninitialized_copy<__gnu_cxx::__normal_iterator<const facebook::velox::memory::ContiguousAllocation *, std::vectorfacebook::velox::memory::ContiguousAllocation>, facebook::velox::memory::ContiguousAllocation *>' requested here
{ return std::uninitialized_copy(__first, __last, __result); }
^
/usr/lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/stl_vector.h:558:9: note: in instantiation of function template specialization 'std::__uninitialized_copy_a<__gnu_cxx::__normal_iterator<const facebook::velox::memory::ContiguousAllocation *, std::vectorfacebook::velox::memory::ContiguousAllocation>, facebook::velox::memory::ContiguousAllocation *, facebook::velox::memory::ContiguousAllocation>' requested here
std::__uninitialized_copy_a(__x.begin(), __x.end(),
^
/data/code/xihe-velox/./velox/common/memory/AllocationPool.h:28:7: note: in instantiation of member function 'std::vectorfacebook::velox::memory::ContiguousAllocation::vector' requested here
class AllocationPool {
^
System information
ubuntu +  gcc 10
CMake log
No response

I change the Allocation class as above  to skip the problem now.

repo: facebookincubator/velox


text:
Add support for decimal types to VectorFuzzer

Added methods to generate random UnscaledShortDecimal and UnscaledLongDecimal values. The values are capped within the range of precision provided. Used these methods to generate flat vectors.
Testing:

Created random decimal flat vectors and constant vectors.

Note: UnsafeRow testing needs to support serialize/deserialize of decimal value types. We will be skipping
decimal types in testing of UnsafeRow. Created an issue to fix this https://github.com/facebookincubator/velox/issues/3784

@mbasmanova @pedroerp
Since fuzzer has support for decimals with this chage, the test TYPED_TEST(UnsafeRowComplexDeserializerTests, Fuzzer) tries to SerDe the LONG_DECIMAL type and fails. I was able to fix the serialization and deserialization part by extending the tempaltes, but the computing of offset expects the either the UnsafeRow fields to be of 8-bytes FixedWidth or of variable length. I would like to suggest to write 128-bit decimal as a variable length data instead of treating is as a fixed width type to minimize changes to computation of offset logic.
Do you have any other suggestions?
  /**
   * @param pos
   * @param isFixedWidth
   * @return the location of the fixed size data if isFixedWidth is true,
   * return the first unwritten word for variable length data otherwise.
   */
  char* getSerializationLocation(size_t pos, bool isFixedWidth) {
    setVariableLengthOffset(alignToFieldWidth(variableLengthOffset_));
    return isFixedWidth ? reinterpret_cast<char*>(&reinterpret_cast<uint64_t*>(
                              fixedLengthData_)[pos])
                        : buffer_ + variableLengthOffset_;
  }

@karteekmurthys It sounds to me that UnsafeRowSerde doesn't support decimal types. Implementing this support may need to be a separate effort. For now, it might be sufficient to modify the test to not generate decimal types. This can be done by introducing a variation of VectorFuzzer::randRowType that takes a list of supported scalar types.
static TypePtr kSupportedTypes[]{
      BOOLEAN(),
      TINYINT(),
      SMALLINT(),
      INTEGER(),
      BIGINT(),
      REAL(),
      DOUBLE(),
      VARCHAR(),
      VARBINARY(),
      TIMESTAMP(),
      DATE(),
  };

const auto type = fuzzer.randRowType(kSupportedTypes);

@pedroerp @mbasmanova would you pls review this.

@mbasmanova @majetideepak would you please review this.

@mbasmanova would you please review this.

authors: karteekmurthys mbasmanova


text:
Add Arrow - Velox conversion support

This PR introduces PyVelox functions for the conversion of Arrow Arrays to Velox Vectors and vice-versa.

I rebased to fix the failing builds due to the arrow link change. The wheel workflow works now and make python-test should also install the extra_requires.

Looks good @sanjibansg . Can you rebase against latest main and It should be good to merge after that.

Rebased it to main, and did the format-check. Thanks!

@sanjibansg Can you look into the failing PyVelox build ?

Hi, I would like to know when will the package on pypi https://pypi.org/project/pyvelox/ to be updated to include this important change?
Thanks!

@sighingnow I have a job here to publish the new python package : https://github.com/facebookincubator/velox/actions/runs/5554843861 .

The packages are published @sighingnow , you can get it from pypi.

The packages are published @sighingnow , you can get it from pypi.

Thank you!

authors: assignUser kgpai sanjibansg sighingnow


text:
Could you please provide some example on using "Data Understanding Tool"?

Thanks for updating the paper.
In the updated paper, you mentioned you have implemented a "data understanding tool" based on world model. This is super useful and important.
Could you provide some example on how to use the tool?

Sure. We will have a related diff coming out soon. Once it is done, you'll be able to run ml/rl/test/gym/world_model/mdnrnn_gym.py to get feature importance/sensitivity of any gym environment.

Expect timeline: 2 weeks.

Thank you! Look forward to it!

Any updates on "Data Understanding Tool"?

Hi,
Sorry for some delay. Now you can use the following command to check feature importance and feature sensitivity in the cartpole environment:
python mdnrnn_gym.py -- -p ml/rl/test/configs/mdnrnn_cartpole_v0.json -f -s

The output should be something like this:
INFO:ml.rl.evaluation.world_model_evaluator:**** Debug tool feature importance ****: tensor([18.9650,  9.1601,  0.1277, 13.4917,  0.7331, 12.0240])
[2019-06-19 13:48:59,942] **** Debug tool feature importance : tensor([18.9650,  9.1601,  0.1277, 13.4917,  0.7331, 12.0240])
action 0, feature importance: 18.964975357055664
action 1, feature importance: 9.16006088256836
state 0, feature importance: 0.1277211308479309
state 1, feature importance: 13.491726875305176
state 2, feature importance: 0.7331321239471436
state 3, feature importance: 12.024038314819336
INFO:ml.rl.evaluation.world_model_evaluator: Debug tool feature sensitivity ****: tensor([0.0067, 0.2099, 0.0066, 0.3125])
[2019-06-19 13:49:07,774] **** Debug tool feature sensitivity ****: tensor([0.0067, 0.2099, 0.0066, 0.3125])
state 0, feature sensitivity: 0.006689509842544794
state 1, feature sensitivity: 0.2099362462759018
state 2, feature sensitivity: 0.00659541692584753
state 3, feature sensitivity: 0.31252968311309814

repo: facebookresearch/Horizon


text:
Inquiries about korean datasets utilized in the CCNet pipeline

While studying data pipelines, I found CCNet. CCNet is very intriguing to me. I'm going to use CCNet to create a better data pipeline for Korean datasets.
I have a question. In the paper, it is stated that CCNet conducted a study with the "Feb. 2019 snapshot of Common Crawl" dataset.
I wonder how many Korean datasets are in that dataset.
In the paper, the size of the datasets in table 6 is written as the size after data preprocessing. I wonder if the data preprocessing is only deduplication. Also, I'm curious about the size of the Korean dataset before the data preprocessing. If you share the size of the Korean dataset, it will be of great help to me who is conducting research using CCNet.

Hi, the processing pipeline is mostly:
CommonCrawl -> Deduplication at paragraph level -> Language detection -> optionally LM based filtering.
In the case of Korean we did train a LM on Korean Wikipedia and kept only the top 30% of text according to this LM.
The final number of "clean" Korean is reported in the paper.

authors: gwenzek hyunmokky


text:
What is the parameter number of mbart-large-one-to-many-mmt?

What is the parameter number of mbart-large-one-to-many-mmt?
I could not find any information on the web.
Thanks.

Closing since I found the answer
from transformers import MBartForConditionalGeneration
model = MBartForConditionalGeneration.from_pretrained("facebook/mbart-large-50-one-to-many-mmt")
model.num_parameters()

--> 610879488

repo: facebookresearch/fairseq


text:
[Bugfix] Refactor virtual function calls in ctors and dtors.

Motivation and Context
Numerous virtual function calls were being called from constructors or destructors.  This is bad in that it bypasses virtual dispatch (i.e. the functions do not behave as virtual anymore).  This PR addresses these situations by either specifying the owning class in the call (in effect manually bypassing virtual dispatch) or changing function to no longer be virtual (Note : close() in Simulator was marked as virtual, but is no longer).

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Assuming the new clang-tidy checks pass, merge it in.

repo: facebookresearch/habitat-sim


text:
Might want to add a tip to replace conda with mamba which is optional but strongly recommended (dep resolution goes from ~40 seconds to ~5 seconds).

          Might want to add a tip to replace conda with mamba which is optional but strongly recommended (dep resolution goes from ~40 seconds to ~5 seconds).

Originally posted by @exhaustin in https://github.com/facebookresearch/home-robot/pull/36#discussion_r1110176117

Resolve in #58

repo: facebookresearch/home-robot


text:
[wip] better recommend operator for NGOpt8

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue

How Has This Been Tested (if it applies)
will not be merged before additional tests
Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CLA).
[x] All tests passed, and additional code has been covered with new tests.

Re-implemented in branch "rdo", in another pull request.

repo: facebookresearch/nevergrad


text:
Add snap packaging

Add snap packaging together with the associated workflow.
The snap may be still a little rough but loading/saving mcap file works.
Let me know if you test it and find any issue.
The workflow will automatically publish the snap to the store if/once:

you register the snap name mcap-editor
create a store token as explained here

Awesome

Seems to have an issue: https://github.com/facontidavide/mcap_editor/actions/runs/8003424007/job/21859531118#step:2:8

Seems to have an issue: https://github.com/facontidavide/mcap_editor/actions/runs/8003424007/job/21859531118#step:2:8

I will look into it asap. At least it is only the very final cleanup step that failed. As a result, the artifact if available here.

If I'm not mistaken now I should be able to install it with snap. However, I am getting the following error:
$ sudo snap install mcap-editor

error: snap "mcap-editor" not found

authors: artivis facontidavide szepilot


text:
The following RangeError was thrown attaching to the render tree

When I run the simulator, I get the following error.
I do not get an error when I run my phone (apk, ipa).

That's probably because the simulator doesn't have a camera


text:
[Feature request] return image when QR code is read

I would like to store the image in which the QR code was recognized.  I'm looking for suggestions about how to participate properly in getting such an enhancement approved and implemented.  I'm willing to work on it.

Looking at other's comments, I see I can simply take a photo when the QR code is recognized.  Will pursue that.

How did it work? I am trying to do the same but it was a mess as i have to dispose the controller and initialize the camera controller and still somehow the image is very very dim. Did you make it work?

I did not pursue this to implementation.  Knowing the presumed solution, I went on to other things.  I still hope to store the image with the QR code in it and will either figure out how to get all the controllers aligned or perhaps dust off my Objective C or whatever and dig into the component.  Sorry I can't be of more help at this point.

authors: ShiroYacha cfransen giraffe-team


text:
Add loguru

I was getting loguru requirement error when running kim_developmental_ccf_mouse windows 10 conda env (python 3.8)

Sorry these PR keep defaulting to wrong branch

repo: faekronman/bg-atlasgen


text:
未知情况关机

今天早上发现服务异常了，检查了下proxy和api_server都在昨天同一时间关机了，但是不知道是什么原因造成的
我的proxy启动命令
nohup ./proxy --addr=0.0.0.0:7000 --addr-rpc=0.0.0.0:9091 --addr-store=etcd://0.0.0.0:2379 --namespace=test &
proxy 的 shutdown日志，是10：31直接关掉的，没看到有任何访问

api_server的 shutdown日志也是这样的

应该可以看到在 10：31之前是很久没有访问的，是不是有什么默认的检查机制，自己shutdown？
附上我的api 和server创建的部分代码，Cluster是我开头就创建好的ID为1的

最好那个图片的Server地址是127.0.0.1：7002 我当时是用127.0.0.1:7001，跟这个是没有关系的

因为程序里面捕捉了SIGNUP信号，我用的ssh连接的阿里云主机，nohup完毕之后，关闭terminal会产生这个信号，应该exit退出，就不会有这个问题了

repo: fagongzi/gateway


text:
Add fahadhaneefa's file

New file create for second slide page

Patch#1 merged with master

repo: fahadhaneefa/github-slideshow


text:
Fix module not found and typing-extensions not installed

ModuleNotFoundError: No module named 'termspark.text_styler.constants'

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7f574ea) 100.00% compared to head (c21d892) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #72   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           57        57
  Lines         1751      1751
=========================================
  Hits          1751      1751

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter faissaloux

repo: faissaloux/termspark


text:
A string in a query value is not attempted to be parsed as a Date before comparing

I think we should try to parse it before considering it as a real String.

This query should work in fongodb : {"creationDate":{"$gt", "2015-01-06"}}
It does not because the date value is of type String. We should try to parse it.

Thanks !

Hi @libetl,
do you have a reference for this ?
I try to reproduce on a real mongodb, and this is not working
> db.db.find();
{ "_id" : 1234, "var1" : "val1", "created" : ISODate("2015-02-04T00:02:01.719Z") }
{ "_id" : 2345, "var1" : "val2", "created" : ISODate("2015-02-06T00:02:01.719Z") }

> db.db.find({created:{$gte:ISODate("2015-02-04T00:02:01.719Z")}});
{ "_id" : 1234, "var1" : "val1", "created" : ISODate("2015-02-04T00:02:01.719Z") }
{ "_id" : 2345, "var1" : "val2", "created" : ISODate("2015-02-06T00:02:01.719Z") }

> db.db.find({created:{$gte:ISODate("2015-02-04")}});
{ "_id" : 1234, "var1" : "val1", "created" : ISODate("2015-02-04T00:02:01.719Z") }
{ "_id" : 2345, "var1" : "val2", "created" : ISODate("2015-02-06T00:02:01.719Z") }
> db.db.find({created:{$gte:"2015-02-04"}});

and :
> db.db.find({created:{$gte:"2015-02-04"}});
>

I also check your TestCase againts MongoDB (if you pass FongoRule(true) it check againts a real mongodb instance) and you test fail.
Can you provide me more information ?

Hello,
That was a mistake. I cannot figure out why, but when I insert an ISO date in string format (i.e. "2014-01-07T13:33:57.229Z"), it is converted automatically in a real ISODate. Is it related to the java mongo driver ?
I am going to revert the change. It is not supposed to work.

if you want to query a date, in mongo shell, you can use the $date operator (>= 2.6).

authors: libetl twillouer

repo: fakemongo/fongo