Apparently due to the following code which was introduced in 2.4.1.
TypeError: Cannot convert undefined or null to object
I’ve raise my concerns about this line, when it was still in code review, as it is clearly unneeded and breaks backward compatible. Apparently to be ignored…
See point 1 at
Your comments were definitely not ignored, however in this case the original behaviour was actually a bug, and it was always intended that the SDK would be returning those kinds of errors as part of the error callbacks. As this was a bug, we decided to include the fix in the 2.4 series, the bug that came from this was a bit of a parallel issue that came up and has since been fixed (to be merged into 2.4.2).