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

I have the same issue. I’m trying to submit a Build with a fix but since the subscription shows waiting for review, the new build is being rejected for App completeness as the subscription is not linked with the new version. i’m in a catch22 situation.

Do you have access to the latest source code for your project? That's really the key question here. I agree with the poster above — when I've done development in the past, the app owner has their own Apple Developer account and invites the developer to join their team. The app should be submitted to App Review through the owner's account, not the developer's. A couple of other things to be aware of: if the annual Developer Program fee isn't paid and the account lapses, Apple will remove your app from the store. Once that happens, it's much harder to recover, so time is important here. Also, check any contracts you have with the development company. You may have rights to the source code, which could matter if the company's assets are being handled through bankruptcy proceedings. Without the source code, you'd essentially be starting over from scratch. The good news is that if you do manage to get the code and set up your own developer account, Apple has an app transfer process in App Store Connect that can mo

Hi there, You're on the right track in wanting to retain full control of your Apple Developer account while working with a freelancer. The best and most modern approach is to add the developer to your App Store Connect account with the Developer role. This allows them to access the necessary signing tools in Xcode without needing your personal credentials, and they can submit the app directly through App Store Connect. Sharing certificates and private keys (as your developer suggests) can be risky and is no longer considered best practice. Instead, you should handle signing through Xcode and App Store Connect, which ensures both security and control. This way, your app remains under your Apple Developer account, and you retain long-term control while allowing the developer to work without compromising security. Hope that helps! -Dean Reyburn, reyburnengineering.com iOS/MacOS app developer

Is this an iOS, MacOS, WatchOS app? And do you have the source code in an Xcode project? Has the app already been published and this is an update? Or is this first time. Happy to help -Dean Reyburn, Reyburn Engineering, Inc. reyburnengineering.com

I have this issue too. Payment made on iPhone. I can see the subscription in my subs. However, when I log in, the status says pending and there's a link to continue through to payment. I've emailed Apple Support but so far no reply (Case: 102821244027) @Apple Developer Support

My team has also encountered a similar situation. In mid-January, the build (App ID: 1552207792) was submitted for review and remained in the Waiting for Review state for several days. The status did not change, so we tried resubmitting the build, but that did not help. A week later, we resubmitted it again after accepting the new Terms of Use in App Store Connect, thinking that might have been the cause of the delay. Currently, the app has been stuck in Waiting for Review since February 4th — it has now been 10 days. A request for an expedited review and contacting Apple have not had any impact on the situation.

@DTS Engineer It's February 2026 and when I try to upload an app to App Store Connect with url-content-filter I get the following error: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'url-filter-provider'

@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