Solved: SES was being broken by a transformation #659 (comment)
When importing and calling lockdown() in a React Native context, the following error appears:
entry index.js file
import { AppRegistry } from 'react-native';
import App from './App';
import { name as appName } from './app.json';
import './lockdown.umd.js'
lockdown({ errorTaming: 'unsafe'})
AppRegistry.registerComponent(appName, () => App);ELI5 React Native Setup:
yarn install -g expo-cli
expo init LockdownBug
cd LockdownBug
Add lockdown.umd.js in the project root
Then, inside index.js:
import { registerRootComponent } from 'expo';
import App from './App';
import './lockdown.umd'
lockdown({errorTaming: 'unsafe'})
// registerRootComponent calls AppRegistry.registerComponent('main', () => App);
// It also ensures that whether you load the app in the Expo client or in a native build,
// the environment is set up appropriately
registerRootComponent(App);Finally,
This opens a debugging tab with the error present!
Solved: SES was being broken by a transformation #659 (comment)
When importing and calling
lockdown()in a React Native context, the following error appears:entry
index.jsfileELI5 React Native Setup:
Add
lockdown.umd.jsin the project rootThen, inside
index.js:Finally,
This opens a debugging tab with the error present!