Overview

Post

Replies

Boosts

Views

Activity

Unable to submit reinstatement request after Developer Program termination
Hello Apple Developer Support, My Apple Developer Program membership was terminated under Section 3.2(f), and I would like to petition the App Review Board for reinstatement. However, I am unable to access the Developer Support / reinstatement process. When I select “Get Started,” I am asked to sign in. After successfully signing in with the Apple Account associated with my developer membership, the page redirects and enters a login loop, so I cannot submit a request. My account currently appears as CLOSED in App Store Connect. Could Apple Developer Support please advise how I can submit my reinstatement petition, or assist with creating a support case for my terminated membership? Thank you.
1
0
377
1d
BlockStorageDeviceDriverKit grant confirmed by support but shows "No Requests" in the portal. How to resolve?
Hello! I am hoping a DTS engineer or someone who knows the Capability Requests portal can help, because I am stuck between a written support confirmation and what the portal actually shows. Background. We are building a native macOS iSCSI initiator for SOHO and home NAS use, developed over close to two years. A userspace daemon runs the iSCSI protocol and a DriverKit system extension presents the remote LUN as a block device. The code is essentially complete. Only the DriverKit extension cannot be signed, loaded and validated without the entitlement. We submitted request 32PC8MGU57 for two entitlements: com.apple.developer.driverkit.family.block-storage-device for the extension com.aviontex.iscsi.AviontexISCSI.AviontexInitiator com.apple.developer.driverkit.userclient-access for the app com.aviontex.iscsi.AviontexISCSI, scoped to the extension bundle id The problem. On June 25 Developer Support confirmed in writing that both entitlements were granted. The portal does not match that: Block Storage Device: No Requests: on both App IDs UserClient Access: Assigned: on the app SCSI Controller: Submitted: on the app So the one entitlement we actually need, Block Storage Device, shows as never requested, even though request 32PC8MGU57 covered it and support confirmed the grant. The case was escalated to the senior team on July 2 (case 102922935570). Follow-up emails since then have not received a response. Why Block Storage Device specifically Our initiator has no PCI or Thunderbolt bus and no DMA path, so SCSIControllerDriverKit does not fit. This is confirmed by DTS in thread 776020, where Kevin Elliott explains that SCSIControllerDriverKit passes data through fBufferIOVMAddr as a physical address with no mechanism to convert it into a VM address the dext can access. He also notes it cannot be used with any bus other than PCI or Thunderbolt. Block Storage Device is therefore the family we need. My questions: Am I reading the portal correctly: Block Storage Device not requested, UserClient Access assigned, SCSI Controller submitted? From here, what is the correct way to get Block Storage Device onto these two App IDs, with both the Development and the Distribution grant, since our public beta depends on Distribution? Should I submit a new request through the Capability Requests tab or does the escalated case handle it? Is there any way to get visibility on the escalated case, since email follow-ups are not being answered? A full technical justification is prepared and we are happy to share the source code. Any guidance would be appreciated. Thank you.
45
1
11k
1d
App Store "Individual" Account Setup for paid Apps
I have registered my (free) Apple developer account years ago and long before AppStore started. Now I upgraded to a paid account and want to provide in-app purchases for my apps. I don't find an option to set my apps to a price, except than "free". I have searched the internet and know that I have to sign some form but I can't find that form or any link to provide the required information to update an existing form. Has anybody an idea where I can look?
0
0
97
1d
Bug in Accelerate Lapack - Wrong eigenvectors
In the LAPACK interface of Accelerate (the default, without ACCELERATE_NEW_LAPACK), zheev with JOBZ='V', UPLO='U' returns eigenvectors that are neither orthonormal nor eigenvectors, while INFO=0. The eigenvalues are correct. zhegv with UPLO='U' fails the same way (tested with B = identity). It happens when: the matrix is complex Hermitian of order N >= 130 (N = 129 is correct, N = 130 already fails, N = 300 fails), and its last two or more rows and columns are exactly zero (one zero row is fine). Zero rows at the start or in the middle are fine. Banded and dense matrices both fail. On the same matrices the following are correct to rounding (1e-15): zheev and zhegv with UPLO='L', zheevd with UPLO='U', dsyev with UPLO='U' on real symmetric matrices of the same shape, zheev with UPLO='U' through the new LAPACK interface (-DACCELERATE_NEW_LAPACK). Since only the eigenvectors are wrong, and only above N=129 (presumably where zhetrd switches to its blocked code), the fault seems to be in the blocked Householder reduction or in the back-transformation (zhetrd/zlatrd or zungtr/zungql) of the legacy library, for columns that are zero. Asking LAPACK for the optimal LWORK (LWORK = -1 query) does not change the result. We found this in a physics code (Quanty, quanty.org), where a matrix of this shape arises naturally: a block tridiagonal (block Lanczos) matrix whose last block is padded with zeros after deflation. The wrong eigenvectors silently degraded results by 1e-4 relative, instead of 1e-15. STEPS TO REPRODUCE Save the attached zheev_upper_bug.c. clang -O2 zheev_upper_bug.c -o zheev_upper_bug -framework Accelerate ./zheev_upper_bug For comparison: clang -O2 -DACCELERATE_NEW_LAPACK zheev_upper_bug.c -o zheev_upper_bug_new -framework Accelerate && ./zheev_upper_bug_new The program builds a random Hermitian matrix (fixed seed, entries in [-0.5,0.5), bandwidth 11 or dense), zeroes its last NZERO rows and columns, calls zheev/zhegv/zheevd and prints max|V^H V - 1| and max|A V - V diag(W)|. EXPECTED RESULT Both numbers of order 1e-15 for every line, as with the new LAPACK interface. ACTUAL RESULT (legacy interface) zheev UPLO=U N=129 zero trailing rows=2 INFO=0 max|V^H V - 1| = 4.0e-15 max|A V - V W| = 4.4e-15 ok zheev UPLO=U N=130 zero trailing rows=2 INFO=0 max|V^H V - 1| = 9.8e-01 max|A V - V W| = 1.1e+00 <-- WRONG zheev UPLO=U N=130 zero trailing rows=1 INFO=0 max|V^H V - 1| = 4.7e-15 max|A V - V W| = 3.3e-15 ok zheev UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.1e+00 max|A V - V W| = 1.2e+00 <-- WRONG zheev UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 2.1e-01 max|A V - V W| = 2.2e+00 <-- WRONG zheev UPLO=U N=300 zero trailing rows=2 INFO=0 max|V^H V - 1| = 7.0e-01 max|A V - V W| = 1.5e+00 <-- WRONG zhegv UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.1e+00 max|A V - V W| = 1.2e+00 <-- WRONG the same matrices with UPLO = 'L' or zheevd: zheev UPLO=L N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 5.9e-15 max|A V - V W| = 3.6e-15 ok zhegv UPLO=L N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 4.4e-15 max|A V - V W| = 3.7e-15 ok zheevd UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.9e-15 max|A V - V W| = 1.4e-15 ok With -DACCELERATE_NEW_LAPACK every line is "ok" (1e-15). Code to reproduce the error: zheev_upper_bug.c.txt
1
0
87
1d
Xcode Cloud: All export archive steps fail with exit code 70 (Remote Mac + managed signing)
I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 Command exited with non-zero exit-code: 70 The same pattern repeats for ad-hoc and app-store distribution exports. What I've verified: The build itself compiles successfully (all modules compile, command executed successfully) No code changes were made that would affect signing The workflow is configured with automatic signing managed by Xcode Cloud Post-action is set to TestFlight External Testing Additional constraint — Remote Mac: I'm building on a Remote Mac, which adds complexity to code signing and keychain access. The Remote Mac environment has known limitations with certificate and provisioning profile management compared to a local Mac. This may be a contributing factor to the export failures. This appears to be an issue with how Xcode Cloud is handling the Apple Distribution and Apple Development signing certificates during the export phase, not a build compilation issue. Has anyone encountered this recently, or is there a known issue with Xcode Cloud's managed signing on Remote Mac environments? Any guidance on resolving exit code 70 during the export step would be greatly appreciated.
2
0
636
1d
Sanboxed Apps Reading Extended Security Information (ACL)
My custom filesystem kernel extension stores ACLs as an extended attribute, com.apple.system.Security. Sanboxed apps such as TextEdit, Pages, etc., running as a non-privileged process, fail to save modified contents when permissive ACLs are in use. Running them as a privileged process, does allow for file changes to be saved though. Non-sandboxed apps, such as VSCode, and command line programs are not susceptible to this behaviour. APFS, on the other hand, seems to handle ACLs as an ATTR_CMN_EXTENDED_SECURITY filesystem attribute, rather than as an EA. In this case, sandboxed apps have no trouble accessing the ACL data. I implemented a minimal PoC within my custom kext to verify this. I construct an ACL in memory allowing a given user to write,append,delete file contents, and return it that via vnop_getattr. This allows the file contents to be modified and saved by sandboxed apps. Can you please confirm if my findings are accurate and sandboxed apps fail to read the com.apple.system.Security EA by design? Also, Is it an accurate assumption, that ACLs should be handled either as an EA, or an ATTR_CMN_EXTENDED_SECURITY, but not both? Thanks.
13
0
929
1d
macOS 27.2 b2: Contacts app freezes for several seconds on every contact card
What happens Since installing macOS 27.2 b2 (didn't go through b1, might have been there already), the Contacts app has become almost unusable on my two Macs. Opening a contact or moving to the next one often freezes the app for 8 to 10 seconds, with the spinning wheel. It happens many times in a row while browsing the address book. It comes back no matter what I try: restarting, letting iCloud resync the contacts, deleting and recreating cards. Once, it seemed to go away for a couple of minutes upon restarting, but it returned. Both Macs share the same iCloud account (~690 contacts): a MacBook Pro M4 Pro and a Mac mini M4, both on 27.2 b2 (26B5091g). Reported as FB24928119. Technical details All 18 Contacts_*.spin reports show the main thread blocked in CNCDContactFetcher withLockedContext_fetchPosterData, waiting on a synchronous XPC call to com.apple.contacts.poster.api. That service is postersyncd, which syncs Contact Posters. The kernel kills postersyncd with exceeded mem limit: InactiveHard 20 MB (fatal) at 30–35 MB. launchd relaunches it every ~10 s: 74 kills in 26 h on one Mac, 54 in 24 h on the other. log stream --level debug shows the same sequence on every relaunch: START: Background cleanup → Potential cleanup for missingLocalContactIdentifiers → FetchingContacts → killed within the same second. The cleanup never finishes, so it restarts forever. The poster store (group.com.apple.contacts/ContactsMetadata) is ~85 MB, with blobs of up to 9 MB each. The memory limit stays InactiveHard even while Contacts is frontmost. Moving the poster store aside doesn't help: iCloud rebuilds it in ~25 s. Posters deleted from iOS or iCloud.com get a deletion date but are never purged. Question: has anyone else seen this on 27.2 b2? Is there a way to reset the Contact Posters data stored in iCloud?
4
1
358
1d
Paid Apple Developer Program membership suspended during compliance review — no response, apps removed (pending) — Case 102975269103
Hello, I am posting here because my Apple Developer Program membership is currently stuck in a state that I cannot resolve through the available self-service options, and I have not received a response to my compliance reply or Developer Support case. Timeline: • January 6, 2026 — I purchased my Apple Developer Program membership for a one-year term and received an Apple invoice. • September 22, 2026 — Apple Developer Relations notified me that my membership had been suspended pending a compliance review concerning possible digital-asset activities. • September 23, 2026 — I replied to Apple Developer Relations and provided the requested written confirmation that I do not provide digital-asset or cryptocurrency financial services. I also stated that I am enrolled as an individual and do not operate a registered company or other business entity. I have received no further response or request for additional documentation. My account is now in a contradictory state: • App Store Connect reports “Developer Program Membership Expired” and states that my apps have been removed from the App Store. • My membership was purchased on January 6, 2026 for a one-year term, so it should still be within its paid membership period. • developer.apple.com/account shows “Join the Apple Developer Program.” • If I attempt to enroll, Apple displays: “Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership.” Therefore, I cannot access my existing paid membership, restore Developer Program access, or enroll again. I contacted Apple Developer Support regarding this issue. Developer Support Case ID: 102975269103 The case remains unresolved, and phone support for this case currently shows: “Phone support is currently unavailable. Due to high call volumes, phone support is temporarily unavailable.” I am ready to provide immediately, through an appropriate secure Apple verification channel: • government-issued identification; • proof of address; • my Apple Developer Program purchase invoice; • information about my applications and their functionality; or • any other documentation required to complete the compliance review. I am not asking for a workaround or a new enrollment. I need the existing paid membership and compliance case to be reviewed by the appropriate Apple Developer Program Membership / Compliance team. Could an Apple Developer Relations representative or forum moderator please help route or escalate Case 102975269103 to the appropriate team, or advise whether there is any additional verification or documentation currently required from me? My applications have already been removed from the App Store while this remains unresolved, so the issue is actively affecting distribution. Thank you.
0
0
32
1d
Xcode Cloud reassigns one ciProduct between app targets with unique bundle IDs
I am seeing Xcode Cloud reuse and reassign a single ciProduct when onboarding multiple iOS app targets from one Xcode project. Each target has its own bundle ID, PBXNativeTarget, product reference, and shared scheme. Environment: Xcode 26.6 (17F113) macOS Tahoe 26.5.2 GitHub repository connected to Xcode Cloud Project: pilot-ios/Airtap.xcodeproj Targets / shared schemes: PocketPilot.ai DEV1 — ai.airtap.dev1 PocketPilot.ai DEV2 — ai.airtap.dev2 PocketPilot.ai DEV3 — ai.airtap.dev3 PocketPilot.ai DEV4 — ai.airtap.dev4 PocketPilot.ai QA1 — ai.airtap.qa1 PocketPilot.ai QA3 — ai.airtap.qa3 Every entry above is a separate PBXNativeTarget with a distinct productReference. Each shared scheme is stored under Airtap.xcodeproj/xcshareddata/xcschemes and builds its corresponding target. QA1 and QA3 were onboarded earlier and received independent Xcode Cloud products as expected. Reproduction: In Xcode, open Xcode Cloud Reports and choose Create Workflow. Select target PocketPilot.ai DEV1 and create an archive workflow using scheme PocketPilot.ai DEV1. DEV1 appears under the correct App Store Connect app. Create another workflow for target PocketPilot.ai DEV2 using scheme PocketPilot.ai DEV2. DEV1 disappears as a separate Xcode Cloud product. Both the DEV1 and DEV2 workflows now appear under the DEV2 App Store Connect app. The App Store Connect API confirms this is not only an Xcode UI or cache issue: Before DEV2 onboarding, ciProduct F048BF00-CECF-4926-84DB-D3474CB030A9 was related to bundle ID ai.airtap.dev1. After DEV2 onboarding, that same ciProduct ID became related to bundle ID ai.airtap.dev2. The product now contains both workflows: PocketPilot DEV1 Archive / scheme PocketPilot.ai DEV1 PocketPilot DEV2 Archive / scheme PocketPilot.ai DEV2 No build was started, and both workflows are currently disabled. Expected behavior: Because every target has a different bundle ID, Xcode should create a separate Xcode Cloud product for each target, as described in the Xcode Cloud onboarding documentation. Actual behavior: The newest onboarding changes the existing ciProduct-to-App Store Connect app relationship instead of creating a new ciProduct. This moves all earlier workflows to the newest app. The public App Store Connect API cannot repair this because it supports reading and deleting ciProducts, but not creating one; ciWorkflows can only be created under an existing ciProduct. I also encountered an Xcode crash while adding another product. The crash stack included XcodeCloudNavigableItemCoordinator.removeNavigableItem(for:) and IDENavigableItemCoordinator, which may be related to the product reassignment. I can provide the crash report in Feedback Assistant if needed. A recent forum thread reports the same high-level symptom: previously created workflows migrate to the newest app. In our case, the API relationship change above makes the backend reassignment directly observable. Is this a current Xcode Cloud onboarding/backend regression? Is there a supported workaround, or can Apple Support create or restore separate ciProducts for these bundle IDs?
3
0
366
1d
Apple Developer enrollment paid, but account now shows “Not Eligible”
Title: Apple Developer enrollment paid, but account now shows “Not Eligible” Hello, I recently enrolled in the Apple Developer Program using my Apple Account. I completed the enrollment process and paid the membership fee using Apple Pay. The payment was successfully charged, and during the enrollment process I was told that I would receive an email shortly regarding the enrollment. However, I never received that email. When I now log in to my Apple Developer account, it says that my account is not eligible for the Apple Developer Program. The membership fee has already been charged, so I would like to understand what happened to my enrollment and whether the payment can be associated with my application. Could someone please advise me on what I should do next or how I can have the enrollment and payment reviewed? Thank you.
7
2
711
1d
ios27 ARSCNViewDelegate EXC_BAD_ACCESS (code=2, address=0x16f74ffb0)
Hi, I understand Scenekit is deprecated in ios27, but expectation is that it should continue working in ios27 and not anymore maintained. With ios27 , when we attempt to set self.delegate in an ARSCNViewDelegate we receive a crash. Is there any workaround to have that fixed until we have time to move away from Scenekit? Can this be part of a fix in ios27 considering we should have sometime to migrate out production apps or that won't go through? Thank you.
2
0
1.4k
1d
FALSE SPAM CLAIM: Spam Flag After Apple Confirmed Our App Was NOT Spam
We need Apple to urgently remove the spam flag on our app. This is not a request for another generic explanation of the rejection. We previously had a Webex meeting with Ewelina from Apple, during which we explained the app, its purpose, and the changes made in response to the prior rejection. We were explicitly told that our app is not spam, (and was never a spam) that the issue would be addressed, and that we could confidently resubmit the app. We relied on that assurance and resubmitted. Yet we received the same spam rejection again. This is causing immediate and substantial financial harm. We are already paying commitments to Plaid and Checkbook, fees to other providers, and salaries to employees who cannot perform the work they were hired to do while our app remains blocked. These costs continue every day without a launch, and our company is facing significant financial distress. We have had to cancel our launch event three times. The third cancellation followed this latest rejection, after Apple told us we could confidently resubmit. We made financial and operational decisions based on that guidance. Please urgently escalate this to someone who can review the Webex meeting with Ewelina, remove the spam designation, and ensure our app is not rejected again on the same basis Apple already told us did not apply. We need a concrete resolution now. We cannot keep paying providers and employees, cancelling launch plans, and absorbing losses because the same flag continues to be applied. If anyone here has experienced the same situation or knows how to get this escalated to someone who can resolve it, we would be extremely grateful for your help.
0
0
71
1d
iPadOS 27.2 Beta — Display Zoom "Larger Text" spacebar bug fixed?
Hi everyone! Could anyone testing iPadOS 27.2 Beta 2 on an iPad please check a Display Zoom keyboard bug for me? When setting Display Zoom to Larger Text (Settings -> Display & Brightness -> Display Zoom), the spacebar becomes extremely small and squeezed between the language/layout switching keys. Just to add — this applies to both Developer Beta 2 and Public Beta . Thanks to anyone who can test this! Is this UI bug fixed in Beta 2? Thanks!
0
0
45
1d
Title: EAS iOS build fails with “iTunes service key is empty” on Windows
Hello, I’m trying to create an iOS TestFlight build for an Expo/EAS app on Windows. The project is configured with: Expo SDK 57 EAS CLI 24.1.0 iOS bundle ID: com.i3radleyy.flooriq Apple Developer Program: active individual membership Apple Team ID: R7GLN64JYP The Bundle ID is registered in Apple Developer The app record exists in App Store Connect I am the Account Holder The Expo configuration command succeeds and reports the correct bundle ID. EAS project initialisation also succeeds. However, when running the production build, Apple authentication fails after the Apple ID and password are accepted: Authentication with Apple Developer Portal failed! Failed to set up credentials. iTunes service key is empty Error: build command failed. I have also tried: EAS_NO_VCS=1 EXPO_NO_KEYCHAIN=1 Git is not being used, and the project is being built from the correct app directory. The Apple Developer account and App Store Connect pages are accessible in the browser, and the Bundle ID is registered. Is this a known EAS/Apple authentication issue on Windows? Is there a recommended way to provide the Apple signing credentials or use an App Store Connect API key so that EAS can create the iOS distribution certificate and provisioning profile? Thank you.
10
5
1.7k
1d
URLSession fails with -1009 on physical iPhone 16 Pro Max running iOS 27 beta, works in Simulator
I’m building a SwiftUI app that fetches public JSON data using URLSession.shared. The request works correctly in the iPhone 17 Pro Max Simulator, but fails on my physical iPhone 16 Pro Max running iOS 27 beta. Endpoint: https://api.jolpi.ca/ergast/f1/2026/driverstandings.json?limit=100 Error: NSURLErrorDomain Code=-1009 “The Internet connection appears to be offline.” NWPath: unsatisfied (Denied over Wi-Fi interface) Resolved 0 endpoints in 1ms The device can access the endpoint through Safari, and the same request works in Simulator. VPN, cellular permissions, Wi-Fi changes, and ATS settings have been checked. Could this be an iOS 27 beta networking regression affecting URLSession on physical devices? Are there recommended workarounds or diagnostics?
1
0
559
1d
27-Day Nightmare: Expedited Review Fails to Trigger. Is My Account Bugged? Need Human Support.
Hi everyone, I am experiencing a severe system delay and I am wondering if anyone else has faced this, or if an Apple engineer can check my account for a backend glitch. My timeline: It took 17 days just for my individual Apple Developer enrollment to be approved. My first app, has now been stuck on "Waiting for Review" for 10 days. I was officially granted an "Expedited Review" by the support team (Cases 102974693297 and 102976576467), and an agent explicitly told me it would begin "shortly." However, nothing has changed, and the standard support channel only replies with identical automated templates. Given the unusual 17-day initial enrollment delay, I strongly suspect my developer account might have a hidden hold or backend technical bug preventing the App Store Connect system from moving the app's status to "In Review." Has anyone experienced a granted expedited review completely failing to trigger? How can I get a human technical specialist to check my account backend for blockers? Thank you in advance for any guidance.
5
1
335
1d
AVSpeechSynthesizer Enhanced voices produce silent audio in sandboxed Mac Catalyst app
I have reproduced an issue with AVSpeechSynthesizer on macOS 26.6.2 (25G83) using a minimal Mac Catalyst application. Environment macOS 26.6.2 (25G83) Apple Silicon Xcode 26.x Mac Catalyst AVSpeechSynthesizer Enhanced voice: com.apple.voice.enhanced.en-GB.Daniel The problem is specifically related to App Sandbox. Reproduction I created a completely new minimal Mac Catalyst application. With App Sandbox disabled: let synthesizer = AVSpeechSynthesizer() let utterance = AVSpeechUtterance(string: "Hello, this is a test.") utterance.voice = AVSpeechSynthesisVoice(identifier: "com.apple.voice.enhanced.en-GB.Daniel") synthesizer.speak(utterance) The Enhanced voice works normally. With App Sandbox enabled, with no other sandbox capabilities enabled, the same code no longer produces audible speech.
3
0
814
1d
New app review stuck
This has happened before with a new app I build that involved subscriptions and it got stuck in a blackhole and i believe it could be a glitch on apples review system. I submitted a new app, the subscription wasnt fully included for review, the reviewer replied to me asking some questions and thiis is when i noticed the sub was not fully linked. So i linked it and now im worried its fallen into the same black hole as before as there has been no movement. Its just sitting waiting to be reviewed. Which is totally fine if the team are just backlogged but i dont want to wait a month or so before knowing this for sure as i cant afford that amount of wasted time. Its related to my WeatherLens app
1
0
95
1d
App stuck in "Waiting for Review" for 12 days while other updates from the same account are approved normally
App ID: 6790321094 Submission ID: 883d7004-33a3-4fd7-b229-756a15b51cb9 Submitted: August 4, 2026 My app has been in "Waiting for Review" for 12 days with no change in status. In the same period, five other updates from the same developer account went through review normally, within the usual timeframe. So this does not appear to be a general queue backlog or an account-level issue. An expedited review request was submitted and had no effect. The previous version of this update was rejected under Guideline 4.3, and the issue behind that rejection has been fully addressed in this build. Details are in the Review Notes. There is no active thread in Resolution Center, so I have no way to contact the review team about this submission directly. Could someone confirm whether this submission is queued correctly or whether it is stuck? Any guidance would be appreciated.
3
2
436
1d
Back button briefly jumps to the leading edge of the navigation bar during interactive pop from a screen with a hidden navigation bar (iPhone Duo)
On the iPhone Duo's narrow display, the navigation bar's back button sits in the trailing column below the status bar. During an interactive swipe-back from a screen whose navigation bar is hidden to a screen whose navigation bar is visible, the back button briefly renders in the leading (top-left) position of the bar for one or more frames. In those same frames the trailing-column button is blank. It then jumps back to the trailing column. The result is a visible flicker. Steps to reproduce: Open the attached code in Xcode 27.1 and run it on the iPhone Duo simulator (iOS 27.1), using the narrow display in portrait. Tap "Push". This pushes a screen with a visible navigation bar. Tap "Push without header". This pushes a screen that hides the navigation bar. Slowly swipe back from the leading edge to return to the previous screen. Expected: the back button of the revealed navigation bar stays in the trailing column for the whole transition, the same as with a programmatic pop. Actual: for one or more frames during the gesture, the back button renders at the leading edge of the navigation bar (top-left), and the trailing column is blank. Then it returns to the trailing column. Repro: import UIKit @main final class AppDelegate: UIResponder, UIApplicationDelegate {} final class SceneDelegate: UIResponder, UIWindowSceneDelegate { var window: UIWindow? func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options: UIScene.ConnectionOptions) { guard let windowScene = scene as? UIWindowScene else { return } let window = UIWindow(windowScene: windowScene) let nav = SwipeableNavigationController(rootViewController: ScreenVC(title: "header 0", showsHeader: true)) window.rootViewController = nav window.makeKeyAndVisible() self.window = window // Auto sequence when launched with `-auto YES`: push header, push no header, pop. guard UserDefaults.standard.bool(forKey: "auto") else { return } DispatchQueue.main.asyncAfter(deadline: .now() + 1.5) { nav.pushViewController(ScreenVC(title: "header 0", showsHeader: true), animated: true) } DispatchQueue.main.asyncAfter(deadline: .now() + 3.0) { nav.pushViewController(ScreenVC(title: "no header", showsHeader: false), animated: true) } DispatchQueue.main.asyncAfter(deadline: .now() + 4.5) { nav.popViewController(animated: true) } } } final class ScreenVC: UIViewController { private let showsHeader: Bool init(title: String, showsHeader: Bool) { self.showsHeader = showsHeader super.init(nibName: nil, bundle: nil) self.title = title } required init?(coder: NSCoder) { fatalError() } override func viewWillAppear(_ animated: Bool) { super.viewWillAppear(animated) navigationController?.setNavigationBarHidden(!showsHeader, animated: animated) } override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .systemGroupedBackground let push = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Push") { [weak self] _ in self?.navigationController?.pushViewController(ScreenVC(title: "header 0", showsHeader: true), animated: true) }) let pushNoHeader = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Push without header") { [weak self] _ in self?.navigationController?.pushViewController(ScreenVC(title: "no header", showsHeader: false), animated: true) }) let back = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Go back") { [weak self] _ in self?.navigationController?.popViewController(animated: true) }) let stack = UIStackView(arrangedSubviews: [push, pushNoHeader, back]) stack.axis = .vertical stack.translatesAutoresizingMaskIntoConstraints = false view.addSubview(stack) NSLayoutConstraint.activate([ stack.topAnchor.constraint(equalTo: view.safeAreaLayoutGuide.topAnchor, constant: 10), stack.centerXAnchor.constraint(equalTo: view.centerXAnchor), ]) } } final class SwipeableNavigationController: UINavigationController, UIGestureRecognizerDelegate { override func viewDidLoad() { super.viewDidLoad() interactivePopGestureRecognizer?.delegate = self if #available(iOS 26.0, *) { interactiveContentPopGestureRecognizer?.delegate = self } } func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool { viewControllers.count > 1 } } Thank you in advance!
1
1
210
1d
Unable to submit reinstatement request after Developer Program termination
Hello Apple Developer Support, My Apple Developer Program membership was terminated under Section 3.2(f), and I would like to petition the App Review Board for reinstatement. However, I am unable to access the Developer Support / reinstatement process. When I select “Get Started,” I am asked to sign in. After successfully signing in with the Apple Account associated with my developer membership, the page redirects and enters a login loop, so I cannot submit a request. My account currently appears as CLOSED in App Store Connect. Could Apple Developer Support please advise how I can submit my reinstatement petition, or assist with creating a support case for my terminated membership? Thank you.
Replies
1
Boosts
0
Views
377
Activity
1d
BlockStorageDeviceDriverKit grant confirmed by support but shows "No Requests" in the portal. How to resolve?
Hello! I am hoping a DTS engineer or someone who knows the Capability Requests portal can help, because I am stuck between a written support confirmation and what the portal actually shows. Background. We are building a native macOS iSCSI initiator for SOHO and home NAS use, developed over close to two years. A userspace daemon runs the iSCSI protocol and a DriverKit system extension presents the remote LUN as a block device. The code is essentially complete. Only the DriverKit extension cannot be signed, loaded and validated without the entitlement. We submitted request 32PC8MGU57 for two entitlements: com.apple.developer.driverkit.family.block-storage-device for the extension com.aviontex.iscsi.AviontexISCSI.AviontexInitiator com.apple.developer.driverkit.userclient-access for the app com.aviontex.iscsi.AviontexISCSI, scoped to the extension bundle id The problem. On June 25 Developer Support confirmed in writing that both entitlements were granted. The portal does not match that: Block Storage Device: No Requests: on both App IDs UserClient Access: Assigned: on the app SCSI Controller: Submitted: on the app So the one entitlement we actually need, Block Storage Device, shows as never requested, even though request 32PC8MGU57 covered it and support confirmed the grant. The case was escalated to the senior team on July 2 (case 102922935570). Follow-up emails since then have not received a response. Why Block Storage Device specifically Our initiator has no PCI or Thunderbolt bus and no DMA path, so SCSIControllerDriverKit does not fit. This is confirmed by DTS in thread 776020, where Kevin Elliott explains that SCSIControllerDriverKit passes data through fBufferIOVMAddr as a physical address with no mechanism to convert it into a VM address the dext can access. He also notes it cannot be used with any bus other than PCI or Thunderbolt. Block Storage Device is therefore the family we need. My questions: Am I reading the portal correctly: Block Storage Device not requested, UserClient Access assigned, SCSI Controller submitted? From here, what is the correct way to get Block Storage Device onto these two App IDs, with both the Development and the Distribution grant, since our public beta depends on Distribution? Should I submit a new request through the Capability Requests tab or does the escalated case handle it? Is there any way to get visibility on the escalated case, since email follow-ups are not being answered? A full technical justification is prepared and we are happy to share the source code. Any guidance would be appreciated. Thank you.
Replies
45
Boosts
1
Views
11k
Activity
1d
App Store "Individual" Account Setup for paid Apps
I have registered my (free) Apple developer account years ago and long before AppStore started. Now I upgraded to a paid account and want to provide in-app purchases for my apps. I don't find an option to set my apps to a price, except than "free". I have searched the internet and know that I have to sign some form but I can't find that form or any link to provide the required information to update an existing form. Has anybody an idea where I can look?
Replies
0
Boosts
0
Views
97
Activity
1d
Bug in Accelerate Lapack - Wrong eigenvectors
In the LAPACK interface of Accelerate (the default, without ACCELERATE_NEW_LAPACK), zheev with JOBZ='V', UPLO='U' returns eigenvectors that are neither orthonormal nor eigenvectors, while INFO=0. The eigenvalues are correct. zhegv with UPLO='U' fails the same way (tested with B = identity). It happens when: the matrix is complex Hermitian of order N >= 130 (N = 129 is correct, N = 130 already fails, N = 300 fails), and its last two or more rows and columns are exactly zero (one zero row is fine). Zero rows at the start or in the middle are fine. Banded and dense matrices both fail. On the same matrices the following are correct to rounding (1e-15): zheev and zhegv with UPLO='L', zheevd with UPLO='U', dsyev with UPLO='U' on real symmetric matrices of the same shape, zheev with UPLO='U' through the new LAPACK interface (-DACCELERATE_NEW_LAPACK). Since only the eigenvectors are wrong, and only above N=129 (presumably where zhetrd switches to its blocked code), the fault seems to be in the blocked Householder reduction or in the back-transformation (zhetrd/zlatrd or zungtr/zungql) of the legacy library, for columns that are zero. Asking LAPACK for the optimal LWORK (LWORK = -1 query) does not change the result. We found this in a physics code (Quanty, quanty.org), where a matrix of this shape arises naturally: a block tridiagonal (block Lanczos) matrix whose last block is padded with zeros after deflation. The wrong eigenvectors silently degraded results by 1e-4 relative, instead of 1e-15. STEPS TO REPRODUCE Save the attached zheev_upper_bug.c. clang -O2 zheev_upper_bug.c -o zheev_upper_bug -framework Accelerate ./zheev_upper_bug For comparison: clang -O2 -DACCELERATE_NEW_LAPACK zheev_upper_bug.c -o zheev_upper_bug_new -framework Accelerate && ./zheev_upper_bug_new The program builds a random Hermitian matrix (fixed seed, entries in [-0.5,0.5), bandwidth 11 or dense), zeroes its last NZERO rows and columns, calls zheev/zhegv/zheevd and prints max|V^H V - 1| and max|A V - V diag(W)|. EXPECTED RESULT Both numbers of order 1e-15 for every line, as with the new LAPACK interface. ACTUAL RESULT (legacy interface) zheev UPLO=U N=129 zero trailing rows=2 INFO=0 max|V^H V - 1| = 4.0e-15 max|A V - V W| = 4.4e-15 ok zheev UPLO=U N=130 zero trailing rows=2 INFO=0 max|V^H V - 1| = 9.8e-01 max|A V - V W| = 1.1e+00 <-- WRONG zheev UPLO=U N=130 zero trailing rows=1 INFO=0 max|V^H V - 1| = 4.7e-15 max|A V - V W| = 3.3e-15 ok zheev UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.1e+00 max|A V - V W| = 1.2e+00 <-- WRONG zheev UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 2.1e-01 max|A V - V W| = 2.2e+00 <-- WRONG zheev UPLO=U N=300 zero trailing rows=2 INFO=0 max|V^H V - 1| = 7.0e-01 max|A V - V W| = 1.5e+00 <-- WRONG zhegv UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.1e+00 max|A V - V W| = 1.2e+00 <-- WRONG the same matrices with UPLO = 'L' or zheevd: zheev UPLO=L N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 5.9e-15 max|A V - V W| = 3.6e-15 ok zhegv UPLO=L N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 4.4e-15 max|A V - V W| = 3.7e-15 ok zheevd UPLO=U N=138 zero trailing rows=5 INFO=0 max|V^H V - 1| = 1.9e-15 max|A V - V W| = 1.4e-15 ok With -DACCELERATE_NEW_LAPACK every line is "ok" (1e-15). Code to reproduce the error: zheev_upper_bug.c.txt
Replies
1
Boosts
0
Views
87
Activity
1d
Xcode Cloud: All export archive steps fail with exit code 70 (Remote Mac + managed signing)
I'm experiencing a persistent issue with Xcode Cloud where my iOS app (Spellboard) builds and archives successfully, but all three export steps fail with exit code 70: Export archive for ad-hoc distribution — exit code 70 Export archive for development distribution — exit code 70 Export archive for app-store distribution — exit code 70 Environment: Xcode Cloud Build 45, branch: main Project: Spellboard.xcodeproj Team: EinsteinAI Target: Any iOS Device (arm64) Automatic code signing (managed by Xcode Cloud) Building on a Remote Mac (additional code signing constraints) Error details from logs: The xcodebuild -exportArchive command fails during the signing phase. For example, the development distribution step shows: xcodebuild -exportArchive -archivePath /Volumes/workspace/tmp/ec4c2b30-ebd1-435f-8d8f-621326235df1.xcarchive -exportPath /Volumes/workspace/developmentexport -exportOptionsPlist /Volumes/workspace/ci/development-exportoptions.plist -DVTProvisioningIsManaged=YES -IDEDistributionLogDirectory=/Volumes/workspace/tmp/development-export-archive-logs -DVTSkipCertificateValidityCheck=YES -DVTServicesLogLevel=3 Command exited with non-zero exit-code: 70 The same pattern repeats for ad-hoc and app-store distribution exports. What I've verified: The build itself compiles successfully (all modules compile, command executed successfully) No code changes were made that would affect signing The workflow is configured with automatic signing managed by Xcode Cloud Post-action is set to TestFlight External Testing Additional constraint — Remote Mac: I'm building on a Remote Mac, which adds complexity to code signing and keychain access. The Remote Mac environment has known limitations with certificate and provisioning profile management compared to a local Mac. This may be a contributing factor to the export failures. This appears to be an issue with how Xcode Cloud is handling the Apple Distribution and Apple Development signing certificates during the export phase, not a build compilation issue. Has anyone encountered this recently, or is there a known issue with Xcode Cloud's managed signing on Remote Mac environments? Any guidance on resolving exit code 70 during the export step would be greatly appreciated.
Replies
2
Boosts
0
Views
636
Activity
1d
Sanboxed Apps Reading Extended Security Information (ACL)
My custom filesystem kernel extension stores ACLs as an extended attribute, com.apple.system.Security. Sanboxed apps such as TextEdit, Pages, etc., running as a non-privileged process, fail to save modified contents when permissive ACLs are in use. Running them as a privileged process, does allow for file changes to be saved though. Non-sandboxed apps, such as VSCode, and command line programs are not susceptible to this behaviour. APFS, on the other hand, seems to handle ACLs as an ATTR_CMN_EXTENDED_SECURITY filesystem attribute, rather than as an EA. In this case, sandboxed apps have no trouble accessing the ACL data. I implemented a minimal PoC within my custom kext to verify this. I construct an ACL in memory allowing a given user to write,append,delete file contents, and return it that via vnop_getattr. This allows the file contents to be modified and saved by sandboxed apps. Can you please confirm if my findings are accurate and sandboxed apps fail to read the com.apple.system.Security EA by design? Also, Is it an accurate assumption, that ACLs should be handled either as an EA, or an ATTR_CMN_EXTENDED_SECURITY, but not both? Thanks.
Replies
13
Boosts
0
Views
929
Activity
1d
macOS 27.2 b2: Contacts app freezes for several seconds on every contact card
What happens Since installing macOS 27.2 b2 (didn't go through b1, might have been there already), the Contacts app has become almost unusable on my two Macs. Opening a contact or moving to the next one often freezes the app for 8 to 10 seconds, with the spinning wheel. It happens many times in a row while browsing the address book. It comes back no matter what I try: restarting, letting iCloud resync the contacts, deleting and recreating cards. Once, it seemed to go away for a couple of minutes upon restarting, but it returned. Both Macs share the same iCloud account (~690 contacts): a MacBook Pro M4 Pro and a Mac mini M4, both on 27.2 b2 (26B5091g). Reported as FB24928119. Technical details All 18 Contacts_*.spin reports show the main thread blocked in CNCDContactFetcher withLockedContext_fetchPosterData, waiting on a synchronous XPC call to com.apple.contacts.poster.api. That service is postersyncd, which syncs Contact Posters. The kernel kills postersyncd with exceeded mem limit: InactiveHard 20 MB (fatal) at 30–35 MB. launchd relaunches it every ~10 s: 74 kills in 26 h on one Mac, 54 in 24 h on the other. log stream --level debug shows the same sequence on every relaunch: START: Background cleanup → Potential cleanup for missingLocalContactIdentifiers → FetchingContacts → killed within the same second. The cleanup never finishes, so it restarts forever. The poster store (group.com.apple.contacts/ContactsMetadata) is ~85 MB, with blobs of up to 9 MB each. The memory limit stays InactiveHard even while Contacts is frontmost. Moving the poster store aside doesn't help: iCloud rebuilds it in ~25 s. Posters deleted from iOS or iCloud.com get a deletion date but are never purged. Question: has anyone else seen this on 27.2 b2? Is there a way to reset the Contact Posters data stored in iCloud?
Replies
4
Boosts
1
Views
358
Activity
1d
Paid Apple Developer Program membership suspended during compliance review — no response, apps removed (pending) — Case 102975269103
Hello, I am posting here because my Apple Developer Program membership is currently stuck in a state that I cannot resolve through the available self-service options, and I have not received a response to my compliance reply or Developer Support case. Timeline: • January 6, 2026 — I purchased my Apple Developer Program membership for a one-year term and received an Apple invoice. • September 22, 2026 — Apple Developer Relations notified me that my membership had been suspended pending a compliance review concerning possible digital-asset activities. • September 23, 2026 — I replied to Apple Developer Relations and provided the requested written confirmation that I do not provide digital-asset or cryptocurrency financial services. I also stated that I am enrolled as an individual and do not operate a registered company or other business entity. I have received no further response or request for additional documentation. My account is now in a contradictory state: • App Store Connect reports “Developer Program Membership Expired” and states that my apps have been removed from the App Store. • My membership was purchased on January 6, 2026 for a one-year term, so it should still be within its paid membership period. • developer.apple.com/account shows “Join the Apple Developer Program.” • If I attempt to enroll, Apple displays: “Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership.” Therefore, I cannot access my existing paid membership, restore Developer Program access, or enroll again. I contacted Apple Developer Support regarding this issue. Developer Support Case ID: 102975269103 The case remains unresolved, and phone support for this case currently shows: “Phone support is currently unavailable. Due to high call volumes, phone support is temporarily unavailable.” I am ready to provide immediately, through an appropriate secure Apple verification channel: • government-issued identification; • proof of address; • my Apple Developer Program purchase invoice; • information about my applications and their functionality; or • any other documentation required to complete the compliance review. I am not asking for a workaround or a new enrollment. I need the existing paid membership and compliance case to be reviewed by the appropriate Apple Developer Program Membership / Compliance team. Could an Apple Developer Relations representative or forum moderator please help route or escalate Case 102975269103 to the appropriate team, or advise whether there is any additional verification or documentation currently required from me? My applications have already been removed from the App Store while this remains unresolved, so the issue is actively affecting distribution. Thank you.
Replies
0
Boosts
0
Views
32
Activity
1d
Xcode Cloud reassigns one ciProduct between app targets with unique bundle IDs
I am seeing Xcode Cloud reuse and reassign a single ciProduct when onboarding multiple iOS app targets from one Xcode project. Each target has its own bundle ID, PBXNativeTarget, product reference, and shared scheme. Environment: Xcode 26.6 (17F113) macOS Tahoe 26.5.2 GitHub repository connected to Xcode Cloud Project: pilot-ios/Airtap.xcodeproj Targets / shared schemes: PocketPilot.ai DEV1 — ai.airtap.dev1 PocketPilot.ai DEV2 — ai.airtap.dev2 PocketPilot.ai DEV3 — ai.airtap.dev3 PocketPilot.ai DEV4 — ai.airtap.dev4 PocketPilot.ai QA1 — ai.airtap.qa1 PocketPilot.ai QA3 — ai.airtap.qa3 Every entry above is a separate PBXNativeTarget with a distinct productReference. Each shared scheme is stored under Airtap.xcodeproj/xcshareddata/xcschemes and builds its corresponding target. QA1 and QA3 were onboarded earlier and received independent Xcode Cloud products as expected. Reproduction: In Xcode, open Xcode Cloud Reports and choose Create Workflow. Select target PocketPilot.ai DEV1 and create an archive workflow using scheme PocketPilot.ai DEV1. DEV1 appears under the correct App Store Connect app. Create another workflow for target PocketPilot.ai DEV2 using scheme PocketPilot.ai DEV2. DEV1 disappears as a separate Xcode Cloud product. Both the DEV1 and DEV2 workflows now appear under the DEV2 App Store Connect app. The App Store Connect API confirms this is not only an Xcode UI or cache issue: Before DEV2 onboarding, ciProduct F048BF00-CECF-4926-84DB-D3474CB030A9 was related to bundle ID ai.airtap.dev1. After DEV2 onboarding, that same ciProduct ID became related to bundle ID ai.airtap.dev2. The product now contains both workflows: PocketPilot DEV1 Archive / scheme PocketPilot.ai DEV1 PocketPilot DEV2 Archive / scheme PocketPilot.ai DEV2 No build was started, and both workflows are currently disabled. Expected behavior: Because every target has a different bundle ID, Xcode should create a separate Xcode Cloud product for each target, as described in the Xcode Cloud onboarding documentation. Actual behavior: The newest onboarding changes the existing ciProduct-to-App Store Connect app relationship instead of creating a new ciProduct. This moves all earlier workflows to the newest app. The public App Store Connect API cannot repair this because it supports reading and deleting ciProducts, but not creating one; ciWorkflows can only be created under an existing ciProduct. I also encountered an Xcode crash while adding another product. The crash stack included XcodeCloudNavigableItemCoordinator.removeNavigableItem(for:) and IDENavigableItemCoordinator, which may be related to the product reassignment. I can provide the crash report in Feedback Assistant if needed. A recent forum thread reports the same high-level symptom: previously created workflows migrate to the newest app. In our case, the API relationship change above makes the backend reassignment directly observable. Is this a current Xcode Cloud onboarding/backend regression? Is there a supported workaround, or can Apple Support create or restore separate ciProducts for these bundle IDs?
Replies
3
Boosts
0
Views
366
Activity
1d
Apple Developer enrollment paid, but account now shows “Not Eligible”
Title: Apple Developer enrollment paid, but account now shows “Not Eligible” Hello, I recently enrolled in the Apple Developer Program using my Apple Account. I completed the enrollment process and paid the membership fee using Apple Pay. The payment was successfully charged, and during the enrollment process I was told that I would receive an email shortly regarding the enrollment. However, I never received that email. When I now log in to my Apple Developer account, it says that my account is not eligible for the Apple Developer Program. The membership fee has already been charged, so I would like to understand what happened to my enrollment and whether the payment can be associated with my application. Could someone please advise me on what I should do next or how I can have the enrollment and payment reviewed? Thank you.
Replies
7
Boosts
2
Views
711
Activity
1d
ios27 ARSCNViewDelegate EXC_BAD_ACCESS (code=2, address=0x16f74ffb0)
Hi, I understand Scenekit is deprecated in ios27, but expectation is that it should continue working in ios27 and not anymore maintained. With ios27 , when we attempt to set self.delegate in an ARSCNViewDelegate we receive a crash. Is there any workaround to have that fixed until we have time to move away from Scenekit? Can this be part of a fix in ios27 considering we should have sometime to migrate out production apps or that won't go through? Thank you.
Replies
2
Boosts
0
Views
1.4k
Activity
1d
FALSE SPAM CLAIM: Spam Flag After Apple Confirmed Our App Was NOT Spam
We need Apple to urgently remove the spam flag on our app. This is not a request for another generic explanation of the rejection. We previously had a Webex meeting with Ewelina from Apple, during which we explained the app, its purpose, and the changes made in response to the prior rejection. We were explicitly told that our app is not spam, (and was never a spam) that the issue would be addressed, and that we could confidently resubmit the app. We relied on that assurance and resubmitted. Yet we received the same spam rejection again. This is causing immediate and substantial financial harm. We are already paying commitments to Plaid and Checkbook, fees to other providers, and salaries to employees who cannot perform the work they were hired to do while our app remains blocked. These costs continue every day without a launch, and our company is facing significant financial distress. We have had to cancel our launch event three times. The third cancellation followed this latest rejection, after Apple told us we could confidently resubmit. We made financial and operational decisions based on that guidance. Please urgently escalate this to someone who can review the Webex meeting with Ewelina, remove the spam designation, and ensure our app is not rejected again on the same basis Apple already told us did not apply. We need a concrete resolution now. We cannot keep paying providers and employees, cancelling launch plans, and absorbing losses because the same flag continues to be applied. If anyone here has experienced the same situation or knows how to get this escalated to someone who can resolve it, we would be extremely grateful for your help.
Replies
0
Boosts
0
Views
71
Activity
1d
iPadOS 27.2 Beta — Display Zoom "Larger Text" spacebar bug fixed?
Hi everyone! Could anyone testing iPadOS 27.2 Beta 2 on an iPad please check a Display Zoom keyboard bug for me? When setting Display Zoom to Larger Text (Settings -> Display & Brightness -> Display Zoom), the spacebar becomes extremely small and squeezed between the language/layout switching keys. Just to add — this applies to both Developer Beta 2 and Public Beta . Thanks to anyone who can test this! Is this UI bug fixed in Beta 2? Thanks!
Replies
0
Boosts
0
Views
45
Activity
1d
Title: EAS iOS build fails with “iTunes service key is empty” on Windows
Hello, I’m trying to create an iOS TestFlight build for an Expo/EAS app on Windows. The project is configured with: Expo SDK 57 EAS CLI 24.1.0 iOS bundle ID: com.i3radleyy.flooriq Apple Developer Program: active individual membership Apple Team ID: R7GLN64JYP The Bundle ID is registered in Apple Developer The app record exists in App Store Connect I am the Account Holder The Expo configuration command succeeds and reports the correct bundle ID. EAS project initialisation also succeeds. However, when running the production build, Apple authentication fails after the Apple ID and password are accepted: Authentication with Apple Developer Portal failed! Failed to set up credentials. iTunes service key is empty Error: build command failed. I have also tried: EAS_NO_VCS=1 EXPO_NO_KEYCHAIN=1 Git is not being used, and the project is being built from the correct app directory. The Apple Developer account and App Store Connect pages are accessible in the browser, and the Bundle ID is registered. Is this a known EAS/Apple authentication issue on Windows? Is there a recommended way to provide the Apple signing credentials or use an App Store Connect API key so that EAS can create the iOS distribution certificate and provisioning profile? Thank you.
Replies
10
Boosts
5
Views
1.7k
Activity
1d
URLSession fails with -1009 on physical iPhone 16 Pro Max running iOS 27 beta, works in Simulator
I’m building a SwiftUI app that fetches public JSON data using URLSession.shared. The request works correctly in the iPhone 17 Pro Max Simulator, but fails on my physical iPhone 16 Pro Max running iOS 27 beta. Endpoint: https://api.jolpi.ca/ergast/f1/2026/driverstandings.json?limit=100 Error: NSURLErrorDomain Code=-1009 “The Internet connection appears to be offline.” NWPath: unsatisfied (Denied over Wi-Fi interface) Resolved 0 endpoints in 1ms The device can access the endpoint through Safari, and the same request works in Simulator. VPN, cellular permissions, Wi-Fi changes, and ATS settings have been checked. Could this be an iOS 27 beta networking regression affecting URLSession on physical devices? Are there recommended workarounds or diagnostics?
Replies
1
Boosts
0
Views
559
Activity
1d
27-Day Nightmare: Expedited Review Fails to Trigger. Is My Account Bugged? Need Human Support.
Hi everyone, I am experiencing a severe system delay and I am wondering if anyone else has faced this, or if an Apple engineer can check my account for a backend glitch. My timeline: It took 17 days just for my individual Apple Developer enrollment to be approved. My first app, has now been stuck on "Waiting for Review" for 10 days. I was officially granted an "Expedited Review" by the support team (Cases 102974693297 and 102976576467), and an agent explicitly told me it would begin "shortly." However, nothing has changed, and the standard support channel only replies with identical automated templates. Given the unusual 17-day initial enrollment delay, I strongly suspect my developer account might have a hidden hold or backend technical bug preventing the App Store Connect system from moving the app's status to "In Review." Has anyone experienced a granted expedited review completely failing to trigger? How can I get a human technical specialist to check my account backend for blockers? Thank you in advance for any guidance.
Replies
5
Boosts
1
Views
335
Activity
1d
AVSpeechSynthesizer Enhanced voices produce silent audio in sandboxed Mac Catalyst app
I have reproduced an issue with AVSpeechSynthesizer on macOS 26.6.2 (25G83) using a minimal Mac Catalyst application. Environment macOS 26.6.2 (25G83) Apple Silicon Xcode 26.x Mac Catalyst AVSpeechSynthesizer Enhanced voice: com.apple.voice.enhanced.en-GB.Daniel The problem is specifically related to App Sandbox. Reproduction I created a completely new minimal Mac Catalyst application. With App Sandbox disabled: let synthesizer = AVSpeechSynthesizer() let utterance = AVSpeechUtterance(string: "Hello, this is a test.") utterance.voice = AVSpeechSynthesisVoice(identifier: "com.apple.voice.enhanced.en-GB.Daniel") synthesizer.speak(utterance) The Enhanced voice works normally. With App Sandbox enabled, with no other sandbox capabilities enabled, the same code no longer produces audible speech.
Replies
3
Boosts
0
Views
814
Activity
1d
New app review stuck
This has happened before with a new app I build that involved subscriptions and it got stuck in a blackhole and i believe it could be a glitch on apples review system. I submitted a new app, the subscription wasnt fully included for review, the reviewer replied to me asking some questions and thiis is when i noticed the sub was not fully linked. So i linked it and now im worried its fallen into the same black hole as before as there has been no movement. Its just sitting waiting to be reviewed. Which is totally fine if the team are just backlogged but i dont want to wait a month or so before knowing this for sure as i cant afford that amount of wasted time. Its related to my WeatherLens app
Replies
1
Boosts
0
Views
95
Activity
1d
App stuck in "Waiting for Review" for 12 days while other updates from the same account are approved normally
App ID: 6790321094 Submission ID: 883d7004-33a3-4fd7-b229-756a15b51cb9 Submitted: August 4, 2026 My app has been in "Waiting for Review" for 12 days with no change in status. In the same period, five other updates from the same developer account went through review normally, within the usual timeframe. So this does not appear to be a general queue backlog or an account-level issue. An expedited review request was submitted and had no effect. The previous version of this update was rejected under Guideline 4.3, and the issue behind that rejection has been fully addressed in this build. Details are in the Review Notes. There is no active thread in Resolution Center, so I have no way to contact the review team about this submission directly. Could someone confirm whether this submission is queued correctly or whether it is stuck? Any guidance would be appreciated.
Replies
3
Boosts
2
Views
436
Activity
1d
Back button briefly jumps to the leading edge of the navigation bar during interactive pop from a screen with a hidden navigation bar (iPhone Duo)
On the iPhone Duo's narrow display, the navigation bar's back button sits in the trailing column below the status bar. During an interactive swipe-back from a screen whose navigation bar is hidden to a screen whose navigation bar is visible, the back button briefly renders in the leading (top-left) position of the bar for one or more frames. In those same frames the trailing-column button is blank. It then jumps back to the trailing column. The result is a visible flicker. Steps to reproduce: Open the attached code in Xcode 27.1 and run it on the iPhone Duo simulator (iOS 27.1), using the narrow display in portrait. Tap "Push". This pushes a screen with a visible navigation bar. Tap "Push without header". This pushes a screen that hides the navigation bar. Slowly swipe back from the leading edge to return to the previous screen. Expected: the back button of the revealed navigation bar stays in the trailing column for the whole transition, the same as with a programmatic pop. Actual: for one or more frames during the gesture, the back button renders at the leading edge of the navigation bar (top-left), and the trailing column is blank. Then it returns to the trailing column. Repro: import UIKit @main final class AppDelegate: UIResponder, UIApplicationDelegate {} final class SceneDelegate: UIResponder, UIWindowSceneDelegate { var window: UIWindow? func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options: UIScene.ConnectionOptions) { guard let windowScene = scene as? UIWindowScene else { return } let window = UIWindow(windowScene: windowScene) let nav = SwipeableNavigationController(rootViewController: ScreenVC(title: "header 0", showsHeader: true)) window.rootViewController = nav window.makeKeyAndVisible() self.window = window // Auto sequence when launched with `-auto YES`: push header, push no header, pop. guard UserDefaults.standard.bool(forKey: "auto") else { return } DispatchQueue.main.asyncAfter(deadline: .now() + 1.5) { nav.pushViewController(ScreenVC(title: "header 0", showsHeader: true), animated: true) } DispatchQueue.main.asyncAfter(deadline: .now() + 3.0) { nav.pushViewController(ScreenVC(title: "no header", showsHeader: false), animated: true) } DispatchQueue.main.asyncAfter(deadline: .now() + 4.5) { nav.popViewController(animated: true) } } } final class ScreenVC: UIViewController { private let showsHeader: Bool init(title: String, showsHeader: Bool) { self.showsHeader = showsHeader super.init(nibName: nil, bundle: nil) self.title = title } required init?(coder: NSCoder) { fatalError() } override func viewWillAppear(_ animated: Bool) { super.viewWillAppear(animated) navigationController?.setNavigationBarHidden(!showsHeader, animated: animated) } override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .systemGroupedBackground let push = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Push") { [weak self] _ in self?.navigationController?.pushViewController(ScreenVC(title: "header 0", showsHeader: true), animated: true) }) let pushNoHeader = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Push without header") { [weak self] _ in self?.navigationController?.pushViewController(ScreenVC(title: "no header", showsHeader: false), animated: true) }) let back = UIButton(configuration: .plain(), primaryAction: UIAction(title: "Go back") { [weak self] _ in self?.navigationController?.popViewController(animated: true) }) let stack = UIStackView(arrangedSubviews: [push, pushNoHeader, back]) stack.axis = .vertical stack.translatesAutoresizingMaskIntoConstraints = false view.addSubview(stack) NSLayoutConstraint.activate([ stack.topAnchor.constraint(equalTo: view.safeAreaLayoutGuide.topAnchor, constant: 10), stack.centerXAnchor.constraint(equalTo: view.centerXAnchor), ]) } } final class SwipeableNavigationController: UINavigationController, UIGestureRecognizerDelegate { override func viewDidLoad() { super.viewDidLoad() interactivePopGestureRecognizer?.delegate = self if #available(iOS 26.0, *) { interactiveContentPopGestureRecognizer?.delegate = self } } func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool { viewControllers.count > 1 } } Thank you in advance!
Replies
1
Boosts
1
Views
210
Activity
1d