-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DebugView not working in TestFlight Builds #14182
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @LoadingIndicator, your issue seems intended and related to #13260. DebugView needs to run the app in a development environment with the |
It used to work with this workaround. It was possible to set those arguments in the
Now it is not working anymore. Not sure it is the workaround or iOS 18 or something else that stopped working. |
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. |
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:
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:
The workaround in these issues is supposed to be this:
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
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: