Hello Joseph,

what you notice is actually a bug, due to slight incompatibilities on how URLs are encoded and decoded by iOS and Java. Unfortunately, the specifications for URL encoding leave room for interpretation and, as frequently happens, different systems interpret it in different ways. Thanks for reporting, it will be surely solved in an upcoming release.

In the meanwhile, a simple workaround would be to pre-escape the "+" sign with some character combination, and then unescape it in the metadata adapter (notifyUser and notifyNewSession methods).
Hope this helps. Best regards,

Gianluca