DebugView not working in TestFlight Builds

[LoadingIndicator]

Description

We are experiencing the problem, that the Firebase DebugView seems to no longer be working from TestFlight builds.

The documentation states to put the -FIRDebugEnabled param into the scheme launch arguments. This works, but only when starting the app from Xcode. However, for our analytics department and QA, they work with TestFlight builds provided by the devs.

Up until now we were using the following code as a workaround to mutate the launch arguments:

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

As of this thread, this is discouraged and does no longer work: https://forums.developer.apple.com/forums/thread/767584

Therefore we were looking for other solutions and fount two similar issues:

• https://github.com/firebase/firebase-ios-sdk/issues/13598
• https://github.com/firebase/firebase-ios-sdk/issues/13640

The workaround in these issues is supposed to be this:

UserDefaults.standard.set(true, forKey: "/google/firebase/debug_mode")
UserDefaults.standard.set(true, forKey: "/google/measurement/debug_mode")

Turns out, it still did not work for us.

We tested different devices in our company and iOS 16 and 18 did not work under any circumstances. However for two colleagues with iOS 17 devices, the DebugView is still working.

Can you please help on this issue, since this effectively blocks our analytics team from approving tracking in new features.

Reproducing the issue

No response

Firebase SDK Version

11.5

Xcode Version

16.1

Installation Method

Swift Package Manager

Firebase Product(s)

Analytics, Crashlytics, Messaging

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[rizafran]

Hi @LoadingIndicator, your issue seems intended and related to #13260. DebugView needs to run the app in a development environment with the -FIRDebugEnabled flag enabled in Xcode.

[cavaalex]

It used to work with this workaround. It was possible to set those arguments in the AppDelegate.mm (react-native with Objective C).

    NSMutableArray *newArguments =
        [NSMutableArray arrayWithArray:[[NSProcessInfo processInfo] arguments]];
    [newArguments addObject:@"-FIRDebugEnabled"];
    [newArguments addObject:@"-FIRAnalyticsDebugEnabled"];
    [[NSProcessInfo processInfo] setValue:[newArguments copy]
                                   forKey:@"arguments"];

Now it is not working anymore. Not sure it is the workaround or iOS 18 or something else that stopped working.

[LoadingIndicator]

We tried this UserDefaults workaround again:

UserDefaults.standard.set(true, forKey: "/google/firebase/debug_mode")
UserDefaults.standard.set(true, forKey: "/google/measurement/debug_mode")

This workaround is actually working, but only on the second launch of the app, so apparently the first launch does not recognize the UserDefaults value.

[skywalkerlw]

Got the same issue: working on simulator but not on the TestFlight version. and @LoadingIndicator solution works.

[huynamboz]

@LoadingIndicator Save my life, respect!

[yusera-ansari]

This does work! Thanks! @LoadingIndicator