Skip to main content

Trouble creating an Apple Push Notification Certificate

Today we were updating our Apple push notification certificate as it was due to expire (why do they only last a year). We've done this many times before and know the process well; but for some reason today after deploying the updated certificate every call to create the PushSharp instance returned the following error:

The specified network password is not correct

We went through the standard process of repeating the creation / deployment of the certificate, then double / triple checking and then repeating the creation process again but nothing improved the situation - the same error message was returned all the time. We tried different passwords / double checked eveything in the Apple developer portal. We cleared the historic and new entries in the KeyChain, tried new .cer certificates / private keys, nothing resolved the issue.

As we'd exhausted every option we could think of, we just tried the process on another machine.....just to see......it worked first time! At the current time we think the issue was caused by a particular machine. Now that we're able to send push notifications again we will have to investigate it further. We did have "show password" ticked when exporting to the P12 file, I've noticed when that is ticked that the password strength indicator no longer works, I wonder if there's an issue around that? If we get to the bottom of the issue then I'll post an update.

Comments

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…

Unit Testing Workflow Code Activities - Part 1

When I first started looking into Windows Workflow one of the first things that I liked about it was how it separated responsibilities. The workflow was responsible for handling the procedural logic with all it's conditional statements, etc. Whilst individual code activities could be written to handle the business logic processing; created in small easily re-usable components. To try and realise my original perception this series of blog posts will cover the unit testing of bespoke code activities; broken down into: Part One: Unit testing a code activity with a (generic) cast return type (this post)Part Two: Unit testing a code activity that assigns it's (multiple) output to "OutArguments" (Not yet written)So to make a start consider the following really basic code activity; it expects an InArgument<string> of "Input" and returns a string containing the processed output; in this case a reverse copy of the value held in "Input".namespace Ex…