-
-
Notifications
You must be signed in to change notification settings - Fork 6
Troubleshooting
When integrating PATCH some problems may arise. In fact, it interacts with external services like web servers, so sometimes additional operations are needed.
You uploaded your files, but the web server seems to not serve them correctly.
By default, web servers do not serve all mime types in production. PATCH tries to use standard data formats for web, but Unity builds can contain a lot of forbidden mime types and the server can block their delivery.
Context: the server returns HTTP errors like 4xx (403, mostly) or 500. You can verify it by navigating to that file's URL with your browser.
Solution: reach your web server's configuration and allow the serving of all mime types. If you are unsure about how to do it, just google the process to do it for your specific web server.
In some cases, your web server may maintain a file cache (in particular if you are using a CDN) to optimize traffic and resource usage.
Context: you modify existing remote files and when you access them through the browser you still see the old version.
Solution: refreshing the cache should solve the problem.