Overview

Hi Team,   We were using the API, ' https://itunes.apple.com/search?entity=tvSoftware&term=digital+signa&limit=10&country=US' for searching and fetching apple TV applications within our product. But we found that the API response is null currently. When going through iTunes Search API: Constructing Searches, we found that 'tvSoftware' is no longer an entity.   Could you please let me know what's the 'entity' value that we need to use for fetching Apple TV applications?

Hi, I’m trying to understand the availability of previousOriginalTransactionId in App Store Server Notifications. According to Apple documentation, the field exists here: https://developer.apple.com/documentation/appstoreservernotifications/previousoriginaltransactionid And the App Store Server Notifications changelog indicates it was added in March 2025: https://developer.apple.com/documentation/appstoreservernotifications/app-store-server-notifications-changelog However, I cannot find this field in practice. What I checked I’m using the Java App Store Server Library version 5.1.1 (latest on Maven Central). JWSTransactionDecodedPayload does not expose a property/getter for previousOriginalTransactionId. Example: JWSTransactionDecodedPayload payload = verifier.verifyAndDecodeTransaction(signedTransaction); There does not appear to be something like: payload.getPreviousOriginalTransactionId() I initially assumed this was an SDK lag issue, so I decoded the raw JWS payload JSON manually. However, I also do not see previousOriginalTransactionId in the decoded payload. Questions Is previousOriginalTransactionId only included for specific transaction/subscription migration scenarios? Has anyone actually observed this field in production or sandbox payloads? Is the Java SDK simply behind, or is the field conditionally emitted and I’m testing the wrong flow? Environment: App Store Server Library Java: 5.1.1 Dependency source: Maven Central Class: JWSTransactionDecodedPayload Verified by inspecting decoded raw JWS payload as well

tle: New account — all notarization submissions stuck In Progress 26+ hours Hi, I recently enrolled in the Apple Developer Program and all my notarization submissions have been stuck "In Progress" for over 26 hours with no resolution. Team ID: 799833449H Submission IDs: bb31ba38-9ff4-416d-b6ea-8ad88b84a2be (26+ hours) 8fdd039d-3db4-4e96-8111-37dba9d4afd2 (25+ hours) 685cba55-aacd-4a05-8086-707a6b88e138 (23+ hours) Binary is a universal macOS binary, codesign verifies cleanly with hardened runtime. notarytool log returns "not yet available" for all. Is this the in-depth analysis path for new accounts? Any ETA or action needed from my side?

Hi everyone, I'm developing an iOS app using Swift (Foundation, Network, and Combine) that communicates via TCP with a weighing scale. The scale uses an internal ESP32 module acting as a Wi-Fi Access Point (no internet access) specifically for data transmission. The app connects to this network and opens a socket to receive weight data and send command strings. I’m currently facing two main issues: Socket Management: The socket isn't closing properly. Occasionally, the app opens multiple simultaneous connections instead of maintaining a single one. Since the ESP32 has a client limit, these ghost connections eventually hang the communication module. Invalid Outbound Data: The connection drops frequently because the scale receives invalid strings from the app. My logs show strange character sequences (like "gggggggggfdhj" or "vfgdddddddddddtty") being sent involuntarily. I haven't programmed these strings, and they cause the scale to terminate the session due to protocol violations. How can I ensure proper socket closure and prevent these random data packets? Additionally, a technical question: Is it possible to keep this TCP connection active in the background indefinitely on iOS while the user interacts with other apps?

It has been 20 days since we applied for Family Controls (Distribution) permission, but the status still shows as Submitted. Is there any way to expedite the review process?

I’m using Swift Charts to show a scatter plot with multiple PointMarks. When the user selects a point, I attach an annotation to the selected PointMark to show a label like Strike 1. I expected the annotation to render above all chart marks, but in practice nearby PointMarks can be drawn over the annotation text/background. Simplified example: Chart { ForEach(points.filter { !$0.isSelected }) { point in PointMark( x: .value("X", point.x), y: .value("Y", point.y) ) .foregroundStyle(.black) } if let selectedPoint { PointMark( x: .value("X", selectedPoint.x), y: .value("Y", selectedPoint.y) ) .foregroundStyle(.orange) .annotation(position: .top) { Text("Strike \(selectedPoint.number)") .padding(.horizontal, 8) .padding(.vertical, 4) .background(Capsule().fill(.orange.opacity(0.15))) } } } screenshots

Hi all, I’m looking for some guidance regarding my app review status. About a week ago, I submitted my app for review on the App Store. The review team responded asking for some declarations and a few changes in the app. I addressed all the requested changes and resubmitted the app promptly. However, it has now been more than a week since the resubmission, and I haven’t received any further updates or feedback from the review team. The status still appears unchanged, and there has been no communication. I understand that review times can vary, but I wanted to check: Is this delay normal after a resubmission? Is there anything I should do from my side (e.g., follow-up, resubmit again, contact support)? Has anyone else experienced similar delays recently? my app name is Darenite Any insights or suggestions would be really helpful. Thanks in advance!

Dear Apple Team, My app was rejected during App Store review on the basis that it must provide the same functionality as the web version. I respectfully asked the reviewer to clarify where this requirement is stated, as I could not find it in the App Store Review Guidelines. However, my question was not addressed, and the app remains in Rejected status. Could you please advise on the best next steps and the expected timeline for resolution? Thank you.

May 4, i subscribed to apple developer program then they ask me for 99$ , i paid and got confirmation on main but then go no replay and no support replay to main and nothing at all happens what should i do now ?

My Apple Developer account was recently terminated, and I received an email stating that the reason was section 3.2(f) of the Apple Developer Program License Agreement. However, I have not changed anything recently in our apps, business model, or developer activity, and I genuinely do not understand the reason behind this termination. I have always tried to follow Apple’s guidelines carefully and act in good faith. This termination has severely impacted my work and users, and I am urgently requesting clarification regarding what exactly triggered this action. If someone from Apple or the App Review / Developer Relations team could please contact me or review the case again, I would greatly appreciate it. Thank you.

I tried every possible but it just won't work on my device. The program runs well on the simulator by the way

I've noticed an inconsistency between how the SF Symbols app and SwiftUI code handle variable color for symbols that use the "Draw" animation mode. Background SF Symbols that support variable color fall into two categories based on their animation preference: Symbols suited for .symbolVariableValueMode(.color) — layers are highlighted/dimmed by color opacity Symbols suited for .symbolVariableValueMode(.draw) — layers are progressively drawn/erased When .symbolVariableValueMode is not set (i.e., the default mode), I expected the system to automatically choose the appropriate mode for each symbol. What SF Symbols app shows In the SF Symbols app, selecting thermometer.high, enabling variable color, and setting the value to 0.5 with "Default" mode selected produces a correct and expected result — the symbol renders identically to the explicit "Draw" mode. What SwiftUI code does In code, when symbolVariableValueMode is not specified (default), symbols from the "Draw" category receive no visual effect — they appear static, as if variable value is ignored entirely. // This works correctly Image(systemName: "thermometer.high") .symbolVariableValue(0.5) .symbolVariableValueMode(.draw) // This shows NO effect — expected to fall back to .draw, but doesn't Image(systemName: "thermometer.high") .symbolVariableValue(0.5) // no .symbolVariableValueMode set Symbols in the "Color" category appear unaffected — they render correctly with or without an explicit mode. Question / Bug? Is this a known limitation, or is the default mode in code intentionally different from what the SF Symbols app previews? If so, is there a programmatic way to query which symbolVariableValueMode a given symbol prefers at runtime, so I can set it explicitly without hardcoding per-symbol logic?

Dear App Review Team, Our app – Apple ID 6757288398 has been stuck in the “In Review” status for over 3 daysNormally, reviews ends typically in 48 hours(i requested expedite review) it seems unusually delayed. Could you please clarify: • Is there a specific reason for this extended hold? • Is any action required from our side? • When can we expect the review to proceed? Thank you very much for your time and assistance.

Hello, I am developing an macOS app and planning to implement a cross-platform save feature. I have two questions regarding the App Store Review Guidelines and Game Center integration. 1. Requiring Game Center exclusively for an optional "Cross-Save" feature (Guideline 5.1.1 & HIG) in macOS To comply with Guideline 5.1.1(v), we do not force users to sign in to Game Center upon app launch. Users can fully access the core features, play locally, and even use standard iCloud sync without any Game Center authentication. However, to use the specific, optional "Cross-Save" feature (which syncs data across different platforms via our proprietary backend), we intend to require Game Center login. Question: Is it acceptable to prompt for and require Game Center authentication only when the user explicitly tries to enable this specific cross-save feature? 2. Associating Game Center IDs with a proprietary backend account (Guidelines 4.5.3 & 4.5.5) To facilitate cross-progression, our backend server plans to authenticate the user using Game Center's identity verification signature via fetchItems(forIdentityVerificationSignature:). Once authenticated, we want to link the user's Game Center ID (specifically, teamPlayerID or gamePlayerID) to our proprietary service account in our own database. Question: Guidelines 4.5.3 and 4.5.5 state that we should not share Player IDs with "any third party." Does storing and linking the Game Center ID to our own backend server account (strictly to manage our game's cross-saves) fall under this "third party" restriction, or is our proprietary backend considered a permitted, first-party use? I want to ensure our implementation fully complies with Apple's privacy and user experience standards. Any insights would be greatly appreciated. Thank you.

My app is stuck in the "in review" stage for over 3days. . Did my review get stuck or lost or something? Is there anyway to get any clarity on this?

Hi. I want to know what's the difference between VirtualEnvironmentProbeComponent and ImageBasedLightComponent? It seems they both can achieve the same light and reflection effect of environment.

Hi Apple Support, I've been unable to send my apps for review for quite a while. Getting this error message: "Unable to Add for Review The items below are required to start the review process: To submit new apps or avoid potential payment blocks, add compliance information for Part XX of the Income Tax Act (ITA)." I've already added compliance information as requested, not sure how to resolve this. Case ID: 102880270773 Thank you

ARCamera.TrackingState questions: Did the threshold or sensitivity for transitioning ARCamera.TrackingState from .normal to .limited(.excessiveMotion) or .limited(.insufficientFeatures) change between iOS 26.3 and iOS 26.4? What does "ARWorldTrackingTechnique: resource constraints [33]" mean, and is it new in iOS 26.4? Does it correspond to a tracking state degradation? Is there a way for the client to detect or respond to ARKit entering a resource-constrained mode short of the full tracking state transition — for example, a lower-level notification or a flag on ARFrame — so that apps can take protective action without interpreting it as a full tracking failure? ARCamera.unprojectPoint questions: Did the behavior of ARCamera.unprojectPoint(_:ontoPlane:orientation:viewportSize:) change between iOS 26.3 and iOS 26.4 for near-parallel geometry? Specifically, on iOS 26.3 this method returns nil when the camera ray is nearly parallel to the target plane (denominator of the ray-plane intersection → 0 at ~90° of camera rotation). On iOS 26.4, with identical code and environment, it returns a large finite value instead — we observed z = −12.27m. Since the method's optional return type implies nil is the documented signal for no valid intersection, this reads as a behavioral regression rather than an intentional change. If returning the computed value for near-parallel geometry is now the intended behavior, is there a recommended way for the caller to guard against it? For example, should we check abs(dot(rayDirection, planeNormal)) against a threshold before calling, and if so, is there a documented epsilon Apple uses internally? Alternatively, is there a newer API we should prefer over unprojectPoint(:ontoPlane:) for this use case that handles degenerate geometry more gracefully — such as ARSession.raycast(:)? Are there any other ARKit API adjustments between OS 26.3 and 26.4? We are using the same codebase, but it behaves differently in between these 2 OS versions now. Thanks!

I'm hitting a kernel-side rejection on IOServiceOpen from a host app against my DEXT's IOUserService, before any code in my DEXT's NewUserClient runs. DEXT activation and USB matching succeed; only the user-client connection fails. What works DEXT activates and shows as [activated enabled] in systemextensionsctl list. DEXT matches IOUSBHostInterface for the target device and Start() runs to completion. Inside Start(), CopyInterface() returns successfully and CopyPipe() for the expected endpoints all succeed. Host app receives the matching notification for the DEXT's IOUserService and calls IOServiceOpen(service, mach_task_self(), 0, &connect). What fails IOServiceOpen returns kIOReturnError (0xE00002BC). My DEXT's NewUserClient override is never reached — verified by the absence of any breadcrumb log and by stepping through under lldb (no entry on the DEXT side). This reproduces both with: The original com.apple.developer.driverkit.userclient-access entitlement listing the host bundle ID. The dev fallback com.apple.developer.driverkit.allow-any-userclient-access = true on host + DEXT. (Background: the App ID portal has the bundle-ID list for userclient-access stored as a single newline-joined string instead of separate array entries — see Support Thread 822652 — so I've been using allow-any-userclient-access = true for now. The IOServiceOpen failure persists either way.) Diagnostics I can't get I'd like to confirm the kernel-side rejection reason, but DEXT os_log output is suppressed in Console and: sudo log config --process <dext-pid> --mode "level:debug" log: Unable to set mode for pid <dext-pid> I've tried by PID and by subsystem; both refuse. SIP is in its default state. Any pointer to the correct invocation (or a Configuration Profile to enable DriverKit verbose logging) would unblock me. Environment macOS 26.3.1 (build 25D2128) Xcode 26.3 (build 17C529) Host app: AppKit, sandboxed, Mac App Store distribution DEXT: matches IOUSBHostInterface on idVendor: 0x1452 (DNP) and (pending capability approval) 0x1343 (Citizen) Entitlements on host: com.apple.developer.driverkit, com.apple.developer.driverkit.userclient-access (or allow-any-userclient-access = true for dev) Entitlements on DEXT: com.apple.developer.driverkit, com.apple.developer.driverkit.transport.usb, com.apple.developer.driverkit.allow-any-userclient-access for dev Questions Is IOServiceOpen → kIOReturnError before NewUserClient always an entitlement/sandbox check failure, or are there other kernel-side reasons (matching score, IOService class hierarchy mismatch) that produce the same generic code? What's the correct way to enable DEXT os_log capture so I can see the rejection reason? Is there a known interaction between a malformed userclient-access array on the App ID (Forums Thread 822652) and the kernel's user-client authorization path that would persist even after switching to allow-any-userclient-access = true? Sample profiles, codesign output, and the exact matching dictionary available on request. Thanks.

Hi, I’m seeing WeatherKit fail on device with a JWT permission error even though the app appears to be signed correctly with the WeatherKit entitlement. Error: Failed to generate jwt token for: com.apple.weatherkit.authservice Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Setup verified: iOS physical device, tested after clean install/reboot Tested on more than one physical device Bundle ID: com.elilindenDinematch.Al-Outfits Team ID: FYGW4LHN42 App ID has WeatherKit capability enabled Fresh provisioning profile includes: application-identifier = FYGW4LHN42.com.elilindenDinematch.Al-Outfits com.apple.developer.team-identifier = FYGW4LHN42 com.apple.developer.weatherkit = true Signed app binary entitlements also include com.apple.developer.weatherkit = true codesign -dv confirms TeamIdentifier=FYGW4LHN42 Cleared DerivedData and regenerated/reinstalled with a fresh profile Toggled WeatherKit capability off/on in Developer portal and regenerated profile The failure occurs when calling: let weather = try await WeatherKit.WeatherService.shared.weather(for: location) The request takes a few seconds before failing, which makes it seem like the WeatherKit daemon is reaching Apple’s auth service but being rejected during JWT generation. Has anyone seen WeatherKit entitlement propagation get stuck server-side for a specific Team ID + Bundle ID? Is there anything else I can verify locally, or does this require Apple to inspect the WeatherKit auth service registration for this App ID?