Median.co HomeDeveloper PortalCreate New App
Questions
Online TermsPrivacy Policy

Questions

Ask a Question
Back to all

Found a specific issue in Median-generated iOS source causing provisioning errors

10 hours ago by Noric Gebhardt

Hi Median Support,

I’m having an iOS provisioning/signing issue with my app Garanto (com.garanto-app.garanto).

I have already regenerated the Apple signing assets and verified the Apple Developer configuration. The following provisioning profiles are newly generated:

  • Garanto_Main
  • Garanto_OneSignal
  • Garanto_ShareExtension

The required capabilities and App Groups are enabled, and the Median Apple/App Store connection is valid.

The Median cloud build currently fails during GatherProvisioningInputs with provisioning errors for all three targets: the Main App, Share Extension and OneSignal Notification Service Extension.

I downloaded the iOS source generated by Median and found two things that appear relevant:

  1. Incorrect OneSignal App Group entitlements

The Main App provisioning profile contains both:

group.com.garanto-app.garanto

group.com.garanto-app.garanto.onesignal

However, the generated Main App entitlement file only contains:

group.com.garanto-app.garanto

The OneSignal Extension provisioning profile contains:

group.com.garanto-app.garanto.onesignal

but the generated OneSignal Extension entitlement file contains:

group.com.garanto-app.garanto

This seems inconsistent with Median’s OneSignal configuration requirements.

  1. Missing provisioning profile mappings

In the generated project.pbxproj, I cannot find PROVISIONING_PROFILE_SPECIFIER or PROVISIONING_PROFILE assignments for the Main App, Share Extension, or OneSignal Extension.

The cloud build switches to manual signing (CODE_SIGN_STYLE=Manual) and uses the distribution certificate, but there do not appear to be target-specific provisioning profile assignments.

Since all three targets fail during GatherProvisioningInputs, this seems like a possible issue with how the Median cloud build generates or assigns signing assets.

Could you please investigate this on the Median side?

Ideally, I would like to continue using the normal Median cloud-build workflow rather than building the source manually in Xcode.

Could you please check:

  1. Whether the OneSignal App Group entitlements are being generated incorrectly.
  2. Whether the correct provisioning profile is being assigned to each target during the cloud build.
  3. Whether Median may be using a cached/incorrect signing configuration.
  4. Whether this can be fixed in Median App Studio so future builds can be generated normally.

I can provide the generated iOS source archive or the relevant project files privately if needed.

Thanks!