Troubleshooting

When integrating PATCH some problems may arise. In fact, it interacts with external services like web servers, so sometimes additional operations are needed.

How to ask for help

When you contact me to ask for help, please remember to attach:

• Unity Player logs (you can find them here)
• PATCH logs (you can find them in Logs/ folder)
• The debug report that PATCH can generate in both Admin Tool and Launcher

Also, try to describe the problem and how you triggered it! Just a simple "it does not work, why?" won't help me to solve your issue quickly!

Debug Mode

The Launcher has a Debug Mode that should help with debugging. The Debug Mode can be enabled in two ways:

• building your Launcher in Debug
• set the UpdatingContext.Settings.DebugMode flag on true
• use the settings overrider to override the DebugMode flag

Debug Mode enables the logging of the Debug level logs, but not only! It also allows you to see additional information about logs like the file from where the log has been sent, the method name, the line number.

Files cannot be downloaded

You uploaded your files, but the web server seems to not serve them correctly.

Forbidden mime types

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.

Web cache

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.

Wrong files location

PATCH requires you to set a remote root folder where searching for needed files. If files are not uploaded to the correct location, PATCH cannot find them.

Context: PATCH cannot locate files and/or returns an error like "Our servers are not responding"

Solution: double check your remote folders structure. In your remote folder you must have the same structure you have in PATCHWorkspace folder. Example: your remote folder is http://localhost/patch? PATCH expects to find builds in http://localhost/patch/Builds/, patches in http://localhost/patch/Patches/ and updater in http://localhost/patch/Updater/.