Deployment Provisioning Profile AppID Wildcard Problem

2 posts, 0 answers
  1. Richardsonke
    Richardsonke avatar
    93 posts
    Member since:
    Jul 2007

    Posted 15 Jan 2013 Link to this post

    My project app identifier is com.MyCompany.MyProject.  If I generate an Apple in-house deployment provisioning profile with an AppID of com.MyCompany.*, the publish dialog of Icenium says "Project Application Identifier does not match any of the AppStore provisions Application Identifiers."  If I leave profile in Icenium and create a deployment provisioning profile with the AppID of com.MyCompany.MyProject, the publish dialog says "There are more than one AppStore provisions matching.  Package will be signed with the first one matching."  If I remove the profile with the wildcard, the publish dialog then says "Your application validators are OK!"

    This is a two-part problem.  First of all, is there any reason why we can't publish with a profile using a wildcard.  If we can't then it shouldn't incorrectly state that there are multiple matching profiles once I add one that doesn't use a wildcard.

    Thanks for looking into this.
  2. Yavor Georgiev
    Admin
    Yavor Georgiev avatar
    982 posts

    Posted 16 Jan 2013 Link to this post

    Hello Keith,

     Unfortunately we didn't have the resources to properly address all code-signing scenarios in the Publisher when it was introduced and so we went after the most common scenario - a single App Store provision with a concrete App ID. This means that bugs and corner cases are possible, for which we are sorry.

     However, we're in the process of revamping the code-signing workflow and we're taking into account precisely scenarios such as yours, after gathering feedback. You can expect the new Publish wizard in a future release.

    Greetings,
    Yavor Georgiev
    the Telerik team

    Share feedback and vote for features on our Feedback Portal.
    Want some Kendo UI online training - head over to Pluralsight.
Back to Top