InjectionX does not work on AppCode 2018.2.3 using XCode 10.0

[donirn]

Hi, I am using AppCode 2018.2.3 to run my app. The XCode I'm using is version 10.0.
When I run it with XCode and a same configuration, it works fine. But, when I tried it on AppCode, it produced an error.

I'm already adding [[NSBundle bundleWithPath:@"/Applications/InjectionX.app/Contents/Resources/iOSInjection.bundle"] load]; to my AppDelegate and turning off code coverage for the scheme.

But still I got an error:

*** Compiling /Users/doni.ramadhan/Projects/TheProject/Something.m ***
Loading .dylib - Ignore any duplicate class warning...
*** dlopen() error: dlopen(/Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval101.dylib, 2): Symbol not found: ___llvm_profile_runtime
  Referenced from: /Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval101.dylib
  Expected in: flat namespace
 in /Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval101.dylib ***
*** Compiling /Users/doni.ramadhan/Projects/TheProject/Something.m ***
Loading .dylib - Ignore any duplicate class warning...
*** dlopen() error: dlopen(/Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval102.dylib, 2): Symbol not found: ___llvm_profile_runtime
  Referenced from: /Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval102.dylib
  Expected in: flat namespace
 in /Users/doni.ramadhan/Library/Containers/com.johnholdsworth.InjectionX/Data/eval102.dylib ***

Can you help me on what I did wrong? Or maybe AppCode using XCode 10 is not supported yet?

[johnno1962]

Hi, this usually comes up when you have "gather coverage statistics" turned on in your scheme.

[donirn]

Yes, I already disabled that in my scheme. Specifically this line:
codeCoverageEnabled = "YES" in .xcscheme.

It is working on XCode 10, but not on my AppCode.

[donirn]

Hi, I'm raising this issue on AppCode forum. Since I'm suspecting AppCode uses something on LLVM that prevents injection app to use LLVM.

https://intellij-support.jetbrains.com/hc/en-us/community/posts/205809099-Does-appCode-use-LLVM-?page=1#community_comment_360000171939

[zenangst]

@donirn hey mate, any news on this?

[donirn]

@zenangst There is no response from JetBrains.
I have created a new post there https://intellij-support.jetbrains.com/hc/en-us/community/posts/360001481799-Does-AppCode-2018-2-4-use-LLVM-, perhaps they would answer if it is a new post.

Have you tested InjectionIII in AppCode?

[zenangst]

Nope not yet. But I have used Injection with other editors (other than Xcode), and that worked perfectly.

[yeswolf]

The main issue here is that AppCode uses a separate DerivedData in ~/Library/Preferences/AppCode(major).(minor). There is a reason for that: many users work with their project simultaneously in Xcode and AppCode, and there is a use-case when one wants to debug his application in AppCode and run tests in the Xcode at the same time (and many others).

I have a fix for this issue (by idenfifying IDE that is currently active), however I already see changes in master and quite a bit of changes in swift-conversion branch. So, I'm not sure, which branch to choose for PR. @zenangst Could you please suggest, which one to use?

[johnno1962]

Hi, Thanks for this! Please file your PR against the swift-conversion branch which will be the basis of the next release. AppCode should already work using Xcode’s DerivedData. You just need to be sure to build using Xcode each time you add a file to the project.

[yeswolf]

Hi, Thanks for this! Please file your PR against the swift-conversion branch which will be the basis of the next release.

Ok, will do.

[yeswolf]

Actually, after testing the swift-conversion branch I see that it works in AppCode, because some of modifications, like tracking not only "renamed" flag, are already implemented. As adding a file causes problems both for Xcode and AppCode and requires rebuilding the project, I think that most of use cases are already covered. Thank you, @johnno1962! In case of any further issues with AppCode - I'm ready to help.