Remove namespace from ContentPacketExtension #498
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit sets the namespace of the ContentPacketExtension to null. This was causing issues when parsing the jingle session-initiate message with stanza.io. The namespace was being set on content elements inside a group which stanza.io would fail to parse.
According the group XEP there usually isn't a namespace on the content elements (https://xmpp.org/extensions/xep-0338.html), and the namespace currently doesn't show up on the content elements inside the jingle element in the session-initiate message. (smack 4.2 might be doing something smart to remove a child element's namespace if it is the same as the parent).
More details in this discussion: https://community.jitsi.org/t/jitsi-dev-custom-client-fails-to-parse-jingle-session-initiate-with-new-jicofo/13992
Ran tests in jitsi-videobridge, jicofo, jicoco, and jigasi and all passed.