We are using the Unity's Caching product to store the downloadable content on the local disk to minimize downloading times. This has been working fine on Unity2, but when we migrated to Unity3, the Caching.Authorize function started to return false (meaning we can't use the caching feature).
Are signatures not compatible between Unity versions? Do we have to request another signature for our domain to solve this?
Thanks for your reply. We look into the UnityWebPlayer logs and then we found this error:
You need to run this player from the http://bla.something.com:81 domain to be authorized to use the caching API. (currently running from http://bla.something.com )
Then we changed the domain from "http://bla.something.com:81/" to "bla.something.com".
Now the Caching.Authorize function just returns false without logging any errors.
It seems that there is a difference between how Unity2 and Unity3 detects the domain from where its running the player.
We will need a new signature for the modified domain to fit this new behavior.
answered Oct 19 '10 at 04:00 PM
It should not have changed. When Caching.Authorize fails, you should get an error message on your console. What does it say?
answered Oct 19 '10 at 08:49 AM
jonas echterhoff ♦♦