ubuntu-calculator-app crashes when run from the unity8 session as a deb

[Jean-Baptiste Lallement]

Zesty Desktop
Unity8 as a deb
ubuntu-calculator-app 2.3.1 (37) 479kB devmode
ubuntu-app-platform 1 (34)

Test Case
Install the calculator app, app-platform, connect the plugs, reboot, login into unity8 (as a deb)
Launch the calculator app

Actual result
It fails with
Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
[QPA] UbuntuClientIntegration: connection to Mir server failed.

Mir returned: "Failed to connect: not accepted by server"
[2017-02-24 10:51:42.321945] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in mir_connection_release): /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"

Expected Result
It works

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170216.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Fri Feb 24 10:52:36 2017
InstallationDate: Installed on 2014-07-23 (946 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: unity8
UpgradeStatus: Upgraded to zesty on 2016-11-15 (100 days ago)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1662145, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.