Search results for

missing package product

51,796 results found

Post

Replies

Boosts

Views

Activity

Notarization submissions stuck in “In Progress” for >24 hours (CI / REST API) – production impact
We are experiencing notarization submissions that remain in the “In Progress” state for an extended period (over 24 hours), with no status transition and no submission log available. This is occurring in an automated CI environment using the Notary REST API (non-interactive submission and polling). Re-submitting the same package only results in additional submissions also stuck in “In Progress”. There does not appear to be any API mechanism to cancel, clear, or expire these submissions once they are created. We have already opened an Apple Developer Support case regarding this issue (Case ID: 102818066745 & 102819008943), but have not yet received clarification on what is causing these long-running “In Progress” states. This issue is impacting our production release pipeline, as we are unable to reliably complete notarization for signed packages within an expected timeframe. Based on other reports in this forum (including thread 811968), this behavior appears similar to cases wh
3
0
364
2w
MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic.
MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic. Hardware and software configuration: MAC mini M1 2020 16GB, macOS Ventura 13.0 or 13.7.8 FPGA device capability: 64-bit Complete description: We've developed a DMA driver for PCIe devices (FPGA) based on IOKit. The driver can start normally through kextload, and the bar mapping, DMA registers, etc. are all correct. I am testing DMA data transmission, but a kernel panic has occurred. The specific content of the panic is as follows: {bug_type:210,timestamp:2026-01-28 14:35:30.00 +0800,os_version:macOS 13.0 (22A380),roots_installed:0,incident_id:61C9B820-8D1B-4E75-A4EB-10DC2558FA75} { build : macOS 13.0 (22A380), product : Macmini9,1, socId : 0x00008103, kernel : Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103, incident : 61C9B820-8D1B-4E75-A4EB-10DC2558FA75, crashReporterKey : 6435F6BD-4138-412A-5142-83DD7E5B4F61, date : 2026-01-28 14:35:30.16 +0800, panicString : panic(cpu 0 c
9
0
306
2w
How to Integrate Apple Wallet with Custom FinTech Apps
Hi everyone, With the rapid growth of digital banking, payments, and AI-driven financial services, building secure and scalable FinTech apps on iOS has become more complex than ever. From handling sensitive user data to ensuring compliance and seamless performance, iOS developers face multiple technical challenges. Key areas that usually require deep expertise include: Apple Pay and Wallet integrations Secure authentication (Face ID / Touch ID / biometrics) Real-time transaction processing Core ML for financial predictions SwiftUI dashboards for financial analytics Data encryption and regulatory compliance https://www.nimbleappgenie.com At Nimble AppGenie, we’ve worked extensively as a FinTech app development expert, helping startups and enterprises design and build iOS financial applications that are secure, scalable, and user-centric. Our experience shows that the most successful fintech apps are those that balance strong security architecture with intuitive UX and performance optimization. I’m interested t
0
0
92
2w
Use iTMSTransporter to upload the ipa file on Windows. ERROR: Client configuration failed
Use iTMSTransporter to upload the ipa file on Windows. ERROR: Client configuration failed [2026-02-05 16:35:17 CST] INFO: iTMSTransporter Correlation Key: a97add20-898c-4d66-81c8-a1e313f2807e-0001 [2026-02-05 16:35:17 CST] DEBUG: DataCenter: contentdelivery01.itunes.apple.com [2026-02-05 16:35:18 CST] DBG-X: Apple's web service operation return value: [2026-02-05 16:35:18 CST] DBG-X: parameter DSToken = hidden value [2026-02-05 16:35:18 CST] DBG-X: parameter DSTokenCookieName = myacinfo [2026-02-05 16:35:18 CST] ERROR: Client configuration failed Here is the error message. Package Summary: 1 package(s) were not uploaded because they had problems: C:UsersAdministratorDesktopbaggsl222.ipa - Error Messages: Client configuration failed [2026-02-05 16:35:18 CST] DBG-X: Returning 1
0
0
33
2w
URGENT: Multiple Notarization Submissions Stuck "In Progress" 5+ Days - Blocking Release
Hi Apple Developer Relations / Notary Service Team, CRITICAL: All notarization submissions stuck In Progress since Feb 1, 2026 (5+ days). Blocking product release. Latest (PRIORITY): 9bf1e3ca-33ed-4185-816c-2e06ff539f25 Stuck submissions: a9f1abf6-04a1-462c-b7d1-91e834b44c1a 94a172f8-4aa6-475c-a7ec-fd83c8cfc49a e2c033da-a1d0-480c-a3b5-5401a8dd3d03 eecefd87-8bf9-496c-86c8-c6f0d6a550e0 b1d27d30-7111-4cc7-9f0e-3f44aac43a97 Details: Team ID: JA8C8B5W34 App: 323MB DMG (codesign verified) notarytool log: not available (In Progress) Status page: Green Requests: Process 9bf1e3ca-33ed-4185-816c-2e06ff539f25 Queue status / ETA? @Quinn or Notary team - production blocker!
1
0
252
2w
Avoid creating dsyms for test targets in Xcode Cloud
Hi, our Xcode Cloud runs produce dsyms for test targets that massively increase the artifacts size, more specifically the Test Products for zip, that slows down the build due to the upload artifacts phase. These dsyms are useless, so we would like to stop producing them on Xcode Cloud builds. Consider that the workflow uses the autogenerated scheme for a package that's part of the Xcode project. How can we tell Xcode Cloud to not produce dsyms?
0
0
63
2w
Reply to All notarization submissions stuck "In Progress" for 24-72+ hours (including tiny 6KB test binary)
URGENT: Multiple Notarization Submissions Stuck In Progress 5+ Days - Blocking Release Hi Apple Developer Relations / Notary Service Team, CRITICAL: All notarization submissions stuck In Progress since Feb 1, 2026 (5+ days). Blocking product release. Latest (PRIORITY): 9bf1e3ca-33ed-4185-816c-2e06ff539f25 Stuck submissions: a9f1abf6-04a1-462c-b7d1-91e834b44c1a 94a172f8-4aa6-475c-a7ec-fd83c8cfc49a e2c033da-a1d0-480c-a3b5-5401a8dd3d03 eecefd87-8bf9-496c-86c8-c6f0d6a550e0 b1d27d30-7111-4cc7-9f0e-3f44aac43a97 Details: Team ID: JA8C8B5W34 App: 323MB DMG (codesign verified) notarytool log: not available (In Progress) Status page: Green Requests: Process 9bf1e3ca-33ed-4185-816c-2e06ff539f25 NOW Cancel old submissions Queue status / ETA? @Quinn or Notary team - production blocker!
Topic: Code Signing SubTopic: Notarization Tags:
2w
Same Color in View and colorEffect shader argument produce different results
Opened feedback item FB21877364. Context I have the following Metal shader, which replaces one color with another. [[ stitchable ]] half4 recolor( float2 position, half4 currentColor, half4 from, half4 to ) { if (all(currentColor == from)) return to; return currentColor; } Given this SwiftUI view: let shader = ShaderLibrary.recolor(.color(.red), .color(.green)) Color.red .colorEffect(shader) I get a red rectangle instead of the expected green one. Note that this works on both dynamic and non-dynamic colors. Note that this sometimes works with some colors, which is very inconvenient when trying to figure out what's going on. Did I miss something? I would've expected the shader to work with colors the same way. Issue To really highlight the issue, here's another test case. I'll define #94877E in an Asset Catalog as example and check the RGB values using the Digital Color Meter app in Display native values mode. We'll use the following shader to determine how colorEffect receives colors: [[ stitchable ]
Topic: UI Frameworks SubTopic: SwiftUI
0
0
20
2w
Request for Assistance Apple Developer Account Approval Delay
Dear Apple Developer Support Team, I hope this message finds you well. I am writing to seek assistance regarding my Apple Developer account, which is still pending approval. It has been several weeks since I completed the registration process and submitted all the required information, but I have not received any confirmation or update yet. We understand that the review process for Apple Enterprise Developer Accounts requires strict verification to ensure platform security and compliance, and we fully respect and cooperate with all the review standards and procedures formulated by Apple. According to the public information and practical experience of Apple’s developer program, the conventional review cycle for enterprise developer accounts is 2-4 weeks. However, as of today, more than a month has passed since we submitted the application, and we have not received any confirmation, feedback, or update on the review progress, either via email or phone.  The delay in the account approval has gradually affected
1
0
66
2w
Reply to Unexpected CoreBluetooth background suspension without active location updates
No, the scanning will not stop, but will slow down by a lot when the app is no longer in the foreground. CoreLocation and CoreBluetooth don't have any relation to each other as far as the capabilities go. If you are seeing a difference in CoreBluetooth behavior based on CoreLocation state, you should consider that as an unintended undocumented side effect and not rely on that observed effect for your product. The reason you might be thinking the scanning is stopping when the app is not in the foreground would be due to the slowed down scan rate for your app, the discovery of the advertising device is taking longer than you expect. The recommended advertising intervals for best power to time-of-discovery are 20 ms, 152.5 ms, 211.25 ms, 318.75 ms, 417.5 ms, 546.25 ms, 760 ms, 852.5 ms, 1022.5 ms, 1285 ms Even when using these intervals, it may take more than you expect if you are using one of the higher values. What I would suggest is to first set the advertising interval to 20ms to confirm that your a
Topic: App & System Services SubTopic: Core OS Tags:
2w
review keeps failing ovee IAP issue
hi, first time submitter her, having problems with IAP and getting review approved. Apple reviewer keeps saying that attempted purchase results in error: subscription product not available. please try again later i have verified that sandbox returns a product,. how else can i test this without just submitting again?
1
0
177
2w
Reply to CloudKit sync fails across TestFlight iOS + macOS builds — “Field recordName is not marked queryable”
Whether querying by recordName should work in production CloudKit Yes, in case you have the appropriate indice in the CloudKit production environment. What specifically causes the “Field recordName is not marked queryable” error in TestFlight builds The error is triggered when you try yo query a CloudKit record type and the type doesn't have the index for its recordName field. If the error only occurs in the production environment, which is by default used by a TestFlight build, and not in the development environment, it will indicate that the CloudKit schema in the development environment is not completely deployed to the production environment. To address the error, try to use CloudKit Console to add the indice, as discussed here and here. What steps are required to ensure CloudKit schemas are correctly deployed for cross-platform sync If you can use CKTool to dump the schemas, as discussed in Automate CloudKit tests with cktool and declarative schema, and then compare an
2w