SecureRandom: change link for deprecation of Crypto provider
In the error log, use a link to a post in the Android Developers
blog instead of the current link to stackoverflow.
Also, add a message when an instance from the Crypto provider
is created for apps targeted at SDK <= 23, so that when seeing
log messages of applications that failed we can tell quickly
whether the workaround applied or not.
(cherry picked from commit c045ff585114fe376618186b18291ffe1df91769)
1 file changed