Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do I undo `-FIRAnalyticsDebugEnabled`?

I just added FIRAnalyticsDebugEnabled as a launch argument as was suggested in several places:

  1. The Xcode console:

    6.5.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see [https://help.apple.com/xcode/mac/8.0/])
    
  2. The Get Started with Google Analytics for iOS guide:

    enter image description here

  3. Etc.

Once I enabled it, I started seeing output such as:

Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: session_start (_s), {
    firebase_debug (_dbg) = 1;
    firebase_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    session_id (_sid) = 123;
    session_number (_sno) = 2;
}

Now that I know that events are being output properly, I want to disable this as it is spamming the console. However, none of those resources mentioned above talk about how to disable it.

How do I disable it?

I tried removing the launch argument, but the logs still appear.


Note that this is not a duplicate of these similar questions:

  • How to stop Firebase from logging status updates when app is launched -- OP never enabled FIRAnalyticsDebugEnabled and is asking about how to disable the message telling them to enable FIRAnalyticsDebugEnabled (among others).
  • Completely disable Firebase/Analytics to stop console spam on app startup -- same as above.
like image 362
Senseful Avatar asked May 15 '26 12:05

Senseful


1 Answers

Many places will tell you to add the launch argument -FIRDebugDisabled but because I didn't have it prior to enabling -FIRAnalyticsDebugEnabled, that seems odd.

It took a while to find, but the page on DebugView has some key information:

To enable Analytics Debug mode on your development device, specify the following command line argument in Xcode :

-FIRDebugEnabled

This behavior persists until you explicitly disable Debug mode by specifying the following command line argument:

-FIRDebugDisabled

The key here is that the "behavior persists." It appears that -FIRAnalyticsDebugEnabled is behaving the exact same way in that it persists: you only need to run it once.

Thus to get back to the state you were in before running with -FIRAnalyticsDebugEnabled:

  1. Run the app once with the -FIRDebugDisabled launch argument.
  2. Remove the launch argument.
like image 187
Senseful Avatar answered May 17 '26 01:05

Senseful



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!