Systemic 2 crashing / not opening in MacOs 10.12.3

[carlostib]

Hi,
I downloaded Systemic 2 for Mac but is not opening. I had already installed R in my system (since I work on Data Science and Machine Learning stuff), and I installed recent version of Java JDK 8 from oracle site, and when clicking on "Systemic" app, it just doesn't open, is not even appearing anything in the dock.
System log file is saying the following when trying to open Systemic app:
"(com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.11865): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/XPCServices/RootDebuggingXPCService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
".
Seems a conflict with XCode permissions or something. Please advise so I can use your app. Alternatively, please let me know if I can explore data and use your R library just the same as I have R Studio already installed.

Thanks for your feedback.

[vizcacha]

I'm experiencing the same issue. My system log shows

Mar 6 21:26:06 Stevens-MBP com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.66555): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/XPCServices/RootDebuggingXPCService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
Mar 6 21:26:06 Stevens-MBP com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.66555): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/Frameworks/DFRSupportKit.framework/Versions/A/XPCServices/IDETouchBarSimulatorService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex

[Abelink23]

I've exactly the same problem. The system.log that I have at /private/var/log doesn't report anything. However, I managed to open the program by Showing Package Contents option and then running the Systemic executable that is in Contents/MacOS
I guess this is not the right way to open it and maybe there will be some data missing...
Waiting for your answer...

[stefanoaz]

I see the same symptoms with the same syslog message from V2.200. The workaround Abelink23 found, also worked for me. Using OS 10.12.5.

[caballerodiez]

damn, i'm gonna hang myself from a tree
systemic 2 doesn't run in my mac os Sierra on Virtual box
not sure what i'm doing wrong
i installed R and java, tried deleting the java_cmd.txt, and tried the workaround you have suggested.. nothing works
could you please help me?

[caballerodiez]

solved.

[yuyuan-huang]

How to solved

[caballerodiez]

i installed the wrong version of R

[dianadianadiana]

Hello, I was having the same exact problem as carlostib where I downloaded Systemic 2 for Mac and it just didn't open at all and didn't bounce around in the dock. I have a Mac OS Sierra 10.12.6.

• I believe the R version is fine since someone else I know, who has Systemic 2 working, also has the same R version as me:
  R version 3.4.1 (2017-06-30) -- "Single Candle"
  Copyright (C) 2017 The R Foundation for Statistical Computing
  Platform: x86_64-apple-darwin15.6.0 (64-bit)

• The Java version is different from my colleague's. I followed the directions and installed Java JDX 9 (when it asked Java JDX 7 or higher). The output of the version is:
  java version "9"
  Java(TM) SE Runtime Environment (build 9+181)
  Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)

Whereas for my colleague, he has something along the lines of Java 1.8. I then tried deleting the java_cmd.txt like suggested, but no luck. I believe there is something wrong with the Java set up but I'm not very sure how to fix it..

Nonetheless, the workaround that Abelink123 suggested works in the sense that the application now opens and works (yay!).

Sorry for the lengthy monologue but I just wanted to put all and any information out there that might be useful for anyone who is also having this problem so that they try the workaround by Abelink123 and hopefully it works :)