Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.6f1
Issue ID
1067192
Regression
No
Analytics CustomEvents lose ordering in a way that breaks funnels when multiple events are called in the same frame
Steps to reproduce the issue:
1. Open user's attached project
2. Open Services window and link the project to a selected organisation
3. Enable Analytics
4. Open SampleScene and enter Playmode
5. Press button Funnel 1, 2 or 3 and inspect Validator in Services window
Expected result: custom events appear in the same order they were called (funnel 4 and funnel 5 display the wanted behaviour)
Actual result: custom events appear in a random order in Validator
Reproducible with: 2017.4.9f1, 2018.1.9f1, 2018.2.3f1, 2018.3.0a8
Workaround: wait a frame between each CustomEvent call
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment