You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current appbundler does not set isDebugging = true at line 114 in main.m until the second iteration of running the code, when launchCount > 0.
The problem with this is that there are several ways that app launch could fail during the first iteration (when launchCount = 0), but with isDebugging still false, little or no information is written out via NSLog.
One could just alter line 114 to ignore the value of launchCount, but in that case, a successful launch when debugging is enabled will print out two copies of the all the diagnostics.
Any ideas on a better way to handle this?
The text was updated successfully, but these errors were encountered:
Original report by me.
The current appbundler does not set isDebugging = true at line 114 in main.m until the second iteration of running the code, when launchCount > 0.
The problem with this is that there are several ways that app launch could fail during the first iteration (when launchCount = 0), but with isDebugging still false, little or no information is written out via NSLog.
One could just alter line 114 to ignore the value of launchCount, but in that case, a successful launch when debugging is enabled will print out two copies of the all the diagnostics.
Any ideas on a better way to handle this?
The text was updated successfully, but these errors were encountered: