Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have been behind this for long time. And Managed to fix this. I would like to explain the problem here and the easiest workaround. </p> <p><strong><em>ERROR HERE IS...</em></strong></p> <blockquote> <p>The error is the result of a device manufacturer or ROM creator using an older maps library with a new version of Android. Typically, this is isolated to obscure tablets, but it could theoretically appear in other situations. ( <a href="https://stackoverflow.com/a/13042056/1441326">explained here</a> )</p> </blockquote> <p><code>android.security.MessageDigest</code> was removed in Honeycomb and later. This is the thing which cause issues.</p> <p><strong>EASY FIX from YOUR CODE:</strong></p> <p>Just create MessageDigest.java in src directory under package android\security and put below code inside.</p> <p>This workaround actually works and is the most non-intrusive I have found. I have not seen any side effects with this yet.</p> <pre><code>package android.security; import java.security.NoSuchAlgorithmException; public class MessageDigest { private java.security.MessageDigest instance; public MessageDigest() {} private MessageDigest(java.security.MessageDigest instance) { this.instance = instance; } public static MessageDigest getInstance(String algorithm) throws NoSuchAlgorithmException { if (algorithm == null) return null; try { if (algorithm.equals("SHA-1")) return (MessageDigest) Class.forName("android.security.Sha1MessageDigest").newInstance(); else if (algorithm.equals("MD5")) return (MessageDigest) Class.forName("android.security.Md5MessageDigest").newInstance(); } catch (Exception e) {} return new MessageDigest(java.security.MessageDigest.getInstance(algorithm)); } public void update(byte[] input) { instance.update(input); } public byte[] digest() { return instance.digest(); } public byte[] digest(byte[] input) { return instance.digest(input); } } </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload