Roger roger, thanks!
I can see how you might get into this situation with manual signing
Precisely, yep :/ Once upon a time the automatic signing (and associated certificate/profile resolution) wasn't playing nicely with our build machines for enterprise apps so we switched to manual. Will allocate some time soon to explore deeper. As always, your insights are appreciated!
texas_dev
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
San Antonio, TX
Post
Replies
Boosts
Views
Activity
Appreciate the quick turn around! That seems like a different thing though (granted, the end result may be the same?). I asked about a wildcard (provisioning) profile and what you outlined is for a wildcard app. My situation is about a wildcard distribution profile being used with (multiple) explicit app ids.
Is your response valid for all situations involving either wildcard profiles and/or wildcard app ids?
@eskimo: are entitlements like Hotspot and Access WiFi Information also disallowed with wildcard profiles?
Similar issue doing a debug build around Network framework on beta 3
swift-nio-transport-services/Sources/NIOTransportServices/NIOTSBootstraps.swift:15:5: Failed to build module 'Network'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.5 (swiftlang-1300.0.24.14 clang-1300.0.25.10)', while this compiler is 'Apple Swift version 5.5 (swiftlang-1300.0.24.13 clang-1300.0.25.10)'). Please select a toolchain which matches the SDK.