I believe this is an attempt to enforce some of the permissions changes made around Marshmallow, I believe, where apps now request many permissions at time of use, and not at install. The compatibility layers are a bit 'ugly'.
An interesting side effect is that if you sideload an app that is in this state, Google Play will actually offer to keep it updated, even though it wouldn't allow installation initially.
That was a relatively major change, but there have been enough other changes since then, too, that they're trying to force developers to adopt – some of them "just" cause the hassle of adapting to the new APIs, some of them unfortunately definitively break some power user use cases without a suitable replacement.