This sometimes happens to me. I am surprised that I have not seen it raised in the forum before.
Usually the problem is some severe and immediate error - like trying to use an uninitialised asset in Activity_Resume. The app crashes very early and there is nothing in the log page. Then, when I find and fix the bug, on the next run the missing log data appears - it was obviously produced at the right time in the device but something stopped it getting sent until the bug was cleared. There might be several log runs "stored up".
I have always assumed, without any real idea of how the B4A Bridge works, that the crash broke the bridge before it had time to transfer the log data.