No error on with those on my Nexus 5. :(
I do notice that both of those references include links, which means they have " in their string contents which gets escaped. I had a problem in the iOS app with this breaking because the bridge was sending the JSON blob into a URL and backslashes (\") were misconverted into forward-slashes (/") which caused JSON deserialization to fail on the native side of the bridge.
In the Android case we're using the JS prompt() system for the bridge which *should* not be doing weird things to the text... but clearly something is being weird in some cases!
Try putting an encodeURIComponent() right at the bridge level and de-encoding on the other side and see if that helps.
var ret = window.prompt( JSON.stringify( messagePack) );
->
var ret = window.prompt( encodeURIComponent( JSON.stringify( messagePack) ) );
^ and then the appropriate decoding on the native side.
-- brion