Erik Montes

@chaudhuri will you consider changing the Github issue label from just `text` to possibly `documentation`. I think it would be more meaningful.

I was on expo-cli 6.0.5 and this is still happening. I downgraded to **5.6.0** as @justro suggested and it works.

For me this happens as soon as I upgrade to `3.6.0`. Works fine with `3.5.10`, so yes something must have changed in `3.6.0+`. Here's what I'm using: ``` "react": "17.0.1",...

@Anthony-Buisson @bd-arc can you please merge this 🙏🏼

@HichamELBSI this seems to be fixed? I couldn't reproduce.

Update: you can now update to v2.0.0 which finally removes SafeArea from the library, so this will not be an issue.

From the various graphql servers alternatives, in our experience the easiest one to migrate over to, almost a drop in replacement, was [GraphQL Yoga](https://www.the-guild.dev/graphql/yoga-server) with their [Express integration](https://the-guild.dev/graphql/yoga-server/docs/integrations/integration-with-express).

From the various graphql servers alternatives, in our experience the easiest one to migrate over to, almost a drop in replacement, was [GraphQL Yoga](https://www.the-guild.dev/graphql/yoga-server) with their [Express integration](https://the-guild.dev/graphql/yoga-server/docs/integrations/integration-with-express).

From the various graphql servers alternatives, in our experience the easiest one to migrate over to, almost a drop in replacement, was [GraphQL Yoga](https://www.the-guild.dev/graphql/yoga-server) with their [Express integration](https://the-guild.dev/graphql/yoga-server/docs/integrations/integration-with-express).

> @savayer Not a real solution, but disabling the shiver animations by setting the `animate` prop to`false` fixes the issue. > > The error originates from the `react-native-svg` package, so...