Search results for

“build disappears”

51,311 results found

Post

Replies

Boosts

Views

Activity

Reply to Crash on App Clip Subtitle Focus
I’m not sure we need to go into that level of detail about how we build the App Clip, since the issue seems to be related to the App Store Connect submission page itself. Every time I access App Store Connect, I can consistently reproduce the issue with the following steps: Open the app submission page Navigate to the App Clip section Click on the Subtitle text field App Store Connect immediately displays the error shown in the screenshot If you think these details you asked is important, i can provide, but this looks like a App Store Connect platform crash.
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much with the post. Can I ask you what’s your “cloud-based device testing environment”? Because Universal Links rely on cryptographic trust between the app and the web server, the re-signing process inherently could breaks this trust? The platform signs the app with their own provisioning profile, which does not contain your com.apple.developer.associated-domains entitlement? Apple's security model intentionally prevents unauthorized third parties from claiming your domain. Therefore, there is no native Apple provisioning flag that tells iOS to ignore AASA validation for re-signed builds. Can you provide more details? However, please understand that Universal Links will only work on physical devices with the entitlement. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
1w
SKProductsRequest returns 0 products — all identifiers reported as invalid (Capacitor hybrid app)
I'm building a hybrid iOS app using Capacitor with a native Swift IAP bridge (StoreKit 1). My SKProductsRequest consistently returns 0 products, and all product identifiers appear in response.invalidProductIdentifiers. Setup: Capacitor app with custom CAPBridgeViewController subclass handling IAP via SKPaymentQueue and WKScriptMessageHandler 5 products configured in App Store Connect (3 consumables, 2 auto-renewable subscriptions), all Ready to Submit Bundle ID matches between Xcode and App Store Connect In-App Purchase capability enabled Paid Apps agreement active Testing on physical iPad Air M3 with Sandbox Tester Products created over 48 hours ago Clean Build Folder performed before each test Product IDs: com.opencompass.basic.monthly com.opencompass.premium.monthly com.opencompass.tokens.50 com.opencompass.tokens.150 com.opencompass.tokens.500 Code snippet: let request = SKProductsRequest(productIdentifiers: Set(productIdentifiers)) request.delegate = self request.start() // Delegate fir
0
0
53
1w
Universal Links and Cloud-testing platforms
Hi Apple Developer Support, We are reaching out to request guidance on a testing constraint we have encountered related to iOS Universal Links and Associated Domains entitlements. As part of aligning with updated recommendations from our authentication provider, we have transitioned our mobile apps to use HTTPS redirect callbacks (Universal Links) instead of custom URI schemes. This works as expected in production and on real physical devices. However, we are encountering a significant issue in our cloud-based device testing environment. When our testing platform re-signs the app to run it on their infrastructure, the re-signing process strips the Associated Domains entitlement from the app bundle. As a result, iOS no longer honors our Universal Links, which breaks the authentication redirect flow — the callback cannot route back into the app after the user authenticates. We have identified a potential workaround that would involve disabling app re-signing in the testing platform, but this requires provisioni
7
0
271
1w
Reply to spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and
Topic: Code Signing SubTopic: Notarization Tags:
1w
pkgbuild on Tahoe fails to build packages if any directory name contains non-ascii characters
pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters. pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26. Example that demonstrates the issue: mkdir -p MyAppData/Taishōgoto echo Testing >> MyAppData/Taishōgoto/Content.txt pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg Error messages: parent directory ./Taishōgoto does not exist pkgbuild: error: Cannot write package to myappdata.pkg. (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.) I have submitted this via Feedback Assistant (FB22312299). I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.
3
0
69
1w
Reply to Attached macro loses generated source file
[quote='819975021, tiandt, /thread/819975, /profile/tiandt'] I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. [/quote] Agreed. I recommend that you file a bug about this. Please post your bug number, just for the record. If you use Xcode to expand the macro, what does it show? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
1w
Reply to FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
If you set up a VM that’s never seen your app before and repeat this test on that VM [1], does it have the same problem. I’ve hunted app extension problems like this in the past, and it was always caused by weird issue on my main work Mac. Specifically, old school app extensions [2] rely PluginKit which relies on Launch Services, and it’s very common for Launch Services to behave weirdly on your main development Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You don’t need to build on the VM. Rather, build on your main Mac and then copy the built app to the VM. [2] Modern app extension are based on ExtensionKit rather than PluginKit, but they also rely on Launch Services.
1w
Title: 45 Days "Waiting for Review" – 3 Expedites Approved, Zero Movement. Backend Glitch?
Hey everyone, I’m completely stuck and hoping someone here (or an Apple rep) can help, because Developer Support is just sending me the exact same template replies at this point. I submitted a standard version update for my app (Hadiyyati - Luxury Gifts) back on February 7th. It has now been over 45 days, and the status is still permanently frozen on Waiting for Review. Here is the loop I am stuck in: I've had an Expedited Review requested and approved 3 separate times. Support gives me a case number, says they contacted the App Review Board, and tells me to wait. Weeks pass, nothing happens, and when I follow up, I get: At this time, your app review is proceeding normally, and there is no further action you need to take. 45 days for a store update is not proceeding normally. I strongly suspect my submission (ID: aeadea76-8fb4-437c-9c04-60171b909f3e) is bugged, corrupted, or locked in a ghost state on the App Store Connect backend. Has anyone dealt with a completely frozen submission like this? Is there a spe
2
0
95
1w
Reply to App review process takes long time
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
1w
2 Apps Stuck in "Waiting for Review" (6 & 23+ Days) — Expedited Review Approved but No Movement (2026)
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
0
0
28
1w
Reply to Tap to Pay entitlement stuck in development for nearly 1.5 months – do I need to resubmit?
Hi @mensrev, @devraj, You'll need to contact the provisioning team where you made your initial request. Please see the post below for more information: Resolving Tap to Pay on iPhone errors when building for App Store, TestFlight, or Enterprise distribution https://developer.apple.com/forums/thread/794192 Cheers, Paris X Pinkney |  WWDR | DTS Engineer
1w
Reply to Crash on App Clip Subtitle Focus
I’m not sure we need to go into that level of detail about how we build the App Clip, since the issue seems to be related to the App Store Connect submission page itself. Every time I access App Store Connect, I can consistently reproduce the issue with the following steps: Open the app submission page Navigate to the App Clip section Click on the Subtitle text field App Store Connect immediately displays the error shown in the screenshot If you think these details you asked is important, i can provide, but this looks like a App Store Connect platform crash.
Replies
Boosts
Views
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much with the post. Can I ask you what’s your “cloud-based device testing environment”? Because Universal Links rely on cryptographic trust between the app and the web server, the re-signing process inherently could breaks this trust? The platform signs the app with their own provisioning profile, which does not contain your com.apple.developer.associated-domains entitlement? Apple's security model intentionally prevents unauthorized third parties from claiming your domain. Therefore, there is no native Apple provisioning flag that tells iOS to ignore AASA validation for re-signed builds. Can you provide more details? However, please understand that Universal Links will only work on physical devices with the entitlement. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
SKProductsRequest returns 0 products — all identifiers reported as invalid (Capacitor hybrid app)
I'm building a hybrid iOS app using Capacitor with a native Swift IAP bridge (StoreKit 1). My SKProductsRequest consistently returns 0 products, and all product identifiers appear in response.invalidProductIdentifiers. Setup: Capacitor app with custom CAPBridgeViewController subclass handling IAP via SKPaymentQueue and WKScriptMessageHandler 5 products configured in App Store Connect (3 consumables, 2 auto-renewable subscriptions), all Ready to Submit Bundle ID matches between Xcode and App Store Connect In-App Purchase capability enabled Paid Apps agreement active Testing on physical iPad Air M3 with Sandbox Tester Products created over 48 hours ago Clean Build Folder performed before each test Product IDs: com.opencompass.basic.monthly com.opencompass.premium.monthly com.opencompass.tokens.50 com.opencompass.tokens.150 com.opencompass.tokens.500 Code snippet: let request = SKProductsRequest(productIdentifiers: Set(productIdentifiers)) request.delegate = self request.start() // Delegate fir
Replies
0
Boosts
0
Views
53
Activity
1w
Universal Links and Cloud-testing platforms
Hi Apple Developer Support, We are reaching out to request guidance on a testing constraint we have encountered related to iOS Universal Links and Associated Domains entitlements. As part of aligning with updated recommendations from our authentication provider, we have transitioned our mobile apps to use HTTPS redirect callbacks (Universal Links) instead of custom URI schemes. This works as expected in production and on real physical devices. However, we are encountering a significant issue in our cloud-based device testing environment. When our testing platform re-signs the app to run it on their infrastructure, the re-signing process strips the Associated Domains entitlement from the app bundle. As a result, iOS no longer honors our Universal Links, which breaks the authentication redirect flow — the callback cannot route back into the app after the user authenticates. We have identified a potential workaround that would involve disabling app re-signing in the testing platform, but this requires provisioni
Replies
7
Boosts
0
Views
271
Activity
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Finally I found the problem. In the entitlements file, I had 2 entries iCloud Container Identifier iCloud Services with an empty array of values. These must have been left over from previous edits. After removing the above entries, building completes without any error. 😉
Replies
Boosts
Views
Activity
1w
Reply to spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
1w
pkgbuild on Tahoe fails to build packages if any directory name contains non-ascii characters
pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters. pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26. Example that demonstrates the issue: mkdir -p MyAppData/Taishōgoto echo Testing >> MyAppData/Taishōgoto/Content.txt pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg Error messages: parent directory ./Taishōgoto does not exist pkgbuild: error: Cannot write package to myappdata.pkg. (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.) I have submitted this via Feedback Assistant (FB22312299). I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.
Replies
3
Boosts
0
Views
69
Activity
1w
Reply to Attached macro loses generated source file
[quote='819975021, tiandt, /thread/819975, /profile/tiandt'] I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. [/quote] Agreed. I recommend that you file a bug about this. Please post your bug number, just for the record. If you use Xcode to expand the macro, what does it show? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
1w
Reply to FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
If you set up a VM that’s never seen your app before and repeat this test on that VM [1], does it have the same problem. I’ve hunted app extension problems like this in the past, and it was always caused by weird issue on my main work Mac. Specifically, old school app extensions [2] rely PluginKit which relies on Launch Services, and it’s very common for Launch Services to behave weirdly on your main development Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You don’t need to build on the VM. Rather, build on your main Mac and then copy the built app to the VM. [2] Modern app extension are based on ExtensionKit rather than PluginKit, but they also rely on Launch Services.
Replies
Boosts
Views
Activity
1w
Title: 45 Days "Waiting for Review" – 3 Expedites Approved, Zero Movement. Backend Glitch?
Hey everyone, I’m completely stuck and hoping someone here (or an Apple rep) can help, because Developer Support is just sending me the exact same template replies at this point. I submitted a standard version update for my app (Hadiyyati - Luxury Gifts) back on February 7th. It has now been over 45 days, and the status is still permanently frozen on Waiting for Review. Here is the loop I am stuck in: I've had an Expedited Review requested and approved 3 separate times. Support gives me a case number, says they contacted the App Review Board, and tells me to wait. Weeks pass, nothing happens, and when I follow up, I get: At this time, your app review is proceeding normally, and there is no further action you need to take. 45 days for a store update is not proceeding normally. I strongly suspect my submission (ID: aeadea76-8fb4-437c-9c04-60171b909f3e) is bugged, corrupted, or locked in a ghost state on the App Store Connect backend. Has anyone dealt with a completely frozen submission like this? Is there a spe
Replies
2
Boosts
0
Views
95
Activity
1w
Reply to App review process takes long time
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
Replies
Boosts
Views
Activity
1w
2 Apps Stuck in "Waiting for Review" (6 & 23+ Days) — Expedited Review Approved but No Movement (2026)
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
Replies
0
Boosts
0
Views
28
Activity
1w
Reply to What steps should I follow to get started with iOS development?
Start with Swift basics then learn Xcode build small apps follow tutorials and practice consistently 🌟📲
Replies
Boosts
Views
Activity
1w
Reply to App Review
Was your app reviewed? I have been reading many posts as I am in a similar position and I wonder if deleting the build and uploading a new one would help? It’s almost like it’s just stuck in the system
Replies
Boosts
Views
Activity
1w
Reply to Tap to Pay entitlement stuck in development for nearly 1.5 months – do I need to resubmit?
Hi @mensrev, @devraj, You'll need to contact the provisioning team where you made your initial request. Please see the post below for more information: Resolving Tap to Pay on iPhone errors when building for App Store, TestFlight, or Enterprise distribution https://developer.apple.com/forums/thread/794192 Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Replies
Boosts
Views
Activity
1w