"Selected users" distribution: how the app update process works?

2 posts, 0 answers
  1. Andrea
    Andrea avatar
    4 posts
    Member since:
    Dec 2013

    Posted 21 Jan 2014 Link to this post

    Hi,
    I need an information about the Icenium apps update process. I think (sorry but I'm new to the apps world) that, when I release a new version of an application distributed through the Apple Store/Google Play, the update process on the client's device will "override" the old app with the new one, am I correct?
    But what happens if I update an app released with the "Selected users" distribution type? Do I have to tell the users to uninstall the previous version before installing the new one or the update process is able to "understand" that the application already exists on the device? And also: is it possible to "automatically" update these applications without telling the users "hi, we have updated this app, here is the new file, get it" (like the LiveSync used in Debug mode)?
    Thanks in advance,

    Andrea
  2. Kaloyan
    Admin
    Kaloyan avatar
    872 posts

    Posted 23 Jan 2014 Link to this post

    Hi Andrea,

    I believe you have went through the Build and Distribute Your App to Selected Users articles (here and here). So straight to your questions:
    1. "I think (sorry but I'm new to the apps world) that, when I release a new version of an application distributed through the Apple Store/Google Play, the update process on the client's device will "override" the old app with the new one, am I correct?"
      • You are absolutely correct on that one!
    2. "But what happens if I update an app released with the "Selected users" distribution type?"
      • We assume that by "Selected users" distribution type" you refer to ad-hoc distribution type, correct? The same rules apply for absolutely every iOS distribution, for more information please refer to their documentation.
      • When the selected users acquire the newer version of the application it should automatically override the previously installed one.
    3. "Do I have to tell the users to uninstall the previous version before installing the new one or the update process is able to "understand" that the application already exists on the device?"
      • For Android applications the apk application ID matches the application ID you have set in the Project Properties for your Icenium project. So as long as the applications (the one distributed only for selected users and the official one published on Google Play) share one Application ID and they are built with the same cryptographic identities, they should update automatically. In other words, the official version should override the previous one.

        iOS uses different bundle identifiers in order to understand if this is an update or a completely different application. So, if you download an update from the Apple Store, it should update the "Selected users" distributed app on your device as long as their bundle identifiers are identical. This is so, because in Icenium apps the Bundle ID matches the application ID you have set in the Project Properties for your project.  
    4. "And also: is it possible to "automatically" update these applications without telling the users "hi, we have updated this app, here is the new file, get it" (like the LiveSync used in Debug mode)?"
      • Silent updates are not allowed by Store vendors and is not something our product controls.

    Please be aware that all of your questions are general info available in the documentation of the respective app store provider and not directly related to our product. What Icenium does for you is offer you an IDE and build services, so you can create and build an app. What is the provision you've used to sign your app or how you provide it to your users or publish to app stores is entirely up to the developer.

    Regards,
    Kaloyan
    Telerik
    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.
Back to Top