iOS Cannot install applications because the certificate is not valid

By -

When you upgrade to iOS 7.1 and try to distribute an App via your own means, say for Enterprise distribution, you may get the following error when you try and download the plist.

'Cannot install applications because the certificate for <hostname> is not valid'

 It turns out that App have changed the rules with 7.1, the plist file must be behind a certificate.

So instead of

http://www.myexample.com/manifest.plist

it will need to be

https://www.myexample.com/manifest.plist

This is a real pain if you're a small outfit as you'll have to purchase a SLL certificate.

One option is to use Azure as you'll get a default SSL that you can use.

Remember if you're rolling your own distribution you will need to make sure your web server, i.e. IIS, understands the mime types .ipa and .plist

Comments

Post a Comment

Popular posts from this blog

Switching Xamarin Accounts on Mac and Windows

By -
I had a situation where one of our development Macs already had a Xamarin Indie license installed for iOS development.  We then needed to install a client's Business account onto the Mac but unfortunately Xamarin Studio got confused between the two accounts (it showed the new account name but it still said 'INDIE', when it should have said 'Business'). To do a clean switch over you need to do the following:  First make sure you've logged out of your first account.  And login with your new account.  In Xamarin studio you can do this by selecting Xamarin Studio -> Account from the menu bar. Then delete the entire folder listed below.  Windows %programdata%\MonoTouch\License\ %programdata%\Mono for Android\License\ You may need to startup Visual Studio as an Administrator. Mac ~/Library/MonoTouch ~/Library/MonoAndroid When you start up Xamarin Studio, and build the an app it should reset and pick up the new license and
Read more

Xamarin Forms - InitializeComponent does not exist in the current context

By -
Image
I was presented with this error whilst developing with Xamarin Forms For me it was simply down to copy and paste :-O.  I'd created a new Xaml Page, which fully qualified was MyNameSpace.MyPage. I then copied in some Xaml which had a different name in the Xaml x:Class attribute (x:Class="NotMyNameSpace.OrPage"). I then tried to compile with our fixing the x:Class attribute and got the 'InitializeComponent does not exist' error. Once I changed the Xaml to match my actual classname (x:Class="MyNameSpace.MyPage") I was back on track and the error went away. Hope this helps. For more information have a look at  forums.xamarin.com The other reason is that you may have created a Shared Xamarin Forms Project rather than a Xamarin Forms Portable project. From Craig Dunn at Xamarin (taken from  Xamarin Forms Forum ) You cannot use Xaml with the Shared Project template with iOS apps (in Xamarin Studio). It's a weird combination to rem
Read more

How to setup Azure Service Bus Relay to use with ACS

By -
In August 2014 Microsoft decided to remove Microsoft Azure Active Directory Access Control (also known as Access Control Service or ACS) from the default Azure Portal setup when creating a new Service Bus Namespace.   Shared Access Signature (SAS) is now default. Service Bus authentication through ACS is managed through a companion “-sb” ACS namespace and to create this we now need to do it from the Azure Power Shell command line (thanks Microsoft!) To do this: Download the PowerShell console https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/#Install Open up the Console and type Add-AzureAccount  and then type in the email address and password associated with your account (Work or Microsoft) Once authenticated you need to create the Service Bus Namespace so it's good to go for ACS. To do this you use the  New-AzureSBNamespace command Parameter Set: Default New-AzureSBNamespace [-Name] <String> [[-Location] <String&g
Read more