Search Issue Tracker
Fixed
Votes
0
Found in
2019.3.0b1
Issue ID
1178832
Regression
No
[UDP] Errors do not appear in console or editor log
[UDP] Errors do not appear in console or editor log
When using the UDP package to configure a project and it's IAP products, errors are often shown to the user in regards to validation/pushing/pulling. Currently these errors are shown to the user embedded in the inspector and are not pushed to the console or editor log, inconsistent with other error handling throughout Unity.
Steps to reproduce:
- In Unity 2019.3, create a new project and install the Universal Distribution Portal (UDP) package (alternatively download the attached project)
- Menu: Window > Universal Distribution Portal > Settings
-Inspector (UDP Settings) > Register the project with Unity Cloud Services if the UDP Settings Inspector pane indicates it is not already
- In the Network Adapter settings in the host Operating System, disable all network adapters
- Inspector (UDP Settings) > Pull
- Observe an error is reported to the user
- Observe the same error is not reported to the console
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TransformAccessArray.Add behaves differently when the argument is null and the argument is an int
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
Resolution Note:
Could not reproduce using UDP package 1.3.0, closing as fixed