Apple has introduced the Wireless Insights Service Predictions capability in iOS 26. After prior alignment with Apple engineers, we are working to integrate this capability into the Douyin App, and intend to provide a TestFlight build for Apple engineers to validate and debug the integration. We have encountered a blocking issue with entitlement configuration: We use our Apple Developer Enterprise Program account to build and submit TestFlight builds. When we manually create and configure provisioning profiles via the Apple Developer Portal, the required entitlement key com.apple.developer.wireless-insights.service-predictions is not available for selection or inclusion in the profile's Entitlements. This completely blocks us from enabling, using, and validating the Wireless Insights Service Predictions capability. For comparison, when we use our Apple Developer Program individual account, the entitlement com.apple.developer.wireless-insights.service-predictions is fully available. It is automatically included in provisioning profiles generated for local debugging, and can also be manually added to custom provisioning profiles via the Apple Developer Portal without issues. We request assistance to resolve this entitlement access discrepancy for our Enterprise Program account, so that we can complete the integration and provide the TestFlight build for validation as planned.
AFAICT this capability is not available for Enterprise distribution. I ran through the process described in Finding a Capability’s Distribution Restrictions and, for my Enterprise test team, it only shows Development and Ad Hoc under Provisioning Support. I recommend that you run through this process yourself, just to be sure.
Given that, there’s nothing we can do about this here on the forums. Normally I recommend that folks escalate entitlement issues via Apple > Developer > Contact Us > Development and Technical > Entitlements. However, in this case there might be a better path. You wrote:
After prior alignment with Apple engineers
Does that mean you’ve been discussing this issue with someone at Apple already? If so, that’s proabbly your best path forward.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"