Firebase iOS Debug Console not logging anything

Question

I have setup firebase in both the console and in the app. Everything configures correctly, and events appear to be logging in the app.

Output to console:

<FIRAnalytics/DEBUG> Logging event: origin, name, params: app, 
log_something, {
        "_o" = app;
        "full_text" = khbsdpibdsjl;
        name = lwkjbgskljsavdkjl;
    }

I have the debug flag enabled: -FIRDebugEnabled.

Yet in the debugging events console there is NOTHING. I see no devices available, no events being logged, absolutely 0 indication of anything connected. I must be missing something?

edit: I have been following this for setting up Debugging Events. https://firebase.google.com/docs/analytics/debugview#enabling_debug_mode

I am seeing events in the StreamView, but nothing in the debug view even though I have debug mode enabled.

For me at least, no events were being logged when I was testing the analytics logging feature on the simulator. However, when I tried it on an actual iPhone, it worked! — mj23, Sep 06 '21 at 02:01

score 44 · Answer 1 · edited Aug 13 '23 at 20:33

44

Try this , This is work for me ,

Follow below steps ,

1.In Xcode, select Product → Scheme → Edit Scheme.

2.Select Run from left Menu and Select Arguments tab In the Arguments Passed on + option

add -FIRDebugEnabled

For detail debug view follow steps DebugView track Firebase doc

To send an event in Xcode project follow code below,

Objective C

[FIRAnalytics logEventWithName:@"share_image"
                    parameters:@{@"name": name, @"full_text": text}];

Swift

Analytics.logEvent("share_image", parameters: ["name": name, "full_text": text])

For events log follow detail steps Log events in Application Firebase doc

Hope this will help someone.

edited Aug 13 '23 at 20:33

Westy92

19,087
4
72
54

answered Mar 26 '19 at 12:06

Jaywant Khedkar

5,941
2
44
55

1

You can understand the effect of the visuals from this answer. – mkeremkeskin Sep 30 '19 at 12:29
1

This also helps to run via the VSCode later. – Cyber Oct 02 '22 at 11:46

score 29 · Answer 2 · answered Feb 21 '18 at 19:07

29

Make sure to remove the OS_ACTIVITY_MODE:disable from the Environment Variables in your project scheme if you added it at some point.

answered Feb 21 '18 at 19:07

Esteban Chavarría Solano

351
4
4

someone had put `OS_ACTIVITY_MODE=${DEBUG_ACTIVITY_MODE}` in our debug build, which was sometimes enabled and sometimes disabled, depending on what version of XCode you were running – jes5199 Oct 25 '19 at 17:33

score 28 · Answer 3 · answered Aug 12 '19 at 13:04

28

Make sure to add ONE DASH before -FIRDebugEnabled

I wasted a whole day making silly mistake having missed that DASH

Hope that doesn't happen to others!

answered Aug 12 '19 at 13:04

Dhaval H. Nena

3,992
1
37
50

2

It has been 3 years since you commented and it still help :D – Toan Tran Van May 05 '22 at 07:14
Glad it still helps :) – Dhaval H. Nena Sep 14 '22 at 13:27
1

still helping. I wasted a whole day trying to figure this out and nothing worked but this – Maruta Aug 29 '23 at 09:33
Glad to know that it still helps :) @Maruta – Dhaval H. Nena Aug 29 '23 at 11:12

score 21 · Answer 4 · edited May 08 '19 at 14:21

21

Now it doesn't matter much but still for the people who are getting errors on this issue. Debug mode of firebase analytics does not work sometimes due to issue in GoogleServices-Info.plist file Simply makes these 2 changes.

Set IS_ANALYTICS_ENABLED to YES
Set FIREBASE_ANALYTICS_COLLECTION_DEACTIVATE to NO

edited May 08 '19 at 14:21

RKRK

1,284
5
14
18

answered Mar 26 '19 at 08:36

Abdullah

227
4
13

Thanks a lot. These two keys solved my problem. – hakki Feb 22 '21 at 14:56
2

Does the key `FIREBASE_ANALYTICS_COLLECTION_DEACTIVATE` is still relevant? new `GoogleServices-Info.plist` files do not contains such field – genericUser Nov 02 '21 at 14:42
isn't it FIREBASE_ANALYTICS_COLLECTION_DEACTIVATED – MindBlower3 Sep 14 '22 at 11:36
@Abdullah, thank you so much! I would not have guessed that the plist would have an analytics flag disabled! Wow. – Rethunk Aug 04 '23 at 11:56

Reimond Hill · Answer 5 · 2020-08-11T16:16:47.730

10

Alternatively you can do that inside your AppDelegate:

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {

    var newArguments = ProcessInfo.processInfo.arguments
    newArguments.append("-FIRDebugEnabled")
    ProcessInfo.processInfo.setValue(newArguments, forKey: "arguments")
    
}

---EXTRA---

And just some thoughts:

Regarding

Firebase.Analytics.setAnalyticsCollectionEnabled(true)

If we inspect the method:

So it's kind of POINTLESS...

edited Aug 11 '20 at 16:16

answered Aug 11 '20 at 13:45

Reimond Hill

4,278
40
52

On latest firebase version (SPM) i'm not able to log in debug mode using the ProcessInfo.processInfo programmatically. Is it working for you? In order to back it working, I have to set the -FIRDebugEnabled in Xcode settings. – arcangel06 Aug 14 '23 at 08:22

score 8 · Answer 6 · edited Jun 21 '17 at 10:41

8

I also have the same problems.

1 check your Cocopods' s Firebase version.

use pod update Firebase
List item
make sure that is the latest

2 open debug mode

In the Arguments Passed On Launch part
add - FIRDebugEnabled.

edited Jun 21 '17 at 10:41

Aamir

16,329
10
59
65

answered Jun 21 '17 at 10:34

胡童心

201
2
4

1

I getting some very quirky and unstable results. The debug stream works, and suddenly it stops showing events, – Yaron Levi Jul 23 '17 at 01:00
1

The events were recorded once I updated Firebase by updating pods. So it worked for me. – Keerthi Polepalle Dec 06 '18 at 10:06

score 7 · Answer 7 · answered Oct 08 '19 at 09:10

7

I made it possible by writing the following:

func application(_ application: UIApplication, didFinishLaunchingWithOptions, ...) {
    // some other initialization

    FirebaseApp.configure()
    Firebase.Analytics.setAnalyticsCollectionEnabled(true)
}

answered Oct 08 '19 at 09:10

mr5

3,438
3
40
57

1

this actually helped. Thank you – Filip Luchianenco Jul 15 '20 at 03:58
2

I was skeptical based on comments that it is enabled by default + I had confirmed it was enabled in the plist. But yeah it did not work until I added this line. – Henry Mueller Mar 27 '21 at 23:43
still relevant? I'm using `FirebaseAnalytics` and it also comment that the `setAnalyticsCollectionEnabled` sets to true by default – genericUser Nov 02 '21 at 14:56

score 1 · Answer 8 · answered Nov 20 '18 at 14:17

Check if you have an ad blocker enabled while visiting the Firebase website.

I had uBlock origin enabled and it would block every page (Dashboard, Events, StreamView, DebugView...) and they'd all be blank.

Everything worked as expected as soon as I whitelisted it.

score 1 · Answer 9 · answered Sep 27 '22 at 08:53

Had this issue a few days ago, after trying every solution I found on the internet and none of them working, these are the steps I used to finally enabled DebugView to find my device:

Close the app on the device you’re working on
Go to the Firebase console and sign out of your account
Sign back in again, go to the console and select the project you’re working on.

Again, not sure if this made a difference however do NOT click on DebugView item under the “Project shortcuts” list. Instead, click on the “Analytics” drop-down and select DebugView from there.

It may be possible that this process updates the data stream used in the DebugView page - after following these steps I noticed events which had been missed initially were now showing up - almost as if the event was sent/received properly however the DebugView wasn’t showing the correct data stream.

Bonus tip:

Had issues with this again today, and after signing out/in to Firebase the DebugView still wasn't finding my device. What fixed it was, on my device, move the app into the background i.e. swipe up from the bottom to go to the home screen...

When you re-open the app into the foreground, the DebugView should now start displaying events. I imagine this works because the action of moving the app into the background I believe triggers any saved events on the device to be sent to Firebase, essentially flushing the queue.

score 0 · Answer 10 · answered Dec 11 '19 at 13:58

I recently had an issue where the Xcode console said everything was fine, and all was being logged and sent, and I had the "-FIRDebugEnabled" and I tried all other suggestions in this thread, but nothing worked. Nothing was being sent to Firebase's DebugView.

Looking through my git-history, I determined the issue occurred due to a pod update, and the solution to my issue was another pod update.

I don't know which pod had failed, but I suspect either Moya, Alamofire or FirebaseAnalytics... after this, I'm strongly considering locking my pod-versions.

score 0 · Answer 11 · answered Feb 26 '21 at 16:11

I had the same configuration as jaywant-khedkar, but no events or devices were showing up in the Firebase Debug View.

Found out that my pi-hole on my network was eating all the events. So if if you have any kind of ad blocker on your network, disable it and try again.

Happy debugging!

score 0 · Answer 12 · answered Dec 11 '21 at 01:31

If you've done everything that the Firebase documentation states, then it could be that you have the wrong "Debug Device" selected in Firebase Analytics' "Debug View". After changing the debug device in the top left, all my analytics events from before were displayed! So it wasn't that my events weren't being sent to Firebase, I was just seeing the wrong view. Image attached.

Firebase iOS Debug Console not logging anything

12 Answers12

Linked