react native expo run web is showing some permission issue - react-native

I am trying to run react native project using expo package on web browser.
but I am getting error message.
Commands executed
yarn install - installed all packages.
expo start - executed very well no issue
npm install react-native-web - no issue
npm install react-dom packages - no issue
expo start - no issue
pressed w - no issue
Browser opened up but in console it says something like.
The issue
Uncaught Error: react-native-permissions: NativeModule.RNPermissions is null. To fix this issue try these steps:
installed npm packages

Related

the development server returned 500 react native

I started a new react-native project and I suddenly got this error for no reason and every time I add a package the app can't read and it shows an error for that package for example react-navigation. I tried reinstalling the app countless times but the problem never got fixed.
package.json
You have to install react-native-gesture-handler.
yarn add react-native-gesture-handler
or
npm install react-native-gesture-handler

My gesturehandler is not working while using expo cli

I installed gesturehandler but I think it did not install successfully. It gives vulnerabilities issues during import.
I imported it but it was not working. When I do expo start, it gives me this error:

Graphql error when building react-native app

I'm getting this error on node when I try and npm run android my react native app
Unable to resolve "./printError" from
"node_modules/graphql/error/index.js
The error only occurs when attempting to import any libraries that require Graphql. Graphql is installed, and I've uninstalled and reinstalled my node_modules several times attempting to fix this but nothing works. Any help would be appreciated.
printError was added with v0.12.0. Apollo requires at least v14.5.4. You can install the latest version with npm install graphql#latest.

How to solve this error, Uncaught Error: 36.0.0 is not a valid SDK version. Options are 35.0.0, 34.0.0, 33.0.0, UNVERSIONED

I am working on React native new project when I enter npm start I got this error on my Mobile with blue screen Uncaught Error: 36.0.0 is not a valid SDK version. Options are 35.0.0, 34.0.0, 33.0.0, UNVERSIONED. I tried to solve this error by using these commands
npm install (for node module)
expo update
npm install react-native-gesture-handler --save
npm start
But It didn't work, please help me to resolve this issue.
As said here, you can try to delete the expo client on the emulator, and run the project again. This should work.
Here's the documentation of how to upgrade your expo version, but i think you don't will need it, because you're on the latest version.

"could not connect to development server" error running React Native tutorial with Expo, suspecting Watchman

New to react native and mobile dev, running into this problem:
I am running the React Native hello world from the Facebook Website using Expo CLI as the build tool. What I did was to install Expo, run expo init test, install cocoapods, and cd into the test directory and run expo start.
When I open the app on iOS simulator or my iPhone, I get "Could not connect to development server" after about 3-5 minutes in white screen (see screenshot).
In the Expo logs. It is notable that upon every startup I get the following error logs:
2019-08-25T21:49:21,474: [cli] Failed to open /Users/nsadeh/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Not a directory
ERROR
21:49
Watchman: watchman --no-pretty get-sockname returned with exit code=null, signal=SIGABRT, stderr= 2019-08-25T21:49:21,474: [cli] Failed to open /Users/nsadeh/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Not a directory
I have already tried un- and reinstalling Watchman as well as Expo. Not sure what else to do.
To reproduce:
macOS Mojave 10.14.6
node v10.16.3
expo 3.0.10
Watchman 4.9.0
react-native 0.59.10
Run expo init and from the top directory expo start.
Solution: turns out that postgreSQL left an unrelated LaunchAgents.plist file in my Library that was confusing Watchman. Renaming it resolved the issue.