The browser based Icenium client is called Mist and it currently has a limitation that it does not show provisions that do not comply with the requirements for build, namely:
- your App ID does not match the bundle ID of the provision. In your case you have defined explicit IDs, so matching is absolutely necessary. Check the following help article: Configure the Application Identifier for Your App.
- you have not imported the certificate
Should you comply with both, the provision would show in Mist. I have verified this with your provisions on our end.
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.