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
[TIMOB-25219] Android: FileNotFoundExceptions should not be inside the Titanium log #9391
Conversation
…e the Titanium log
We log the stacktrace in many places (148x). Maybe we want to hide the 3rd parameter in the default logging-state and show it when using trace-logs? How do others solve this? I am very open and happy to discuss it! |
@sgtcoolguy I think this one is save to merge. Other places can be looked into in further use-cases. |
FR Passed. Studio Ver: 5.1.0.201805150850 |
@sgtcoolguy , the unit tests are still failing with:
Can you please take a look. Thanks !! |
@lokeshchdhry Addressed in #10060, but I don't have merge permissions either, so once it turns green, you can merge it. |
Generated by 🚫 dangerJS |
JIRA: https://jira.appcelerator.org/browse/TIMOB-25219
Description:
This removes passing the exception object to the
Log.e
call, which should avoid printing the full exception stack trace for the exact use case Hans mentioned - when unable to open a file or URL that doesn't exist.There's some caveats here: