“show when run”

Hello everyone, We are running into a strange App Store Connect glitch that has trapped our app (BLOKX) in the Waiting for Review queue for almost 20 days. Standard Developer Support is unable to resolve it because the system is feeding them incorrect dates. The Issue: The original submission timestamp keeps automatically resetting to the present day, putting us in a perpetual ghost queue loop. The Timeline: April 8: We originally submitted the app (status changed to Waiting for Review). April 23: We contacted Developer Support. They replied stating our app had been waiting for review as of 23/04. April 27 (Today): We followed up. Support replied again, this time stating our app has been waiting for review as of 27/04. Because the backend timestamp keeps resetting to the current day, automated support simply tells us that our review is proceeding normally and falls within standard timeframes, failing to see that the app has actually been stuck since April 8. Case Number: 102871846091 Has anyone else

What I am trying to do I am building a browser-based exam proctoring platform that runs in Safari and Chrome on iPad. I need to detect when a candidate opens another app or browser tab in Slide Over (the floating panel) while the exam is running in the background. This is a pure web app - no native wrapper, no MDM. What I've already tried I tried listening to window blur and focus events neither fires when Slide Over is triggered on Chrome. I tried document.visibilitychange - same result, it never fires during Slide Over. I tried the resize event but it is completely inconsistent on iPadOS Chrome. For Split View I am computing the ratio of window.innerWidth to window.screen.width and flagging below 0.80 as a likely split. That works. But Slide Over doesn't change the viewport at all - the exam tab stays full width in the background. So my ratio check is completely blind to it. My question Is there any JavaScript API, browser event, visualViewport property, or any other web-accessible signal

When use Q-encoded to handle non-ASCII characters, if raw characters start with non-ASCII, we will get encoded like '=?UTF-8?Q?=XX=XX?='. IOS(>26) Mail App may think the first '?=' end of the '=?UTF-8?Q?=' is then end flag, so show incorrectly.

Hi, We are seeing a reproducible issue when presenting SKStoreProductViewController in our production app context. For a quick summary, presenting and dismissing SKStoreProductViewController on iOS 15/16 can leave our app in a visually corrupted state (black/empty/orphaned-looking UI). On iOS 18/26 (presumably every iOS version in between), the same flow works correctly. What we verified dealloc is not called for our affected view controllers. During StoreKit lifecycle, VC hierarchy is logically valid: window.rootViewController remains stable. presented chain remains expected. SKStoreProductViewController becomes top-presented and dismisses normally as logged in the delegate. In the xcode view hieararchy, only the UITransitionView and UIDropShadowView are present. Our app content VCs are no longer attached to the visible hierarchy. This is the code we used: SKStoreProductViewController *storeVC = [SKStoreProductViewController new]; storeVC.delegate = self; [storeVC loadProductWithParameters:@{ SKStoreProductP

Hi, My enrollment has been Pending for 3 business days after submitting the requested documents. Details: Country: Peru Entity: Individual Subscription paid: April 22, 2026 (PEN 389.90, confirmation received) Documents submitted and acknowledged on April 22 with a follow-up within two business days message Today (April 25): account still shows Pendiente with a prompt to pay again, even though payment is active I have an open Case ID with Apple Developer Support and can share it privately if a moderator needs to reference it. Is this delay normal right now? Posting here in case anyone has guidance or has experienced this recently. Thanks!

I’m using SwiftData with CloudKit and running into an issue during initial sync on a fresh device. I’m importing a small set of records, some records has images as CKAsset (with about 5 images ~3MB). Records indexes are the default ones for the Dev env. The problem is that the import process never seems to complete. However, if I delete those records that contains the assets from the iCloud Dashboard, the import finishes successfully. Has anyone experienced something similar? What approach would you recommend to handle this without implementing a custom sync layer on top of CloudKit? I am logging remote changes events (NSPersistentStoreRemoteChange): CloudKit import in progress...|2026-04-25 22:18:10| Then I see: Background Task 49 (CoreData: CloudKit Import), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this. And then the import ne

Hi everyone, I'm hoping someone here has experienced something similar or can offer some guidance, as I'm running out of ideas. I've been an Apple Developer for about 7 months. This is my first app submission, I submitted it on March 24, 2026, and it has been sitting at Waiting for Review ever since. 32 days now with no movement. What I've already checked and confirmed: All agreements, tax, and banking information are fully completed in App Store Connect No issues visible in the AppStore Connect DSA trader verification has been approved (I'm based in EU) I contacted Developer Support and they confirmed they can see my submission and that it is indeed Waiting for Review since March 24th An expedited review request was submitted and accepted by the support team, who told me the review should begin shortly - that was several weeks ago Additional context: During the 7 months I've been a developer, none of my TestFlight external review requests ever went through either, which makes me wonder if there is s

[Submitted as FB22612121] A SwiftUI Button using .buttonStyle(.glass) with .buttonBorderShape(.capsule) changes its background abruptly when its size goes from 50×50 to 51×51 points in dark mode. This appears to be a threshold in opacity/material rather than a smooth size-based change. The sample shows identical buttons at 40, 50, 51, and 60 points, with a clear jump between 50 and 51. Measured RGB values shift from 19,19,19 to 30,30,30. The effect also varies with the background, which points to a material/opacity change rather than a fixed fill. ENVIRONMENT iOS 26.4.1 (23E254a) iOS 26.5 (23F5059e) REPRO STEPS Create a new iOS SwiftUI project. Replace ContentView with the sample code below. Run the app or open ContentView in SwiftUI Preview (dark mode). Observe the buttons at 40×40, 50×50, 51×51, and 60×60. Compare the 50pt and 51pt buttons. ACTUAL The background changes abruptly between 50pt and 51pt. The 51pt button uses a noticeably different opacity/material, producing a visible jump in

I set up all the App Store details, including support info and other required information, but I’m having an issue when adding a build and trying to save. The Save button turns red, and I’m not sure why. It’s not showing what I’m missing in the setup.

Xcode 26.3 MCP xcode-tools: RunSomeTests / RunAllTests response violates tool output schema (missing required errors per test) I’m using the MCP server “xcode-tools” shipped with Xcode 26.3 to run tests. Two tools fail consistently due to a schema mismatch: RunSomeTests RunAllTests Steps Call XcodeListWindows and get a valid tabIdentifier for my workspace. Call GetTestList with that tabIdentifier. This works and returns test identifiers like: ChatKitManagerCreationTests/testInitializesWithDependencies() Call RunSomeTests with tests = [{ targetName, testIdentifier }, …] (or call RunAllTests). Actual result The tool call fails with an MCP schema validation error like: Structured content does not match the tool's output schema: data/results/0 must have required property 'errors', data/results/1 must have required property 'errors', ... Why this looks like an xcode-tools bug According to the tool descriptor JSON for RunSomeTests / RunAllTests, each element of results[] is required to contain: targetName