Dlog not supported by Dyci

[prabhakaran-p-1044]

Am using xcode and my project is configured to use DLog preprocessor than the default NSLog. I couldn't use Dlog in injectable code section. please let me know if I am missing any.

[PaulTaykalo]

Can you be more specific about the issue

1. Does the other classes in your project works fine& (I mean, can you inject them successfully?)
2. What actully you trying to change? (Methods, defines, or something else)
3. If you can add simple project that is reproducing this issue, It will be easier to find the source of the issue.

Thank you.

[prabhakaran-p-1044]

Hi,

Sorry for  late reply.

I couldn't reproduce the issue in my test project.

To answer your questions :

1. Am using Xcode.
2. No, I couldn't inject any of the classes in this project (Tried on viewcontroller, NSObject, uitableviewcell, Uiview, NSOperation subclasses)
3. Still testing the project, tried to only print a log and show alert in "updateOnClassInjection" method.
4. The issue occurs only in the project I am currently working on and I can't share the source code (sorry).

This is the shared project and my team mate is having the framework path is different directory, hence I have to remove and add the framework
everytime we integrate our code. could that be causing the problem, coz it worked perfectly on the first time i tried the framework.
and it never worked after I re-opened the project next day.

Thanks,
Prabhakaran
 

---

From: tt.kilew notifications@github.com
To: DyCI/dyci-main dyci-main@noreply.github.com
Cc: friendtam prabhakaran_dravid@yahoo.com
Sent: Tuesday, March 5, 2013 1:35 PM
Subject: Re: [dyci-main] Dlog not supported by Dyci (#19)

Can you be more specific about the issue
0) AppCode or Xcode?

1. Does the other classes in your project works fine& (I mean, can you inject them successfully?)

2. What actully you trying to change? (Methods, defines, or something else)

3. If you can add simple project that is reproducing this issue, It will be easier to find the source of the issue.
   Thank you.
   —
   Reply to this email directly or view it on GitHub.