Confirmed. This is particularly weird considering a few things:
1) The content interface to the ubuntu-app-platform is automatically connected, even if the consumer is --dangerous. I assume this is a slot-side assertion.
2) The configure hook specifically runs _after_ services in the snap, which means confinement (including the content interface since it's automatically connected) should be put together by then.
Confirmed. This is particularly weird considering a few things:
1) The content interface to the ubuntu-app-platform is automatically connected, even if the consumer is --dangerous. I assume this is a slot-side assertion.
2) The configure hook specifically runs _after_ services in the snap, which means confinement (including the content interface since it's automatically connected) should be put together by then.