Passbook integration preventing app transfer


We need to transfer our iOS app from one organization to another. Apple has said we cannot do that because of Passbook integration. We are not directly using the Passbook API, so we suspect it is a third party SDK that our app depends. When we searched on this issue, we found this post:

So we suspect it might be the Urban Airship iOS SDK that is the cause of this problem since it is one of the third party SDKs our app uses.

Apple has said that only v1.0 and v1.0.1 of our app used Passbook integration. Our app is now at v2.0.8 and uses Urban Airship's v9.0.2 SDK.

Is this a known problem with earlier versions of UA's iOS SDK? If so, at what point was the SDK updated so that this is no longer a problem?

I searched through the release notes of the SDK and found only one mention of Passbook from 2015.

Thank you for any information. This has turned into a real problem because Apple is now saying that we have to do a binary transfer for the app, which is basically starting by rebuilding the app under a new organization.

Didn't find what you were looking for?

New post


1 comment

  • Hi,

    As you can see in the comments to the older post you've linked to, this is a known issue. A fix was submitted in version 7.2.

    But if you've had a former SDK at any version in your app in the past, having updated to the new one will not solve this problem as far as Apple is concerned.

    Unfortunately, you'll need to contact apple developer relations and explain your case. Explain the fact that your current app version corrects for this, and that you have not used Passbook even in previous versions (and that you have no way to ensure all users updated your app), and ask Apple to take that into consideration.

    Sorry for the trouble.

    Jay M.
    Urban Airship Technical Support

    Comment actions Permalink

Please sign in to leave a comment.