Log in

[giladani]

Which problem was fixed?
adding session.publishers = {} prevents from the policer to be destroyed, but I still can't publish to a new session. When I publish nothing seems to happen (incl. a stream created notification).

Gil.

[giladani]

FYI - I also noticed that your example doesn't work well if you pressed start publishing and then stop.

http://www.tokbox.com/opentok/api/tools ... blish.html

[jtsai]

Ah, I thought you were still referring to the unable to disconnect bug.

I just tested out the publishing to a second session, and it does seem like there is a bug with this though. I have filed a ticket for this.

John

[giladani]

Hi John,

any news about this bug? Can you say if this will be resolved in this week's release?


Thanks,
Gil.

[giladani]

???

[jtsai]

This will not be fixed in this week's release. It got pushed back to next week because of other priorities.

John

[giladani]

Any chance that it will be solved next week? This is a problematic bug for me...

Gil.

[giladani]

Hi John,

due to the pending bug, we're currently restarting the publisher multiple time. We think that there is a chrome related bug (we know that it mostly related to chrome) where if you restart the publisher again and again (maybe also because it's started when the screen is off) then the camera goes blank. Happened for at least 4-5 people out of ~10 that we tested on parallel.

Gil.