All of a sudden, RStudio is not able to start R. Just did a Mojave system update to OSX 10.14.6. R version is 4.02. Reinstalled RStudio just to be sure. R starts up just fine on its own.
I get the following error when starting RStudio:
Error Starting R
The R session failed to start.
ERROR MESSAGE
[No error available]
PROCESS OUTPUT
The R session process exited with code 6 .
ERRORS
dyld: Symbol not found: _GEkillDevice Referenced from: /Applications/RStudio.app/Contents/MacOS/rsession
Expected in: flat namespace
in /Applications/RStudio.app/Contents/MacOS/rsession`
I have not used Homebrew for R or RStudio. I always install RStudio and R updates by hand rather than through Homebrew. I install R from a CRAN repository.
This happened quite suddenly after the latest Mac system update. I can't help but think it is somehow related. I can't think of anything else I changed that might have caused this.
Have you updated XCode? Did you runs the command line checks in the linked thread? Catalina and R4.02 and RStudio's current release play well together on my 2015 Airbook, so it seems likely that it is a system library problem.
I have the latest version of XCode for Mojave. Nothing has changed since two days ago when everything worked. The only intervening event is the automatic security upgrade to OSX.
Let me explain precisely what happens when I try to start RStudio: A window opens with the error message. (I have uploaded an image of the window.) There is no debug information, no chance to load RStudio for debugging. Nothing. Just the error window. When I close the window, RStudio closes.
Again, I have updated R and do not have redundant installations. R runs fine either from R.app or from Terminal.
If macOS, XCode, RStudio and R are not at these versions, they must be all at previous versions that sync up.
The error message is obscure. GEkillDevice been reported on RStudio with iMac in the thread referenced, in connection with the Slackbuild package manager and in R.2.7.0. Beyond this only a handful of other posts reference it.
If R was installed on a user level, rather than in /Library/Frameworks/R.framework the error might occur.
My suggestion is to upgrade all the environment to the versions above, taking care to install R from the notarized package on CRAN for all users.
It seems there was an issue with Cylance rather than just notifying that RStudio was "trying an exploit", it treated the new version more harshly and blocked access that it needed. Just quitting the app is not enough, you have to uninstalled Cylance completely. Installing it back afterwards should allow you to use both.
