Open noahsawyer921 opened 1 month ago
I replicated the issue on Unity 2022.3.37f1
, exploring currently to see if I can determine the root cause.
I've tried probably a dozen different variations of similar code and I continue to reproduce the issue, I will genuinely be shocked if this is a result of user error. There may be some incompatability or something at play, but I think the code is solid.
New Issue Checklist
Issue Description
An ArgumentException and many other similar exceptions are occuring whenever building a Unity build with Parse onto a WebGL release. This exception occurs as soon as the project is run in the browser, as well as whenever I attempt to use any Parse methods, such as ParseClient.Instance.LogInAsync(string username, string password) in the browser.
Example Exception:
When exceptions are set to display the full exception and stack trace in the build settings, I also get this as the first exception, but in any attempts after that (for instance, in the Update loop), I instead get a NullReferenceException.
ArgumentException:
NullReferenceException:
Full example code:
Has anyone else encountered this issue before? Is there any workarounds, or is Unity web deployment not supported?
Steps to reproduce
Actual Outcome
When loading in files that use code from ParseInfrastructure, it causes an ArgumentException on startup. From then on, any uses of the code cause a NullReferenceException. The errors and stack traces are seen above.
Expected Outcome
The code should simply log in the user.
Environment
Unity 2022.3.31f1
Server
3.0.2
MacOS Sonoma 14.4.1
Local
Database
MongoDB
n/a
Local
Client
3.0.2
Logs