1. Airship Support
  2. Community
  3. iOS SDK

Trying to use the Airship iOS Service Extension and Azure pipeline builds fail ...

Avatar
chris.simeone

I'm posting this question here in case other Airship users have had the same experience and may be able to offer a solution. I also created a detailed post on StackOverflow including the .yml files related to this issue.

Using Azure pipelines, I am trying to build/deploy a Xamarin iOS app that depends on the Airship iOS service extension that enables rich push notifications.

To build an iOS app and a related iOS service extension requires multiple provisioning profiles, one for the app and another for the service extension.

The Azure pipeline build fails, complaining that the service extension provisioning profile does not match the apps provisioning profile.

Does anyone have any ideas how I can get an Azure pipeline build to succeed when using the the Airship iOS service extension and  multiple provisioning profiles?

In case it matters, the app is developed using Visual Studio for Mac. I am able to build and run it on a physical test device.

This is the error message we get in the Azure pipeline console. This message is output when trying to build the service extension.

Info.plist : error : Project bundle identifier 'com.xxxxx.ServiceExtension' does not match specified provisioning profile 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx'

(The xxxxx's represent our apps provisioning profile uuid)

Reviewing the Azure code, it looks like there is no way to tell the build step to use multiple provisioning profiles. If I am understanding the code correctly, it looks like the Xamarin iOS Azure pipeline task can only handle a single provProfileUuid value.

Didn't find what you were looking for?

New post

Comments

3 comments

Sort by Date Votes
  • Avatar
    Stéphane Sardes

    Hello Chris,

    Thank you for reaching out.
    It seems that Microsoft's docs state this isn't possible to use multiple provisioning profiles.
    https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/xcode?view=azure-devops#using-multiple-provisioning-profiles

    We would recommend to ask their Support for feedback ?
    Maybe there's another way around this.

    The only other way we could recommend is to build the targets separately.

    It seems that some other people are running into the same thing if you Google this issue.
    https://stackoverflow.com/questions/53225705/azure-devops-pipelines-xcode-project-with-multiple-provisioning-profiles-fails

    Best Regards,

    Comment actions Permalink
    0
  • Avatar
    arhum65 edaerd

    When integrating Airship’s iOS Service Extension with an Azure DevOps pipeline, build failures can arise due to various factors, such as misconfigured build settings or missing dependencies. One common issue is that the Airship SDK, particularly for service extensions aaad, may require additional setup or permissions that aren’t automatically included in the pipeline’s build environment. To resolve this, ensure that the necessary CocoaPods or Swift Package Manager dependencies are correctly installed and updated in your pipeline's YAML configuration. It may also be necessary to add steps for provisioning profiles and code signing to ensure the service extension is properly recognized by the build system.

    Comment actions Permalink
    0
  • Avatar
    Ghulam Hyder

    Using Azure pipelines, I am trying to build/deploy a Xamarin iOS app that depends on the Airship iOS service extension that enables rich push notifications.To build an iOS app Gareth Parkin  and a related iOS service extension requires multiple provisioning profiles, one for the app and another for the service extension. The Azure pipeline build fails, complaining that the service extension provisioning profile does not match the apps provisioning profile.

    Comment actions Permalink
    0

Please sign in to leave a comment.