OnErrorOccurred to surface SDK failures:
Debug.LogError or a crash reporter is fine. Connectivity loss during work the SDK runs on its own - notification polling, event delivery, status refreshes, and a FetchNotifications() that finds no network - is logged at Warning, retried by the SDK, and never fires this event. A device that loses its signal after start-up produces no errors. Only Initialize still reports offline, because the game is waiting on its first status: Disabled when the configuration cannot be fetched, NetworkFailure when the status that follows it cannot.
Compare codes with
==, for example err.Code == AlmediaErrorCode.RateLimited. Errors are non-fatal. The SDK keeps running and may recover on the next status update or fetch.
Do not retry Initialize directly from OnErrorOccurred. Initialize raises its own configuration errors before it returns, so the handler runs inside Initialize. The SDK ignores that retry and logs a Warning. Fix the configuration and retry from a later frame. The same configuration fails the same way.