@vincentk42 nothing to worry about here, just some things that three.js does in it’s compatibility check.
TL;DR:
@ben made a cool workaround which prevents this from happening, I already updated the Flappy Snack to use it!
There are some API things in WebGL that don’t line up with OpenGL ES (The native version of OpenGL ).
As far as I know this isn’t preventing us from anything, and in the future we could PR three.js to better support EXGL.
Our current solution is to use a filter on console.warn to prevent those specific warnings! We do this through expo-three: ^2.0.7 using something like this:
import {THREE} from 'expo-three' // <- This manages the global instance of three
class App extends React.Component {
componentWillMount() {
THREE.suppressExpoWarnings(true)
}
componentWillUnmount() {
THREE.suppressExpoWarnings(false)
}
}