Classes
The Android provider build processor ensures that any custom configuration that the user creates is
correctly passed on to the provider implementation at runtime.
Custom configuration instances that are stored in EditorBuildSettings are not copied to the target build
because they are considered unreferenced assets. To get them to the runtime, they must
be serialized to the built app and deserialized at runtime. Previously, this as a manual process
that required the implementor to manually serialize to some location that can then be read from to deserialize
at runtime. With the new PlayerSettings Preloaded Assets API, you can now add your asset to the preloaded
list and have it be instantiated at app launch.
Note: Preloaded assets are only notified with Awake, so anything you want or need to do with the
asset after launch needs to be handled in the Android provider build process.
For more information about the APIs used, see:
This is custom Editor for Android Provider Settings.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.