I asked Nordic the same question - in their case they use CBCentralManagerState.unknown (and perhaps a few others) to display this message.
So it looks like the only workaround to detect an error is to track whether the app gets inactive within some timeout after creating CBCentralManager. If it doesn't, it means that the permission wasn't requested by iOS.
Topic:
App & System Services
SubTopic:
Core OS
Tags: