-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Add a StrictMode noteSlowCall for SSL init #8339
Conversation
@swankjesse if we don't do #8248, then we should be noisy when it's used on main. |
@swankjesse any objections to this? |
.penaltyListener({ it.run() }) { | ||
violations.add(it) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm. When was this added? I would assume after our minSdk, so it should really have an @SdkSuppress(minSdk=something)
on the class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll check, also why it's not failing if so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahhh, just the tests. And not running because of mannodermaus/android-junit5#225 and a minSdk 26 requirement for tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah. JUnit 5 continues to prove that it's the wrong choice for any project.
Apps may want to defer SSL init off the main thread, so warn if they have enabled Strict Mode.
Alternative or precursor to #8248, should land which ever way that goes.