Bugger The Banks, We’re Going to Mars

With the successful landing of the Curiosity Rover on Mars, the inevitable comparison with what has been poured into the banking system was made in the letters page of the Irish Times (and more amazingly without painful puns):

As a final aside, we could have had an Irish space programme and a viable base on the moon with all the associated financial, technological and investment spin-offs for the money that, with a stroke of a minister’s pen, we “invested” in bailing out our failed banks. – Yours, etc,

For a change though, someone has crunched the numbers. WorldbyStorm from The Cedar Lounge Revolution did some quick calculations on what’s been wasted on propping up failed banks (of course you could also add the money that’s flowing into Quinn Insurance because of the black hole there but that only covers 2/3rds of a Curiosity):

The EU bailout saw €17.5 bn from the NPRF. Then there’s the ‘loans’ from the EU, IMF and UK/Denmark and Sweden which would account for €67.5 bn. Sundry other costs can be thrown in. So let’s say we had €100bn.

That’s a lot of cash, but Apple currently has approximately that in cash reserves right now so it’s not an impossible number to reach especially over a number of years. So what would that get you?

There’s a web page here which suggests that it cost $100bn at 1994 rates to land on the Moon. But even accounting for inflation we wouldn’t necessarily have to follow all the steps. For a start we could double up some of the missions and vehicles, perhaps by moving straight to a three or more person capsule and eschewing either the Mercury or Gemini elements of the program.

Now here’s the thing – Space X has developed, built and launched a reusable spacecraft that docked with the ISS for the paltry sum of $800 million. There’s already plans to build a version that could make it Mars. So a chunk of the R&D has already been done. Their model of providing resupply services to the ISS would also be a source of income to plough back into the program.

That’s all well and good but what about some of the other practicalities of skilled people to actually run such a program or even build anything. As it happens, Ireland is already involved with the ESA since 1975 and has an active (if small) space industry. It’d need to scale up, but that would provide jobs and direct investment that paying off bondholders doesn’t.

Just think. For less than the bailout, we could gather up all the architects of our current situation and bundle them into a capsule bound for Mars and still come out ahead. We could even televise their one way trip for even more money.  All in the name of science.

An Irish Space Programme and an Irish Base on the Moon! What do you mean we spent the money already?

A version of this post also appeared on Broadsheet.ie.

Invalid IPA: The keychain-access-group in the embedded.mobileprovision and your binary don’t match.

Update 2014/03/12 This QuickLook plugin is a great way of seeing what’s in your provisioning profiles: https://github.com/chockenberry/Provisioning

Provisioning profiles are such a delight.  My latest battle with them involved getting the following error:

Invalid IPA: The keychain-access-group in the embedded.mobileprovision and your binary don’t match.

The background to the situation is this: I’d run out of devices on one of my Apple Developer accounts and needed to send out a test build to some new users. So I created a new bundle ID in my second account, re-archived the app and sent it out. The tester came back with the above error when they tried to install it.

The problem lay with me not changing the application-identifier and keychain-access-groups values in the entitlements file. These need to match the new provisioning profile values. The values for these changed because I was using a different developer account. keychain-access-groups is easy to miss as it’s folded when you open the entitlements file in Xcode.

You’ll find the correct values in your provisioning profile as well as in the App IDs page in the iOS Provisioning Portal.

Another error I hit with my second dev account was:

entitlement ‘application-identifier’ has value not permitted by a provisioning profile

This turns out to be caused by signing the IPA with the wrong identity. How did I manage that you ask? I was using my auto archive script and I’d forgotten to change what identity to use when signing. There’s two hours sleep I’ll never get back.

Previously: The executable was signed with invalid entitlements. (0xE8008016)