Skip to content
This repository has been archived by the owner on Jun 13, 2019. It is now read-only.

Only print statements from 1st view controller appear in dotzu log #31

Closed
Mozahler opened this issue May 18, 2017 · 7 comments
Closed

Comments

@Mozahler
Copy link

I have a tab bar controller with each view controller inside a navigation controller getting its own tab. In Xcode I get log messages that don't appear in the app (dotzu's green and black screen). It seems I only get messages from the 1st view controller, but not the 2nd. Do I need to enable in each file, or just in the AppDelegate.swift file? What else could I be doing wrong?

@wwe-johndpope
Copy link

paste the code in a gist.
did you set a break point? maybe the print logging is not being invoked.
try with print ("Test")

@Mozahler
Copy link
Author

why would it be invoked in one view controller and not the other? the only "code" is:

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        Dotzu.sharedManager.enable()
....
}

@johndpope
Copy link

what logging are you using?

Logger.verbose("Test")

Do you have some settings switched off in app screen to disable some conditions?

@remirobert
Copy link
Owner

very strange, as @johndpope which Logger are you using.
Even if you are using print, you will need to import Dotzu everywhere.

@Mozahler
Copy link
Author

Mozahler commented May 21, 2017 via email

@remirobert
Copy link
Owner

So you can initialise Dotzu everywhere in your app.
Dotzu will analyse everything by default.
If you want only a specific class, you will need to enabled and disabled Dotzu.

@remirobert
Copy link
Owner

remirobert commented May 22, 2017

@Mozahler Here what you can do :

//When you enter in the controller
Dotzu.sharedManager.enable()

//When you leave the controller
Dotzu.sharedManager.disable()

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants