Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

@DTS Engineer It's mid February and I am trying to upload an app (just to TestFlight) with a url-content-filter. I am getting the same error: Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'url-filter-provider' for key 'com.apple.developer.networking.networkextension' Is this just still not available? How do we proceed with using this entitlement?

It's mid February and I am trying to upload an app (just to TestFlight) with a url-content-filter. I am getting the same error: Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'url-filter-provider' for key 'com.apple.developer.networking.networkextension' Is this just still not available? How do we proceed with using this entitlement?

If you've enabled MusicKit in the Apple Developer Portal but your build fails with Provisioning profile doesn't include the entitlement, here is the fix: Do NOT add the entitlement to app.json. Apple now treats MusicKit as a Runtime Service, meaning it is checked on Apple's servers when the app runs, not stamped into the .mobileprovision file at build time.

Hello, We are using iBeacon region monitoring with CLLocationManager (startMonitoring(for:)) to detect entry into a specific beacon region. Setup: Background Modes enabled: location bluetooth-central “Always” location permission granted. iBeacon UUID configured correctly. Beacon hardware verified (advertising confirmed). Expected Behavior: When the device enters the beacon region, the app should wake (or relaunch) in the background and trigger BLE communication. Observed Behavior: If the app is sent to the background normally → region enter event works correctly. However, if the user force-quits (swipe up kills) the app, then: The app does not relaunch when entering the beacon region. didEnterRegion is not triggered. BLE communication does not start. Questions: Is it officially supported for iBeacon region monitoring to relaunch an app after the user force-quits it? Is this behavior intentionally blocked by iOS as a user privacy/power decision? Are there any supported mechanisms to resume beacon moni

I completely understand why it feels strange, but keeping the SiriKit extension point for those domain-specific intents is the right thing to do. As to whether or not that functionality is coming over to App Intents at some point, I'm unable to discuss anything pertaining to the future direction of these frameworks. — Ed Ford,  DTS Engineer

It sounds like you tested it on iOS. I understand that some developers refresh Transaction.currentEntitlements when the iOS app switches to the foreground. Yes, I do handle Transaction.unfinished and it is not related to my issue. Have you seen this post by @saxmanbob? He had a similar issue to mine, but he resolved it due to some “Objective-C machinery”. I don’t use Objective-C in my app, although it may exist within some Swift packages. Please try the following and let me know if you get the same result. Download the CotEditor Xcode project, copy and paste the InAppPurchaseManager code somewhere appropriate and launch it in applicationDidFinishLaunching(_:). Locate the CotEditor.storekit file and change the Subscription Renewal Rate to Any Renewal Every 10 Seconds or Any Renewal Every 2 Seconds. Run the app and observe the console. You will see that it does not behave as expected. You could also try this in a fresh AppKit Xcode project. You don’t need to build the UI and you will

Thanks Ed for the reply! I guess the reason for the question is that it seems a little strange to have some intents as AppIntents and others in the (older) SiriKit / IntentExtension framework, as opposed to having them all as AppIntents. Ideally I'd like to get rid of the IntentsExtension if possible, but it sounds like that's something that's intentional from Apple's perspective. Is that true, or are there plans to bring them all over as AppIntents at some point in the future?

Could the issue with not being able to attach IAP purchases to the build be caused by the IAP purchases already being in review before I submit the app for review? This is my first app and I wonder if submitting the IAP for review before attaching and submitting the app for review is the issue.

Thanks for this, I would recommend to get the error message from the build report itself. Follow the steps below to collect the full build report in Xcode: Choose View > Navigators > Reports. Select the report associated with your app’s build in the navigator. Using the filter bar at the top of the build report, select the filter buttons for All and All Messages. Click Export in the filter bar to save the detailed build report. Please share the error message here if you want. Additional information about collecting a build report is available in Xcode’s documentation: https://help.apple.com/xcode/mac/current/index.html?localePath=en.lproj#/dev1c8beb00d Hope this helps Albert Pascual
  Worldwide Developer Relations.

Thank you for providing the code and screenshots. Additionally, I would like to inquire about your filed bug report, instead of submitting two Swift files, would it be possible to upload a focused and simple project to the bug report that demonstrates the issue? That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Also you can share a link for that project in the forums so developers can see the issue and provide workarounds. Albert Pascual
  Worldwide Developer Relations.