You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading to React Native 0.44 (from 0.43) when calling AccessibilityManager.setAccessibilityContentSizeMultipliers I get this red screen
Reproduction Steps and Sample Code
We call this method in our root component's componentDidMount and it worked just fine so far. I created a snack https://snack.expo.io/ryOh1Migb but can not reproduce exception there. I am not sure which version of react-native expo v16 uses though.
Additional Information
React Native version: 0.44.0
Platform: iOS
Development Operating System: macOS
Dev tools: Xcode 8.3.2
The text was updated successfully, but these errors were encountered:
Looks like the implementation of RCTDeviceInfo.m broke this, as the RCTAccessibilityManagerDidUpdateMultiplierNotification notification is being posted on the JS thread rather than the main thread, breaking the assertion in RCTExportedDimensions.
This is effectively blocking upgrades to RN 0.44 for anyone setting custom accessibility content size multipliers. Is this being looked at for RN 0.45?
Summary:
The `UIManager` already has a lot of responsibilities and is deeply
tied with React Native's view architecture. This diff separates out a
`DeviceInfo` native module to provide information about screen dimensions and
font scale, etc.
Reviewed By: fkgozali
Differential Revision: D4713834
fbshipit-source-id: f2ee93acf876a4221c29a8c731f5abeffbb97974
Description
Since upgrading to React Native 0.44 (from 0.43) when calling
AccessibilityManager.setAccessibilityContentSizeMultipliers
I get this red screenReproduction Steps and Sample Code
We call this method in our root component's
componentDidMount
and it worked just fine so far. I created a snack https://snack.expo.io/ryOh1Migb but can not reproduce exception there. I am not sure which version of react-native expo v16 uses though.Additional Information
The text was updated successfully, but these errors were encountered: