Check that the argument to EJSON.parse is a string.

[awwx]

Some Android browser versions of JSON.parse can crash when passed null
(https://code.google.com/p/android/issues/detail?id=11973), so it's
better not to pass on a non-string argument to JSON.parse.

Thanks to @raix for raising the issue in #1401.

[raix]

Thanks Andrew!

[glasser]

That blocks String objects. Which admittedly are annoying and other places in Meteor don't consider them as strings (eg check). So maybe that's fine.

[glasser]

Thanks, merged.

[awwx]

Yeah, does anybody use String objects for anything? You could have a policy to convert String objects to string primitives in entry points to the public API... but that would make sense only if anyone actually wanted to use String objects.

[raix]

Well I kinda did use String guys, thanks, but nice to know that Meteor likes strings as primitive better than objects.

[awwx]

nice to know that Meteor likes strings as primitive better than objects

I don't know if calling Meteor API functions with String objects would in fact cause any problems, but there's no unit test coverage for it at least.