I came across this problem too, and I think that's because this library tries to place SafeArea for you by default :(. It's not documented, but there is a wrapInSafearea property which I set to false since I am already taking care of the SafeArea myself.