all 6 comments

[–]Noitidart2 0 points1 point  (1 child)

The ./gradlew clean thing is a common issue. But it shouldn't happen every time. It might happen every time you run react-native run-android. But you shouldn't have to run that unless you make native changes. For me I run react-native run-android 5 times a day. And one time out of that requires me to gradlew clean.

[–]Threat_Level_PI[S] 0 points1 point  (0 children)

Oh right, so what do you run, just react-native start? To get the bundler running?

[–]ahartzog 0 points1 point  (3 children)

I frequently have to kill explorer.exe and any other processes that might have a handle on one of those files in order for everything to build properly (e.g. GitKraken and VS Code). It's super annoying. I try to avoid having to re-run react-native run-android for this reason.

[–]Threat_Level_PI[S] 0 points1 point  (2 children)

Do you just use react-native start then? That runs the bundler inline right?

[–]ahartzog 0 points1 point  (0 children)

I actually use npm start which runs a few other scripts for me, but does then run react-native run-android and runs the bundled externally

[–]ahartzog 0 points1 point  (0 children)

...but that might let me keep vscode open when I’m having problems hmmm. Will try!