Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.2.0f1
Issue ID
952696
Regression
Yes
Pubnub notifications are not being processed for Collab state updates.
The push notifications from PubNub seem to not get processed in most cases. If the two users restart their clients and have a fresh start with no network issues, the PubNub notifications go through. However, once you introduce a poor network condition (unplug the network for a second or introduce high enough of latency to reach 500ms or more), even after the poor network condition is removed, most pubnub push notifications are missed until it resorts to the 4 minute poll to get the update.
Restart of the editor, refresh the history window, or waiting up to 4 minutes gets around the issue for that one publish/update, but then the bug process begins anew. In-progress notifications are also affected but are on a different timer which might be longer than the 4 minute timer.
Issue seems to only affect the 2017.2 branch and later.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment