Repository navigation
v1.2.1
Diagnostic logging is now compiled out of release builds.
Changed
- All package logging goes through a new
AdLoghelper.InfoandWarncarry[Conditional]attributes forUNITY_EDITORandDEVELOPMENT_BUILD, so a release build removes the call entirely, arguments included. That matters because most messages interpolate a string: a runtime flag would still pay to build every message before discarding it, whereas this costs nothing at all. ErrorandExceptionare deliberately not conditional. They fire only when something is genuinely broken, and a shipping game that fails silently is far harder to diagnose than one that leaves a line in the device log.- Much deeper tracing on the consent path, all of it development-build only:
- which consent path was chosen (local form or InMobi CMP)
- the ATT plan, which component owns the prompt, and the settled ATT status before init
- the geo lookup endpoint and how long it took
- prefab load and instantiation
- what the form was seeded with, and whether it is answerable and readable
- EventSystem creation and which input backend, plus recovery after a scene load
- which button was tapped and the resulting decision, and the guard being released
To see any of it on device, tick Development Build in Build Settings.
Install
https://github.com/HaseebDev/LevelPlay-Mediation-Package.git#v1.2.1
Or import the attached .unitypackage.