UnitySimpleFileBrowser
UnitySimpleFileBrowser copied to clipboard
yasirkula
Non-fatal error on startup
Description of the bug
I'm getting an error whenever I click play:
Trying to add MoreOptionsButton (UnityEngine.UI.Image) for graphic rebuild while we are already inside a graphic rebuild loop. This is not supported. UnityEngine.UI.Graphic:set_color (UnityEngine.Color) SimpleFileBrowser.UISkin:ApplyTo (UnityEngine.UI.Text,UnityEngine.Color) (at Assets/Plugins/SimpleFileBrowser/Scripts/UISkin.cs:556) SimpleFileBrowser.UISkin:ApplyTo (UnityEngine.UI.InputField) (at Assets/Plugins/SimpleFileBrowser/Scripts/UISkin.cs:568) SimpleFileBrowser.FileBrowser:RefreshSkin () (at Assets/Plugins/SimpleFileBrowser/Scripts/FileBrowser.cs:1290) SimpleFileBrowser.FileBrowser:Awake () (at Assets/Plugins/SimpleFileBrowser/Scripts/FileBrowser.cs:880)
It has not caused a problem so far but I figured I would bring it up just in case.
Reproduction steps
Add package and Meta XR Core and All-in-One SDKs Take SimpleFileBrowserCanvas prefab and add to hierarchy Change canvas render mode to "world space" Right click gameobject > Interaction SDK > Add Ray Interation to Canvas
Platform specs
- Unity version: 2022.3.7f1
- Platform: Android
- Device: Windows 10 laptop
- How did you download the plugin: Package Manager
Thank you for bringing this to my attention. This plugin unfortunately suffers from this strange issue (related bug report that I've submitted) and I think the only definitive solution would be to rebuild the SimpleFileBrowserCanvas prefab from scratch. I'm thinking of updating the plugin from Unity 5.6 to 2019 LTS in the future and I might rebuild the prefab during that time. We shall see.
In the newest releases, Unity version is upgraded and TextMesh Pro is integrated. Those might have fixed the issue automagically. If the issue persists, please reopen the Issue.
Also, related Issue: https://github.com/yasirkula/UnitySimpleFileBrowser/issues/94
I do not have permissions to reopen this issue, but after updating to the most recent version (1.7.4) I still have the exact same error appear on startup.