Facebook Stream Target from REST API does not accept newlines for description

[Muhammad_Nuzaihan_Ka]

Creating a Facebook PushPublish stream target with a newline in the description will cause Stream Targets to crash, requiring me to delete and add back the application.

So this is definitely a bug for Wowza. Another thing is to check whether the Facebook stream target is able to accept emojis in the description as well so this might be another bug.

Log:

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000} span.s1 {font-variant-ligatures: no-common-ligatures} span.s2 {font-variant-ligatures: no-common-ligatures; color: #ca3323} span.Apple-tab-span {white-space:pre}

ERRORservercomment2019-09-2402:33:11-----2193.42--------class com.wowza.wms.rest.vhosts.applications.pushpublish.PushPublishStreamsAppConfig.get : java.lang.NullPointerException|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebookUtil.validateEntry(PushPublishFacebookUtil.java:186)|at com.wowza.wms.pushpublish.module.ModulePushPublish.isEntryValid(ModulePushPublish.java:1971)|at com.wowza.wms.pushpublish.manager.PushPublishManager.getEntries(PushPublishManager.java:113)|at com.wowza.wms.rest.vhosts.applications.pushpublish.PushPublishStreamsAppConfig.loadObject(Unknown Source)|at com.wowza.wms.rest.ConfigBase.get(Unknown Source)|

[Muhammad_Nuzaihan_Ka]

I have confirmed. No problems with emoji for description. Only new lines in the description will crash stream targets.

[Amara_Graham]

Thank you for posting the log info. How are you including the new line in the description? Have you tried escaping it?

\\n

[Muhammad_Nuzaihan_Ka]

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px ‘Helvetica Neue’}

It doesn’t make sense since the data for the facebook description should be sanitized at wowza’s end and not my web app’s end.

Here is how the data looks like:

“Test\n\nTest\n\nTest”

I think this should be filed as a bug and character escapes should be deemed as a workaround.

My use case is that I have users who enters the description on a mobile app and send it to my web app and then my web apps sends that data to the Wowza Stream Engine rest api to create the facebook stream target using the description it got from my web app.

I could sanitize it myself but the point is that it is a bug on wowza’s rest api stream target.

Escaping the newline breaks \n will cause the facebook description to appear with “\n” character visible and this is not what i want.

[Muhammad_Nuzaihan_Ka]

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px ‘Helvetica Neue’}

It doesn’t make sense since the data for the facebook description should be my web app’s end instead of wowza’s end.

Here is how the data looks like:

Test\n\nTest\n\nTest

I think this should be filed as a bug and character escapes should be deemed as a workaround.

My use case is that I have users who enters the description on a mobile app with newlines and send it to my web app and then my web apps sends that data to the Wowza Stream Engine rest api to create the facebook stream target using the description it got from my web app.

Also Facebook Post descriptions allow newlines as well, the limiting part is Wowza actually accepting strings with newlines.

i had sanitized the facebook target description as per your recommendation and the Facebook Post for the live video is no longer formats correctly as it was intended to.

The point is that it is a bug on wowza’s rest api stream target and i feel this should be fixed.

[Rose_Power-Wowza_Com]

The engineers would like to ask you for a Wowza support ticket. Tech support does not provide official support through the forums and would like to view your files and run some tests to debug. They can only do this through a support ticket.

Would you kindly submit one @Muhammad Nuzaihan Kamal Luddin? We’d like to address your concerns and thank you for posting about it here. Community feedback from our developers is extremely critical to us.

https://www.wowza.com/support/open-ticket

[Muhammad_Nuzaihan_Ka]

I can’t. I don’t have a support contract.

But this bug is serious enough because it crashes stream targets if the facebook target description has newlines when being created via the REST Api.

With the workaround this is not a complete solution. The stream target should not have crashed in the first place and even in WSE frontned the description should be a text field instead because facebook description supports multiline text.

[Jeff_Reese]

Hello Muhammed, we’ve moved this to a ticket from here in order to track it as a potential bug. Please check your email for a response from us and follow-up when you can.

[Rose_Power-Wowza_Com]

Please check your email @Muhammad Nuzaihan Kamal Luddin when you can. Know that sometimes the Wowza emails go to spam. We can only try to fix this if we can replicate the issue you’re reporting. Thanks so much!