This question is locked. New answers and comments are not allowed.
Brandon Peterson
Top achievements
Rank 2
Rank 2
Brandon Peterson
asked on 06 Feb 2014, 09:24 PM
After exporting projects from Graphite and re-creating them as Visual Studio Icenium (AppBuilder) projects, my nightly "Build [project name] in Cloud" livesync short URLs for Android and itms manifests for iOS seem to expire overnight. I am able to install the apps from the generated QR code and short URLs immediately after building in cloud from Visual Studio but my QA team reports the links do not work in the morning. I then build again and see that the livesync URLs are identical but the content (apk or plist+ipa) are available again. Is there a sliding expiration from time of build in cloud or daily cutoff for livesync URL content availability?
3 Answers, 1 is accepted
0
Hello Brandon,
The scenario you describe is not officially supported by the AppBuilder companion app, which is meant for developer testing purposes only. Should you need to give your app to testers, we recommend building your app with ad-hoc provision and distributing the .ipa directly.
The LiveSync url does not expire in the AppBuilder Windows and In-browser client as the built is kept in our cloud and there is no designated sync like with the Visual Studio extension. The VS sync would trigger deletion of the project from our cloud and its reupload, so the built .ipa is basically deleted.
Regards,
Steve
Telerik
The scenario you describe is not officially supported by the AppBuilder companion app, which is meant for developer testing purposes only. Should you need to give your app to testers, we recommend building your app with ad-hoc provision and distributing the .ipa directly.
The LiveSync url does not expire in the AppBuilder Windows and In-browser client as the built is kept in our cloud and there is no designated sync like with the Visual Studio extension. The VS sync would trigger deletion of the project from our cloud and its reupload, so the built .ipa is basically deleted.
Regards,
Steve
Telerik
Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
0
Joe
Top achievements
Rank 2
Rank 2
answered on 20 Feb 2014, 08:24 PM
Steve, thank you for the explanation. I should have specified that I do not use the companion app, only the Visual Studio Extension "Build in Cloud" option with an Ad Hoc provisioning profile for wireless Ad Hoc distribution via links like so:
iOS: itms-services://?action=download-manifest&url=http%3A%2F%2Flivesync.ly%2F1hOSEXQ
Droid: http://livesync.ly/1b3A3IR
From your insights and my testing just now it appears that timed expiration is not the case at all but rather building an apk will cause an ipa installation attempt to result in the iOS dialog: "Unable to Download Application '[App.Name]' could not be downloaded at this time" when clicking the itms-services link and building an ipa will cause an apk install to result in the download to fail when clicking the livesync.ly link and the Android browser is launched.
Are there any plans to allow one platform's build to not wipe out the other or maybe batch build both platforms in AppBuilder when chosing "Build [App.Name] in Cloud" for wireless Ad Hoc distribution of both platforms simultaneously via those nifty links and QR codes?
iOS: itms-services://?action=download-manifest&url=http%3A%2F%2Flivesync.ly%2F1hOSEXQ
Droid: http://livesync.ly/1b3A3IR
From your insights and my testing just now it appears that timed expiration is not the case at all but rather building an apk will cause an ipa installation attempt to result in the iOS dialog: "Unable to Download Application '[App.Name]' could not be downloaded at this time" when clicking the itms-services link and building an ipa will cause an apk install to result in the download to fail when clicking the livesync.ly link and the Android browser is launched.
Are there any plans to allow one platform's build to not wipe out the other or maybe batch build both platforms in AppBuilder when chosing "Build [App.Name] in Cloud" for wireless Ad Hoc distribution of both platforms simultaneously via those nifty links and QR codes?
0
Hello Joe,
Thanks for the reply.
Indeed, currently AppBuilder VS extension uses our cloud service to build your application, but builds are occasionally removed and you can not rely on the links for longer time.
We are still considering the best usage of the cloud service for our extension and how it should behave. This is why we will be glad to hear your point of view and get deeper knowledge of our customers' needs.
So far our AppBuilder windows and in-browsers clients provide you with the ability to build for both OS (iOS and Android) without wiping out each other. Once your project is created via some of the clients it is stored in our cloud side by side with the build it outputs.
Regards,
Zdravko
Telerik
Thanks for the reply.
Indeed, currently AppBuilder VS extension uses our cloud service to build your application, but builds are occasionally removed and you can not rely on the links for longer time.
We are still considering the best usage of the cloud service for our extension and how it should behave. This is why we will be glad to hear your point of view and get deeper knowledge of our customers' needs.
So far our AppBuilder windows and in-browsers clients provide you with the ability to build for both OS (iOS and Android) without wiping out each other. Once your project is created via some of the clients it is stored in our cloud side by side with the build it outputs.
Regards,
Zdravko
Telerik
Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)