Overview

Post

Replies

Boosts

Views

Created

Unable to Retrieve Existing Card Status from Apple Wallet
Hi, We are able to successfully perform in-app provisioning and add cards to the native wallet. However, we are unable to retrieve the existing card status from the wallet. Even when the card is already added to the device or Apple Watch, the status is always returning as false for both. Could you please let us know if there are any additional configurations, entitlements, or issuer onboarding steps required to retrieve the existing card status from Apple Wallet?
0
0
63
1d
[iPadOS / USBDriverKit] Communicating with RP2040: Avoiding OS preemption of standard CDC-ACM?
Hello everyone, I am currently working on an iPadOS application that requires communicating with a custom hardware board based on the Raspberry Pi RP2040 microcontroller via USB. My initial thought was to use the standard CDC-ACM (virtual serial port) profile on the RP2040. However, my understanding is that iPadOS's built-in system drivers will automatically claim any standard CDC-ACM interfaces, preempting my custom USBDriverKit driver from matching and taking control of the device. Is my assumption correct that iPadOS will strictly preempt a standard CDC-ACM device, making a custom DriverKit implementation impossible for that specific class?
1
0
39
1d
MagSafe 4 LED physics
The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that "carging," and "full" or "reached charging limit," is green, but in case you are far away, you need an estimate of battery percentage. A software magsafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, adding a yellow colour. it should be simple, here is the code: // 1. CRITICAL SAFETY CUT-OFF // If the system detects a hardware/thermal failure, // it cuts power and pulses RED. if (criticalError) { setLED(PULSING_RED); return; } // 2. SLOW CHARGER DETECTION // Logic: Air < 30W OR Pro < 70W triggers Pulsing Yellow. if ((isAir() && wattage < 30) || (isPro() && wattage < 70)) { setLED(PULSING_YELLOW); return; } // 3. CAPACITY GRADIENT // Simple, clear visual feedback based on your percentages. if (soc < 50) { setLED(COLOR_AMBER); // 0-50% } else if (soc >= 50 && soc < 90) { setLED(COLOR_YELLOW); // 50-90% } else if (soc >= 90) { setLED(COLOR_GREEN); // 90-100% }
Topic: Design SubTopic: General
2
0
132
1d
Sectigo Public Server Authentication CA DV R36?
When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading tcp_input [C2.1.1.1:3] flags=[R] seq=2572529641, ack=2572529641, win=251 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 tcp_input [C2.1.1.1:3] flags=[R] seq=2572535079, ack=2572535079, win=1981 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate)] already failing, returning nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 cancelled channel-flow ((null))] already failing, returning Connection 2: received failure notification Connection 2: received ECONNRESET with incomplete TLS handshake - generating errSSLClosedNoNotify Connection 2: failed to connect 3:-9816, reason -1 Connection 2: encountered error(3:-9816) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816]) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "Connessione sicura non riuscita a causa di un errore TLS." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x121bd4240>, NSErrorFailingURLKey=https://taxiprofessional.net/...php, NSErrorFailingURLStringKey=https://taxiprofessional.net/....php, NSErrorClientCertificateStateKey=0, NSErrorPeerCertificateChainKey=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>" ), NSLocalizedDescription=Connessione sicura non riuscita a causa di un errore TLS., _kCFStreamErrorDomainKey=3, NSUnderlyingError=0x121b7b0c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFNetworkCFStreamSSLErrorOriginalValue=-9816, kCFStreamPropertySSLPeerCertificates=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x121bd4240>, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816}}, _kCFStreamErrorCodeKey=-9816}
1
0
49
1d
Guideline 5.2.1 - Legal - Intellectual Property
Good Day All, I am new to the forum so not sure if I am posting this in the correct category. I have 2 other apps that are running successfully on appstore so I am not "fresh" when it comes to creating apps. :) but I have hit a wall with the one I am currently busy with and need some help to figure out the next step please. Currently I have a app that is fully built and working perfect in testflight. However, the app connects to specifically Garmin watches to get specific triggers. When you pair the app with your watch it looks for the GarminConnect app on your phone for the details and then links it. I have the companion Garmin app for the watch on the Garmin store and that is approved. All good that also works. But when I send the app for review so I can release it I get the following response from the team : Guideline 5.2.1 - Legal - Intellectual Property Issue Description The app includes content or features from Garmin, or is marketed to control external hardware from Garmin, without the necessary authorization. The inclusion of third-party content within the app, whether retrieved from the internet by the app or embedded in the app, is subject to the terms of the Apple Developer Program License Agreement. The app and its contents should not infringe upon the rights of another party. In the event the app infringes another party’s rights, you are responsible for any liability to Apple because of a claim. Next Steps To resolve this issue, please attach documentary evidence in the App Review Information section in App Store Connect. Once we have reviewed your documentation and confirmed its validity, we will proceed with the review of the app. Alternatively, please remove the third-party content from the app and its metadata. I have sent them : Hi There My app communicates with Garmin watches exclusively through the official Garmin Connect IQ Companion App SDK. I am a registered Garmin developer (developer name: removed) and have accepted the Garmin Connect IQ Developer Agreement, which explicitly licenses the Companion App API for third-party iOS developers. My Garmin watch app is approved and published on the Garmin Connect IQ Store. I have attached: (1) the Garmin Connect IQ Developer Agreement, (2) my Garmin Developer Dashboard confirming registration, and (3) my app listing on the CIQ Store showing Approved status. I dont really know what else to add to confirm that it has been approved from Garmin's side to approve the app in IOS. I have also now attached a screenshot of the app in the GarminApp store showing that it links with IOS (Dashboard3.png) and that was approved on Garmin side. Thanks in advance Message Attachments: Garmin CONNECT IQ Agreement.pdfDownload Dashboard1.pngDownload Dashboard2.pngDownload Dashboard3.pngDownload They responded basically with the same message which I then sent them the details again and now we are stuck in this loop of them asking for that and I am sending what I have which is clearly not what they are looking for. Can anyone please assist by telling me what I need to send to them to get this resolved or what I can do? Thank you!!
0
0
78
1d
-startDownloadingUbiquitousItemAtURL:error: and NSURLUbiquitousItemDownloadRequestedKey
I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@"error downloading %@ : %@", self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] error:&error]; if (!error) { NSString *downloadStatus = resourceValues[NSURLUbiquitousItemDownloadingStatusKey]; bool downloadRequested = [resourceValues[NSURLUbiquitousItemDownloadRequestedKey] boolValue]; NSLog(@"download requested: %d", downloadRequested); } // ... } downloadRequested is always false, regardless of whether or not the cloud file eventually downloads. I have 2 questions: is there a way to actually check if a download has been requested for a file? what could be preventing this file from downloading? -startDownloadingUbiquitousItemAtURL:error: doesn't report an error, NSURLUbiquitousItemDownloadingErrorKey is always nil, and no error is reported in the NSMetadataQuery observer.
2
0
65
1d
Apple Subscription Offer Code Behavior
I would like to ask for clarification regarding the specifications of Apple Subscriptions. We are currently planning a subscription discount campaign using Offer Codes, and during testing we encountered the following issue. Test scenario: A user who does not have our app installed accesses a URL that contains an Offer Code. The App Store opens and displays the details of the Offer Code. The user reviews the offer and proceeds, at which point the App Store prompts the user to install our app. The user installs the app and launches it. Issue: The subscription remains in an unpurchased state. From the app implementation side, when the app launches, we attempt to retrieve transactions held by Apple using unfinishedTransactions. However, no transaction is returned, so the app cannot transition the user to a subscribed state. In contrast, when a user who already has the app installed accesses the Offer Code URL (step 1), the app can successfully retrieve the unfinished transaction via unfinishedTransactions on launch and correctly switch the user to a subscribed state. Could you please advise on the root cause of this behavior, or whether there is a recommended workaround for this scenario?
0
0
14
1d
App Stuck in “Waiting for Review” for Several Days Without Response
Hi Team, We are facing an issue with our app review process for Chinmaya Clix. Our previous build was submitted on April 30, 2026, and it remained in the “Waiting for Review” state until May 7, 2026 without any update or response from Apple. During this period, we also submitted an expedited review request and contacted Apple Support multiple times, but did not receive any response. After waiting for several days, we rejected the previous build and submitted a new build on May 7, 2026 at 3:36 PM (IST). We again submitted an expedited review request for the latest build, but the app is still stuck in the “Waiting for Review” state. Details for reference: App Name: Chinmaya Clix Support Case ID: 102886900142 Previous Submission ID: eff3c432-bc87-4ec8-9fac-3b23b795cb7d Current Submission ID: a1fc7506-b47c-4da6-9248-207c9b318f70 Current Submission Date: May 7, 2026 at 3:36 PM (IST) Our app release is time-sensitive and planned for this week, so we would really appreciate any guidance regarding: Possible reason for the delay Expected review timeline Any further communication or escalation process we should follow If anyone from Apple or the developer community has experienced something similar, please let us know. Thank you.
0
0
36
1d
App Review Delay for so long
Hello App Review Team, We respectfully ask for your assistance regarding our app review status. Our submission was re-submitted on April 29, 2026, and it has now been waiting for review for more than 12 days without any update or response. In addition, we have already been working through the review process for this app on this developer account for almost 4 months. We carefully addressed all previous review feedback and submitted the required fixes, but the review process continues to experience very long delays. This situation is now seriously impacting our planned product launch, business operations, and partner commitments. We sincerely ask if the App Review Team could please help: Review the current submission status Escalate the case internally if possible Help move the review process forward Reference Information: Case Number: 102877213113 Submission ID: 68850cef-1651-40c8-b717-7916b679a467 We would greatly appreciate any assistance or update regarding this matter. Thank you very much.
0
0
37
1d
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN)
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN) Category: RealityKit / visionOS Environment: visionOS 26.x Summary: Modifying PhysicsBodyComponent.massProperties at runtime on an entity loaded from a .usdz file silently corrupts the entity's transform. The translation and scale components become NaN, while rotation remains valid. The corruption occurs during the next RealityKit scene update cycle (e.g., during an await suspension on the main actor). Steps to Reproduce: Author a .usda file with a RigidBody component including valid m_mass and m_inertia values Load the entity at runtime via Entity(named: "MyEntity.usdz", in: bundle) Read the existing PhysicsBodyComponent, modify massProperties, and set it back: if var physics = entity.components[PhysicsBodyComponent.self] { physics.massProperties = .init( mass: 1.944, inertia: SIMD3<Float>(0.013, 0.026, 0.016), centerOfMass: (position: .zero, orientation: .init()) ) entity.components.set(physics) } Add the entity to the scene Perform any await call (e.g., TextureResource(contentsOf:)) that yields to the main actor, allowing a RealityKit scene update to run Expected: The entity retains its position and scale with the updated mass/inertia values. Actual: The entity's transform becomes corrupted: Transform( scale: SIMD3<Float>(nan, nan, nan), rotation: simd_quatf(real: 1.0, imag: SIMD3<Float>(0.0, 0.0, 0.0)), // ← fine translation: SIMD3<Float>(-nan, -nan, -nan) ) Additional findings from investigation: The entity's physics mode does not matter — corruption occurs even when the entity is .kinematic Creating a new PhysicsBodyComponent(...) and replacing the existing one also triggers the bug Modifying other properties on the same component (linearDamping, angularDamping, material, mode) does not cause corruption — only massProperties triggers it The parent entity's transform remains valid The computed mass/inertia values themselves are valid (finite, positive) The corruption is silent — no error, no warning, no crash from RealityKit itself Workaround: Author mass and inertia values directly in the .usda file and do not modify massProperties at runtime: def RealityKitStruct "massFrame" { float3 m_inertia = (0.02, 0.02, 0.038) float m_mass = 2.5 def RealityKitStruct "m_pose" { } } Other PhysicsBodyComponent properties (damping, material, mode) can safely be modified at runtime.
1
0
215
1d
App stuck “In Review” for 10 days – is anyone else experiencing this?
Hello everyone, My app has been stuck in “In Review” for around 10 days without any update. I have not received any rejection, metadata request, or additional information request from the review team. The app is simply remaining in review with no movement. What worries me the most is that I have already contacted the App Review Team multiple times through App Store Connect, but I still have not received any response. Is anyone else experiencing the same situation recently? Have you found any effective way to speed up the review process? Thank you very much.
0
0
13
1d
Apple Developer Support, please respond! I need your help
(Note: I don't need DTS support. This is not a DTS issue, and the standard responses aren't relevant to the situation. I would ask that DTS not respond in lieu of the developer support official) Yesterday, a poster in this forum wrote about his experience waiting several months to get approved to have his apps notarized. He had hit the "status code 7000; Team ID not configured for notarization" block. An Apple Developer Support account responded to him saying they would help the poster. After a month of waiting and praying for Developer Support to approve my Team ID for notarization, and no progress via the official channels, I am rolling the dice that asking Developer Support here will get my account approved or at least moved forward. I just can't wrap my head around why it takes so long to allow a Team ID to submit apps for notarization. My Team ID is V67NRZ84A2, and my support ticket is 102874600970. Spending months and months developing an app, paying the Developer Support annual fee, and then having to sit on your hands for months while your app gathers dust due to the Status Code 7000 bottleneck is very demoralizing. Again, not a DTS issue. The official channels 100% do not work. Developer Support did respond to a poster yesterday, so this is the pathway I'm hoping will lead to my Team ID getting permission to notarize apps. As it stands, no other method is leading to the problem getting resolved.
1
0
51
1d
tvOS SwiftUI - Siri "On-Screen Actions" breaks lazy lists
Hey team, This is a weird one, when Siri + "On-Screen Actions" are enabled in the Apple TV settings (General Settings), LazyVStack experiences severe main-thread hangs and very high CPU usage. The issue only occurs when Siri + On-Screen Actions are enabled in Apple TV device settings (General Settings). Disabling On-Screen Actions completely resolves the issue. The issue has been verified on multiple Apple TV devices, running tvOS 26.3, 26.4 and 26.5. The behavior was not observed in Simulators, only on an actual device. This seems to be caused by some type of accessibility overlap with SwiftUI. Running the below code with "On-Screen Actions" enabled in the Siri settings will demonstrate a complete hang of the CPU at 100% struct TestData { let id = UUID() var title: String } struct TestView: View { @State private var test: [TestData] = [] var body: some View { ScrollView { LazyVStack { ForEach(self.test, id: \.id) { data in Button { } label: { Text(data.title) } } } } .task { var arr: [TestData] = [] for _ in 0..<30000 { let data = TestData(title: "Title") arr.append(data) } self.test = arr } } } Already submited a bug report FB22758928
0
0
102
1d
App Store Server Notification v2: how to distinguish a resubscription that happened in-app from one that happened in Settings → Subscriptions?
Context We're handling App Store subscriptions on the server side using App Store Server Notification v2. Our pipeline currently identifies each event by transactionId and originalTransactionId. A few notes about our client: Our app is built with Flutter and uses the standard in_app_purchase plugin layer to drive App Store purchases (StoreKit 1 under the hood). We have not migrated to StoreKit 2 on the client yet. We have not been setting SKPayment.applicationUsername on outgoing purchases, so every transaction we've ever produced has appAccountToken: null in its v2 notification. This question is purely about what the server-side notification can tell us, given the current client state above. What we're trying to figure out A user can resubscribe to an expired subscription in two different places: In-app — the user opens our app and re-purchases through our normal in-app purchase flow. App Store — the user goes to Settings → Apple ID → Subscriptions and resubscribes from the system UI, without ever returning to the app. Both paths trigger a SUBSCRIBED notification (subtype RESUBSCRIBE) with structurally identical payloads as far as we can tell — same shape for data.transactionInfo, data.renewalInfo, etc. From the notification alone we can't decide which path produced it. The reason this matters: in our system, the two paths require different business handling: In-app path: the user may have signed in to a different business account in our app. The new subscription should be attributed to whoever paid in the app just now, not to the previous owner of originalTransactionId. App Store path: there is no in-app signal, so the business owner can only be inferred from the previous originalTransactionId mapping. If we get it wrong, the subscription's entitlement ends up on the wrong business account. What we do today Because we can't tell the paths apart from the notification, we defer processing for a few minutes and check whether an in-app order for the same transaction has arrived in the meantime: If an in-app order shows up → it's the in-app path; attribute to the in-app account. If nothing shows up after the delay → assume App Store path; fall back to the previous owner mapping. This works but adds latency to entitlement activation and forces us to build a deferred-retry queue with idempotency against the in-app callback path. Possible direction: appAccountToken / applicationUsername We noticed that v2 notifications carry transactionInfo.appAccountToken, and the docs suggest that StoreKit 1's SKPayment.applicationUsername (when it's a valid UUID) is mirrored into this field. In theory, if we start setting it on every in-app purchase from the Flutter client, the field could double as a path discriminator on the server: appAccountToken != null → in-app path (only the app can set it), and we even get the business user id for free appAccountToken == null → App Store path (no UI to populate it) But we have some open questions before committing to this direction: Questions Is there an existing signal in ResponseBodyV2 / JWSTransactionDecodedPayload / JWSRenewalInfoDecodedPayload that distinguishes these two paths, that I might be missing? Can the same distinction be obtained via getAllSubscriptionStatuses / getTransactionHistory / any other Server API endpoint? Is applicationUsername (StoreKit 1) still a reliable way to populate appAccountToken on v2 notifications today? Specifically: Are there format constraints beyond "valid UUID" that cause Apple to drop the value? Any known differences between sandbox and production in how it's mirrored? Does the App Store path ever strip or overwrite a previously-set value when the same originalTransactionId is reused? For existing subscriptions where applicationUsername was never set (which is all of ours today, since we've never polient), is there any way to retroactively distinguish the in-app vs App Store path? Or is timing-based deferred matching theonly option for that cohort, even after we start setting the value on new purchases? If neither (1) nor (2) is currently possible, is the timing-based heuristic we use today the pattern Apple expects developers to follow, or is there a recommended approach we're missing? A small suggestion, if it turns out there's no existing way If the information genuinely isn't exposed today, it might be worth surfacing a salesChannel-style field on the transaction, similar to what Google Play Developer API exposes on Order.salesChannel (IN_APP, PLAY_STORE, etc.). That would let server-side handlers route each event to the correct business owner immediately, regardless of whether appAccountToken was set, and would also cover legacynt never had a chance to populate it. Thanks — happy to share sample payloads or more detail if helpful.
1
0
56
1d
Testflight issue
Hi, I have been using Testflight iOS app to test my apps before releasing to production. Over the past few weeks, I am unable to install any of my apps through Testflight. I also don't get any email notification that my app is live on Testflight. This is really important and it would be really helpful if I can find any solution to this. Thank you so much.
0
0
55
2d
My application for organization status is taking a very long time to process.
I submitted the application with my DUNS number on May 8, 2026, and today is already May 11, 2026. After submitting the form, it said the process would take about 1 day, but quite a bit of time has already passed and I still have not received organization status. I also have not received any emails from Apple. Could there possibly be some issue that I am not aware of?
0
0
24
2d
Xcode 26 beta stricter codesign validation rejecting Flutter.framework
While testing Flutter applications on macOS 26 beta with Xcode 26 beta, iOS builds consistently fail during Flutter.framework codesigning with: "resource fork, Finder information, or similar detritus not allowed" Investigation suggests newer Xcode beta versions now reject additional extended attributes beyond com.apple.FinderInfo during codesigning. Flutter tooling currently removes only: xattr -r -d com.apple.FinderInfo Replacing it with: xattr -cr successfully resolves the issue. Environment: macOS 26.4.1 beta Xcode 26.4.1 beta Apple Silicon (ARM64) Flutter 3.41.9 Flutter issue: https://github.com/flutter/flutter/issues/186372 Apple Feedback Assistant report: FB22756923 Interested to know whether other developers on Xcode 26 beta are seeing similar stricter codesigning validation behavior.
1
0
66
2d
IAP Issue
Hi, Can someone help me with this issue I'm having with my app's IAP functionality? When you click on the unlock Premium button on the pop-up window, it should trigger the purchase action. However, there is an error when a user clicks on the button; this error appears as " Product Not Found." Please check App Store Connect Configuration". Has anyone faced this issue before, and how was it resolved? My backend code is right, and the IAP configuration in App Store Connect is right and approved, including the Agreement.
1
0
47
2d
TestFlight install fails with BETA_CONTRACT_MISSING although all agreements are active
Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?
0
0
25
2d
Unable to Retrieve Existing Card Status from Apple Wallet
Hi, We are able to successfully perform in-app provisioning and add cards to the native wallet. However, we are unable to retrieve the existing card status from the wallet. Even when the card is already added to the device or Apple Watch, the status is always returning as false for both. Could you please let us know if there are any additional configurations, entitlements, or issuer onboarding steps required to retrieve the existing card status from Apple Wallet?
Replies
0
Boosts
0
Views
63
Activity
1d
[iPadOS / USBDriverKit] Communicating with RP2040: Avoiding OS preemption of standard CDC-ACM?
Hello everyone, I am currently working on an iPadOS application that requires communicating with a custom hardware board based on the Raspberry Pi RP2040 microcontroller via USB. My initial thought was to use the standard CDC-ACM (virtual serial port) profile on the RP2040. However, my understanding is that iPadOS's built-in system drivers will automatically claim any standard CDC-ACM interfaces, preempting my custom USBDriverKit driver from matching and taking control of the device. Is my assumption correct that iPadOS will strictly preempt a standard CDC-ACM device, making a custom DriverKit implementation impossible for that specific class?
Replies
1
Boosts
0
Views
39
Activity
1d
MagSafe 4 LED physics
The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that "carging," and "full" or "reached charging limit," is green, but in case you are far away, you need an estimate of battery percentage. A software magsafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, adding a yellow colour. it should be simple, here is the code: // 1. CRITICAL SAFETY CUT-OFF // If the system detects a hardware/thermal failure, // it cuts power and pulses RED. if (criticalError) { setLED(PULSING_RED); return; } // 2. SLOW CHARGER DETECTION // Logic: Air < 30W OR Pro < 70W triggers Pulsing Yellow. if ((isAir() && wattage < 30) || (isPro() && wattage < 70)) { setLED(PULSING_YELLOW); return; } // 3. CAPACITY GRADIENT // Simple, clear visual feedback based on your percentages. if (soc < 50) { setLED(COLOR_AMBER); // 0-50% } else if (soc >= 50 && soc < 90) { setLED(COLOR_YELLOW); // 50-90% } else if (soc >= 90) { setLED(COLOR_GREEN); // 90-100% }
Topic: Design SubTopic: General
Replies
2
Boosts
0
Views
132
Activity
1d
Sectigo Public Server Authentication CA DV R36?
When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading tcp_input [C2.1.1.1:3] flags=[R] seq=2572529641, ack=2572529641, win=251 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 tcp_input [C2.1.1.1:3] flags=[R] seq=2572535079, ack=2572535079, win=1981 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate)] already failing, returning nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 cancelled channel-flow ((null))] already failing, returning Connection 2: received failure notification Connection 2: received ECONNRESET with incomplete TLS handshake - generating errSSLClosedNoNotify Connection 2: failed to connect 3:-9816, reason -1 Connection 2: encountered error(3:-9816) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816]) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "Connessione sicura non riuscita a causa di un errore TLS." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x121bd4240>, NSErrorFailingURLKey=https://taxiprofessional.net/...php, NSErrorFailingURLStringKey=https://taxiprofessional.net/....php, NSErrorClientCertificateStateKey=0, NSErrorPeerCertificateChainKey=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>" ), NSLocalizedDescription=Connessione sicura non riuscita a causa di un errore TLS., _kCFStreamErrorDomainKey=3, NSUnderlyingError=0x121b7b0c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFNetworkCFStreamSSLErrorOriginalValue=-9816, kCFStreamPropertySSLPeerCertificates=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x121bd4240>, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816}}, _kCFStreamErrorCodeKey=-9816}
Replies
1
Boosts
0
Views
49
Activity
1d
Guideline 5.2.1 - Legal - Intellectual Property
Good Day All, I am new to the forum so not sure if I am posting this in the correct category. I have 2 other apps that are running successfully on appstore so I am not "fresh" when it comes to creating apps. :) but I have hit a wall with the one I am currently busy with and need some help to figure out the next step please. Currently I have a app that is fully built and working perfect in testflight. However, the app connects to specifically Garmin watches to get specific triggers. When you pair the app with your watch it looks for the GarminConnect app on your phone for the details and then links it. I have the companion Garmin app for the watch on the Garmin store and that is approved. All good that also works. But when I send the app for review so I can release it I get the following response from the team : Guideline 5.2.1 - Legal - Intellectual Property Issue Description The app includes content or features from Garmin, or is marketed to control external hardware from Garmin, without the necessary authorization. The inclusion of third-party content within the app, whether retrieved from the internet by the app or embedded in the app, is subject to the terms of the Apple Developer Program License Agreement. The app and its contents should not infringe upon the rights of another party. In the event the app infringes another party’s rights, you are responsible for any liability to Apple because of a claim. Next Steps To resolve this issue, please attach documentary evidence in the App Review Information section in App Store Connect. Once we have reviewed your documentation and confirmed its validity, we will proceed with the review of the app. Alternatively, please remove the third-party content from the app and its metadata. I have sent them : Hi There My app communicates with Garmin watches exclusively through the official Garmin Connect IQ Companion App SDK. I am a registered Garmin developer (developer name: removed) and have accepted the Garmin Connect IQ Developer Agreement, which explicitly licenses the Companion App API for third-party iOS developers. My Garmin watch app is approved and published on the Garmin Connect IQ Store. I have attached: (1) the Garmin Connect IQ Developer Agreement, (2) my Garmin Developer Dashboard confirming registration, and (3) my app listing on the CIQ Store showing Approved status. I dont really know what else to add to confirm that it has been approved from Garmin's side to approve the app in IOS. I have also now attached a screenshot of the app in the GarminApp store showing that it links with IOS (Dashboard3.png) and that was approved on Garmin side. Thanks in advance Message Attachments: Garmin CONNECT IQ Agreement.pdfDownload Dashboard1.pngDownload Dashboard2.pngDownload Dashboard3.pngDownload They responded basically with the same message which I then sent them the details again and now we are stuck in this loop of them asking for that and I am sending what I have which is clearly not what they are looking for. Can anyone please assist by telling me what I need to send to them to get this resolved or what I can do? Thank you!!
Replies
0
Boosts
0
Views
78
Activity
1d
-startDownloadingUbiquitousItemAtURL:error: and NSURLUbiquitousItemDownloadRequestedKey
I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@"error downloading %@ : %@", self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] error:&error]; if (!error) { NSString *downloadStatus = resourceValues[NSURLUbiquitousItemDownloadingStatusKey]; bool downloadRequested = [resourceValues[NSURLUbiquitousItemDownloadRequestedKey] boolValue]; NSLog(@"download requested: %d", downloadRequested); } // ... } downloadRequested is always false, regardless of whether or not the cloud file eventually downloads. I have 2 questions: is there a way to actually check if a download has been requested for a file? what could be preventing this file from downloading? -startDownloadingUbiquitousItemAtURL:error: doesn't report an error, NSURLUbiquitousItemDownloadingErrorKey is always nil, and no error is reported in the NSMetadataQuery observer.
Replies
2
Boosts
0
Views
65
Activity
1d
Apple Subscription Offer Code Behavior
I would like to ask for clarification regarding the specifications of Apple Subscriptions. We are currently planning a subscription discount campaign using Offer Codes, and during testing we encountered the following issue. Test scenario: A user who does not have our app installed accesses a URL that contains an Offer Code. The App Store opens and displays the details of the Offer Code. The user reviews the offer and proceeds, at which point the App Store prompts the user to install our app. The user installs the app and launches it. Issue: The subscription remains in an unpurchased state. From the app implementation side, when the app launches, we attempt to retrieve transactions held by Apple using unfinishedTransactions. However, no transaction is returned, so the app cannot transition the user to a subscribed state. In contrast, when a user who already has the app installed accesses the Offer Code URL (step 1), the app can successfully retrieve the unfinished transaction via unfinishedTransactions on launch and correctly switch the user to a subscribed state. Could you please advise on the root cause of this behavior, or whether there is a recommended workaround for this scenario?
Replies
0
Boosts
0
Views
14
Activity
1d
App Stuck in “Waiting for Review” for Several Days Without Response
Hi Team, We are facing an issue with our app review process for Chinmaya Clix. Our previous build was submitted on April 30, 2026, and it remained in the “Waiting for Review” state until May 7, 2026 without any update or response from Apple. During this period, we also submitted an expedited review request and contacted Apple Support multiple times, but did not receive any response. After waiting for several days, we rejected the previous build and submitted a new build on May 7, 2026 at 3:36 PM (IST). We again submitted an expedited review request for the latest build, but the app is still stuck in the “Waiting for Review” state. Details for reference: App Name: Chinmaya Clix Support Case ID: 102886900142 Previous Submission ID: eff3c432-bc87-4ec8-9fac-3b23b795cb7d Current Submission ID: a1fc7506-b47c-4da6-9248-207c9b318f70 Current Submission Date: May 7, 2026 at 3:36 PM (IST) Our app release is time-sensitive and planned for this week, so we would really appreciate any guidance regarding: Possible reason for the delay Expected review timeline Any further communication or escalation process we should follow If anyone from Apple or the developer community has experienced something similar, please let us know. Thank you.
Replies
0
Boosts
0
Views
36
Activity
1d
App Review Delay for so long
Hello App Review Team, We respectfully ask for your assistance regarding our app review status. Our submission was re-submitted on April 29, 2026, and it has now been waiting for review for more than 12 days without any update or response. In addition, we have already been working through the review process for this app on this developer account for almost 4 months. We carefully addressed all previous review feedback and submitted the required fixes, but the review process continues to experience very long delays. This situation is now seriously impacting our planned product launch, business operations, and partner commitments. We sincerely ask if the App Review Team could please help: Review the current submission status Escalate the case internally if possible Help move the review process forward Reference Information: Case Number: 102877213113 Submission ID: 68850cef-1651-40c8-b717-7916b679a467 We would greatly appreciate any assistance or update regarding this matter. Thank you very much.
Replies
0
Boosts
0
Views
37
Activity
1d
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN)
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN) Category: RealityKit / visionOS Environment: visionOS 26.x Summary: Modifying PhysicsBodyComponent.massProperties at runtime on an entity loaded from a .usdz file silently corrupts the entity's transform. The translation and scale components become NaN, while rotation remains valid. The corruption occurs during the next RealityKit scene update cycle (e.g., during an await suspension on the main actor). Steps to Reproduce: Author a .usda file with a RigidBody component including valid m_mass and m_inertia values Load the entity at runtime via Entity(named: "MyEntity.usdz", in: bundle) Read the existing PhysicsBodyComponent, modify massProperties, and set it back: if var physics = entity.components[PhysicsBodyComponent.self] { physics.massProperties = .init( mass: 1.944, inertia: SIMD3<Float>(0.013, 0.026, 0.016), centerOfMass: (position: .zero, orientation: .init()) ) entity.components.set(physics) } Add the entity to the scene Perform any await call (e.g., TextureResource(contentsOf:)) that yields to the main actor, allowing a RealityKit scene update to run Expected: The entity retains its position and scale with the updated mass/inertia values. Actual: The entity's transform becomes corrupted: Transform( scale: SIMD3<Float>(nan, nan, nan), rotation: simd_quatf(real: 1.0, imag: SIMD3<Float>(0.0, 0.0, 0.0)), // ← fine translation: SIMD3<Float>(-nan, -nan, -nan) ) Additional findings from investigation: The entity's physics mode does not matter — corruption occurs even when the entity is .kinematic Creating a new PhysicsBodyComponent(...) and replacing the existing one also triggers the bug Modifying other properties on the same component (linearDamping, angularDamping, material, mode) does not cause corruption — only massProperties triggers it The parent entity's transform remains valid The computed mass/inertia values themselves are valid (finite, positive) The corruption is silent — no error, no warning, no crash from RealityKit itself Workaround: Author mass and inertia values directly in the .usda file and do not modify massProperties at runtime: def RealityKitStruct "massFrame" { float3 m_inertia = (0.02, 0.02, 0.038) float m_mass = 2.5 def RealityKitStruct "m_pose" { } } Other PhysicsBodyComponent properties (damping, material, mode) can safely be modified at runtime.
Replies
1
Boosts
0
Views
215
Activity
1d
App stuck “In Review” for 10 days – is anyone else experiencing this?
Hello everyone, My app has been stuck in “In Review” for around 10 days without any update. I have not received any rejection, metadata request, or additional information request from the review team. The app is simply remaining in review with no movement. What worries me the most is that I have already contacted the App Review Team multiple times through App Store Connect, but I still have not received any response. Is anyone else experiencing the same situation recently? Have you found any effective way to speed up the review process? Thank you very much.
Replies
0
Boosts
0
Views
13
Activity
1d
Apple Developer Support, please respond! I need your help
(Note: I don't need DTS support. This is not a DTS issue, and the standard responses aren't relevant to the situation. I would ask that DTS not respond in lieu of the developer support official) Yesterday, a poster in this forum wrote about his experience waiting several months to get approved to have his apps notarized. He had hit the "status code 7000; Team ID not configured for notarization" block. An Apple Developer Support account responded to him saying they would help the poster. After a month of waiting and praying for Developer Support to approve my Team ID for notarization, and no progress via the official channels, I am rolling the dice that asking Developer Support here will get my account approved or at least moved forward. I just can't wrap my head around why it takes so long to allow a Team ID to submit apps for notarization. My Team ID is V67NRZ84A2, and my support ticket is 102874600970. Spending months and months developing an app, paying the Developer Support annual fee, and then having to sit on your hands for months while your app gathers dust due to the Status Code 7000 bottleneck is very demoralizing. Again, not a DTS issue. The official channels 100% do not work. Developer Support did respond to a poster yesterday, so this is the pathway I'm hoping will lead to my Team ID getting permission to notarize apps. As it stands, no other method is leading to the problem getting resolved.
Replies
1
Boosts
0
Views
51
Activity
1d
tvOS SwiftUI - Siri "On-Screen Actions" breaks lazy lists
Hey team, This is a weird one, when Siri + "On-Screen Actions" are enabled in the Apple TV settings (General Settings), LazyVStack experiences severe main-thread hangs and very high CPU usage. The issue only occurs when Siri + On-Screen Actions are enabled in Apple TV device settings (General Settings). Disabling On-Screen Actions completely resolves the issue. The issue has been verified on multiple Apple TV devices, running tvOS 26.3, 26.4 and 26.5. The behavior was not observed in Simulators, only on an actual device. This seems to be caused by some type of accessibility overlap with SwiftUI. Running the below code with "On-Screen Actions" enabled in the Siri settings will demonstrate a complete hang of the CPU at 100% struct TestData { let id = UUID() var title: String } struct TestView: View { @State private var test: [TestData] = [] var body: some View { ScrollView { LazyVStack { ForEach(self.test, id: \.id) { data in Button { } label: { Text(data.title) } } } } .task { var arr: [TestData] = [] for _ in 0..<30000 { let data = TestData(title: "Title") arr.append(data) } self.test = arr } } } Already submited a bug report FB22758928
Replies
0
Boosts
0
Views
102
Activity
1d
App Store Server Notification v2: how to distinguish a resubscription that happened in-app from one that happened in Settings → Subscriptions?
Context We're handling App Store subscriptions on the server side using App Store Server Notification v2. Our pipeline currently identifies each event by transactionId and originalTransactionId. A few notes about our client: Our app is built with Flutter and uses the standard in_app_purchase plugin layer to drive App Store purchases (StoreKit 1 under the hood). We have not migrated to StoreKit 2 on the client yet. We have not been setting SKPayment.applicationUsername on outgoing purchases, so every transaction we've ever produced has appAccountToken: null in its v2 notification. This question is purely about what the server-side notification can tell us, given the current client state above. What we're trying to figure out A user can resubscribe to an expired subscription in two different places: In-app — the user opens our app and re-purchases through our normal in-app purchase flow. App Store — the user goes to Settings → Apple ID → Subscriptions and resubscribes from the system UI, without ever returning to the app. Both paths trigger a SUBSCRIBED notification (subtype RESUBSCRIBE) with structurally identical payloads as far as we can tell — same shape for data.transactionInfo, data.renewalInfo, etc. From the notification alone we can't decide which path produced it. The reason this matters: in our system, the two paths require different business handling: In-app path: the user may have signed in to a different business account in our app. The new subscription should be attributed to whoever paid in the app just now, not to the previous owner of originalTransactionId. App Store path: there is no in-app signal, so the business owner can only be inferred from the previous originalTransactionId mapping. If we get it wrong, the subscription's entitlement ends up on the wrong business account. What we do today Because we can't tell the paths apart from the notification, we defer processing for a few minutes and check whether an in-app order for the same transaction has arrived in the meantime: If an in-app order shows up → it's the in-app path; attribute to the in-app account. If nothing shows up after the delay → assume App Store path; fall back to the previous owner mapping. This works but adds latency to entitlement activation and forces us to build a deferred-retry queue with idempotency against the in-app callback path. Possible direction: appAccountToken / applicationUsername We noticed that v2 notifications carry transactionInfo.appAccountToken, and the docs suggest that StoreKit 1's SKPayment.applicationUsername (when it's a valid UUID) is mirrored into this field. In theory, if we start setting it on every in-app purchase from the Flutter client, the field could double as a path discriminator on the server: appAccountToken != null → in-app path (only the app can set it), and we even get the business user id for free appAccountToken == null → App Store path (no UI to populate it) But we have some open questions before committing to this direction: Questions Is there an existing signal in ResponseBodyV2 / JWSTransactionDecodedPayload / JWSRenewalInfoDecodedPayload that distinguishes these two paths, that I might be missing? Can the same distinction be obtained via getAllSubscriptionStatuses / getTransactionHistory / any other Server API endpoint? Is applicationUsername (StoreKit 1) still a reliable way to populate appAccountToken on v2 notifications today? Specifically: Are there format constraints beyond "valid UUID" that cause Apple to drop the value? Any known differences between sandbox and production in how it's mirrored? Does the App Store path ever strip or overwrite a previously-set value when the same originalTransactionId is reused? For existing subscriptions where applicationUsername was never set (which is all of ours today, since we've never polient), is there any way to retroactively distinguish the in-app vs App Store path? Or is timing-based deferred matching theonly option for that cohort, even after we start setting the value on new purchases? If neither (1) nor (2) is currently possible, is the timing-based heuristic we use today the pattern Apple expects developers to follow, or is there a recommended approach we're missing? A small suggestion, if it turns out there's no existing way If the information genuinely isn't exposed today, it might be worth surfacing a salesChannel-style field on the transaction, similar to what Google Play Developer API exposes on Order.salesChannel (IN_APP, PLAY_STORE, etc.). That would let server-side handlers route each event to the correct business owner immediately, regardless of whether appAccountToken was set, and would also cover legacynt never had a chance to populate it. Thanks — happy to share sample payloads or more detail if helpful.
Replies
1
Boosts
0
Views
56
Activity
1d
Testflight issue
Hi, I have been using Testflight iOS app to test my apps before releasing to production. Over the past few weeks, I am unable to install any of my apps through Testflight. I also don't get any email notification that my app is live on Testflight. This is really important and it would be really helpful if I can find any solution to this. Thank you so much.
Replies
0
Boosts
0
Views
55
Activity
2d
My application for organization status is taking a very long time to process.
I submitted the application with my DUNS number on May 8, 2026, and today is already May 11, 2026. After submitting the form, it said the process would take about 1 day, but quite a bit of time has already passed and I still have not received organization status. I also have not received any emails from Apple. Could there possibly be some issue that I am not aware of?
Replies
0
Boosts
0
Views
24
Activity
2d
Xcode 26 beta stricter codesign validation rejecting Flutter.framework
While testing Flutter applications on macOS 26 beta with Xcode 26 beta, iOS builds consistently fail during Flutter.framework codesigning with: "resource fork, Finder information, or similar detritus not allowed" Investigation suggests newer Xcode beta versions now reject additional extended attributes beyond com.apple.FinderInfo during codesigning. Flutter tooling currently removes only: xattr -r -d com.apple.FinderInfo Replacing it with: xattr -cr successfully resolves the issue. Environment: macOS 26.4.1 beta Xcode 26.4.1 beta Apple Silicon (ARM64) Flutter 3.41.9 Flutter issue: https://github.com/flutter/flutter/issues/186372 Apple Feedback Assistant report: FB22756923 Interested to know whether other developers on Xcode 26 beta are seeing similar stricter codesigning validation behavior.
Replies
1
Boosts
0
Views
66
Activity
2d
IAP Issue
Hi, Can someone help me with this issue I'm having with my app's IAP functionality? When you click on the unlock Premium button on the pop-up window, it should trigger the purchase action. However, there is an error when a user clicks on the button; this error appears as " Product Not Found." Please check App Store Connect Configuration". Has anyone faced this issue before, and how was it resolved? My backend code is right, and the IAP configuration in App Store Connect is right and approved, including the Agreement.
Replies
1
Boosts
0
Views
47
Activity
2d
Problem with the $99 payment.
Hello everyone: I paid the $99 requested to publish an app on Saturday around 3 PM (Paris time). They asked me for my French ID card shortly after, around 5 PM (Paris time). I sent it around 8 PM (Paris time), but I haven't heard back since. I emailed support around 10 AM (Paris time). Still no response. Can you help me?
Replies
1
Boosts
0
Views
27
Activity
2d
TestFlight install fails with BETA_CONTRACT_MISSING although all agreements are active
Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?
Replies
0
Boosts
0
Views
25
Activity
2d