Build Errors for Remote Deployment to iOS Device

[Chris]

I'm loving the VS integration.  It's amazing.  I have to be able to deploy the app to a physical device to use some hardware specific features.

I start a new project using the default Kendo UI Mobile default template.  I have an iOS Ad Hoc Provision Distribution Provisioning profile and certificate setup.

When I attempt to build to the Cloud with iOS with Provision, I keep getting the following errors: 

Maybe I've got some things crossed up between the certificates, the provisioning profiles and the type of distribution.

I've removed some of the details from the build output in case it was not appropriate to put in this post.  I can add in all details if necessary.

Building package: [C:\dev\icenium\pharmacy-spanish-app\pharmacy-spanish-app\obj\Debug\pharmacy-spanish-app.zip]
Sending build request for project pharmacy-spanish-app with parameters ProjectTypeGuids={070BCB52-5A75-4F8C-A973-144AF0EAFCC9}
AppIdentifier=com.handsonspanish.pharmacyspanish
ProjectName=pharmacy-spanish-app
ProjectGuid=41c78b7e-6cb5-4dfe-b0be-298e3529e81b
Platform=iOS
MobileProvisionIdentifier={REMOVED_BY_ME_FOR_THIS_POST}
iOSCodesigningIdentity=iPhone Distribution Hands On Spanish; Inc ({REMOVED_BY_ME_FOR_THIS_POST})
Configuration=Debug
IsRunnable=true
FrameworkVersion=3.0.0
CorePlugins=org.apache.cordova.core.device;org.apache.cordova.core.AudioHandler;org.apache.cordova.core.battery-status;org.apache.cordova.core.camera;org.apache.cordova.core.console;org.apache.cordova.core.contacts;org.apache.cordova.core.device;org.apache.cordova.core.device-motion;org.apache.cordova.core.device-orientation;org.apache.cordova.core.dialogs;org.apache.cordova.core.file;org.apache.cordova.core.file-transfer;org.apache.cordova.core.geolocation;org.apache.cordova.core.globalization;org.apache.cordova.core.inappbrowser;org.apache.cordova.core.media-capture;org.apache.cordova.core.network-information;org.apache.cordova.core.splashscreen;org.apache.cordova.core.vibration
AndroidPermissions=android.permission.CAMERA;android.permission.VIBRATE;android.permission.ACCESS_COARSE_LOCATION;android.permission.ACCESS_FINE_LOCATION;android.permission.ACCESS_LOCATION_EXTRA_COMMANDS;android.permission.READ_PHONE_STATE;android.permission.INTERNET;android.permission.RECEIVE_SMS;android.permission.RECORD_AUDIO;android.permission.MODIFY_AUDIO_SETTINGS;android.permission.READ_CONTACTS;android.permission.WRITE_CONTACTS;android.permission.WRITE_EXTERNAL_STORAGE;android.permission.ACCESS_NETWORK_STATE;android.permission.ACCOUNT_MANAGER;android.permission.GET_ACCOUNTS;android.permission.MANAGE_ACCOUNTS;android.permission.BROADCAST_STICKY
DeviceOrientations=Portrait;Landscape
iOSStatusBarStyle=Default
AndroidHardwareAcceleration=false
LiveSyncToken=.
C:\Users\Chris\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\bxfq0f5g.pkw\Targets\Build.targets(98,3): error : Server build failed. Server output: Project "pharmacy-spanish-app.proj" (default targets):
Error: Value cannot be null.
Parameter name: certEntry
Done building project "pharmacy-spanish-app.proj" -- FAILED.
.
Done building project "pharmacy-spanish-app.iceproj" -- FAILED.

Build FAILED.

 

[Steve]

Hi Chris,

Thank you for the kind words - much appreciated. Unfortunately this is a bug in the Icenium extension for Visual Studio (still in Beta after all). As you can see from the build output, the variable iOSCodesigningIdentity=iPhone Distribution Hands On Spanish; Inc contains the name of your certificate, however it is not correct, as your actual name is with comma ',' and not with semicolon ';'.

I've logged this problem in our bug tracking database and we would fix it for the upcoming version of Icenium scheduled for mid November.

Unfortunately the only workaround we can suggest for now is to "migrate" your project to our cloud and use Mist/Graphite to build it. Basically you would have to copy your local folders/files from VS and add them to a Mist/Graphite project.

Please excuse us for the temporary inconvenience. Your Telerik points have been updated as token of gratitude for bringing this problem to our attention.

Regards,
Steve
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.

[Chris]

Hi Steve,  

Thanks so much for the reply and being responsive in this forum.  I have utmost confidence in the team at Telerik that you will certainly deliver a solid release product for the Visual Studio integration.  

I was able to do a remote deployment using Graphite using the same same Ad Hoc certificate so fortunately that is working with this particular certificate.

In the mean time, I'll cut over to Graphite.  I'm thinking I may be able to do a cross style of development where I can use a combination of Graphite and Visual Studio by working on my code through a remote Git repository.

When I need to push to a real device, I can bring up Graphite and do the Connected Device deployment but still work in Visual studio and test against the simulator.

The reason I have to do a lot of on-device testing is that we make have use of Audio and Video files and I believe the only real way to test these capabilites and functionality out is to do so on the device.  I've followed some of the Icenium samples for playing audio file as a quick starting point for my proof-of-concept.

Looking forward to the next release.

Thanks again,

Chris

[Steve]

Hello Chris,

A single git repository would not do out of the box. You cannot use the same repository for Graphite and the VS extension as they use different project files i.e. a project created in the VS extension would not be recognized as valid Graphite/Mist project and vice versa. This means you would have to manually create a project file for Graphite, which is a tedious task that a user should not know about and of course is not documented.

Regards,
Steve
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.