Highlights​

• Async initialization flow: YsoNetwork.initialize() is now asynchronous, and mediations can call it repeatedly. Use YsoNetwork.initializationStatus() plus the new YNEnumInitializationStatus enum to poll for Initialized, Initializing, or Error.
• Request IDs everywhere: All ad loads and shows now expect a requestId. It should be unique per ad (the bid request ID is ideal) and reused between the load/show pair. Reusing the same requestId for concurrent loads is unsupported and leads to undefined behavior.
• Documented initialization sample: The usage guide now shows a mediation-safe initialization block that waits on the status enum before marking the adapter ready.
• Stricter public surface: ProGuard now only exposes the classes that mediation partners need: YsoNetwork, YNLog, YNEnumActionError, and YNEnumInitializationStatus. Everything else remains internal.
• Changelog + docs: Installation, usage, and the platform changelog have all been updated to reflect these behaviors so that partners don’t have to reverse engineer the new flow.

Let us know if you need the adapter templates or sample code snippets in another format—we’re happy to share.