Overview

There are some campaigns who have data in the UI (3000+ impressions), but when I try to fetch keywords report via API (/api/v5/reports/campaigns/{campaign-id}/keywords) by CountryOrRegion, it returns no data, but when fetched without CountryOrRegion, it has data. It is a single country campaign, however, I have other single country campaigns that do share data with CountryOrRegion.

Hi, I have a hand model that is in FBX and I'm exporting it to USD in Blender. I get a skinned mesh and while I can track the whole hand how do I track each joint and assign it and animate the skinned mesh itself. All my attempts say this is not possible in RealityKit as of now. True?

In our project, we are now using UIScene, and when click InputText to pull up Keyboard, and when rotate the device, the Keyboard does not update: how can we fix this issue?

Hi everyone, We just completed an App Store Connect app transfer between two developer teams and ran into what seems like an inconsistency with TN3159 (Migrating Sign in with Apple users for an app transfer). According to the technote, both the source and destination teams should be able to call /auth/usermigrationinfo for 60 days after the transfer, even if the migration wasn’t run beforehand. However, right after the transfer completed, the source team (Team A) started receiving: {"error":"invalid_client"} on all /auth/usermigrationinfo requests, even though /auth/token with scope=user.migration still works fine. What we verified before transfer: Team A’s Sign in with Apple key (ES256) was linked to the app and Services ID. OAuth flow for com.org.appname.web returned valid tokens, and the decoded ID token showed aud=com.org.appname.web with a valid private relay email, confirming the key was trusted. What happens after transfer: The key now shows “Enabled Services: —” and the App/Services IDs are no longer selectable in the Developer portal. /auth/usermigrationinfo immediately returns invalid_client for Team A, even within the same day of the transfer. This effectively makes Team A unable to generate transfer_sub values, blocking the migration flow TN3159 describes. Questions: Is Team A supposed to retain authorization to call /auth/usermigrationinfo for 60 days post-transfer? If yes, is there any known workaround to re-authorize the key or temporarily re-bind it to the transferred identifiers? If not, does this mean transfer_sub must be generated before transfer acceptance, contrary to how TN3159 reads? Would really appreciate any confirmation or guidance from Apple or anyone who’s gone through this recently. Thanks,

Since updating all my devices, TV, iPhone, iPad, and possibly HomePods and watch nothing works as it should. The worst of all is the inability to download any app from the App Store. Everything is playing up. It’s iOS nightmare. Can’t wait for the next official iOS software update!

In visionOS, is there a way to temporarily hide the window close/position handle at the bottom of a window? The Safari app does this, so it must be possible.

We have a that relies on accurate GPS location but we’ve noticed that every now and then the location ‘jumps’ a few hundred meters to a different location but reports horizonal accuracy less than 10m. we think the device is picking up a rough location from a local WiFi rather than internal gps sensors. can we a) disable WiFi location Updates? b) identify WiFi location Updates? thank You

Hello. I work on Windows with Visual Studio 2026 Insider , .Net 10 rc1, MAUI , wifi connected to Mac Mini , XCode 16 and upload to App Store to the public. This was all working fine. Yesterday Apple forced me to update XCode to 26.0.1. Now I cannot publish to the Store like I used to. I do not get any errors , instead I get "Publishing project 'Referee' completed." , but the app never shows up in App Store Connect like it usually does. I tried this many times with two different apps that were fine last week. After the XCode update, do I need to reconnect something to somewhere? . . (I shortened paths here for character limit) Validating Mac operating system version compatibility... Checking Xcode version compatibility... Validating Xcode license state... Verifying installed Xcode tools... Initializing Build agent... Checking Build 26.0.10970-net10-rc.2 installation... Starting Build 26.0.10970-net10-rc.2 in port 59237... Agent Build 26.0.10970-net10-rc.2 is running Build 26.0.10970-net10-rc.2 started successfully Checking installed iOS runtimes... Checking for compatible simulators... Performing server validations against 'Ray’s Mac mini'... Connection to 'Ray’s Mac mini' completed successfully Build properties for C:\TCR\TCR Referee\Referee.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR\TCR MAUI Mar 24.sln, SolutionName: TCR MAUI Mar 24, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/Library/Caches/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\maui\iOS\PairToMac, BasePath: /Users/raybrennan/Library/Caches/maui/PairToMac, LogsPath: /Users/Library/Logs, DotNetRuntimePath: /Users/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: RB, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 Archiving App Bundle 'Referee'... Build properties for C:\TCR\TCR Referee\Referee.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR\TCR MAUI Mar 24.sln, SolutionName: TCR MAUI Mar 24, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/raybrennan/Library/Caches/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\mrray\AppData\Local\maui\iOS\PairToMac, BasePath: /Users/raybrennan/Library/Caches/maui/PairToMac, LogsPath: /Users/raybrennan/Library/Logs, DotNetRuntimePath: /Users/raybrennan/Library/Caches/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: Ray Brennan, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 App archive 'Referee' completed successfully. Begining distribution, 23/10/2025 15:36:09 Channel: App Store App Bundle Id: com.theclubreferee.referee, Version: 0.3 Publishing to 'C:\Users\mrray\AppData\Local\maui\iOS\Archives\2025-10-23\Referee 10-23-25 3.33 PM.xcarchive\Published\Referee0.3.ipa' Build properties for C:\TCR\TCR Referee\Referee.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR\TCR MAUI Mar 24.sln, SolutionName: TCR MAUI Mar 24, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/raybrennan/Library/Caches/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\mrray\AppData\Local\maui\iOS\PairToMac, BasePath: /Users/raybrennan/Library/Caches/maui/PairToMac, LogsPath: /Users/raybrennan/Library/Logs, DotNetRuntimePath: /Users/raybrennan/Library/Caches/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: Ray Brennan, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 Build properties for C:\TCR\TCR Referee\Referee.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR\TCR MAUI Mar 24.sln, SolutionName: TCR MAUI Mar 24, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/raybrennan/Library/Caches/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\mrray\AppData\Local\maui\iOS\PairToMac, BasePath: /Users/raybrennan/Library/Caches/maui/PairToMac, LogsPath: /Users/raybrennan/Library/Logs, DotNetRuntimePath: /Users/raybrennan/Library/Caches/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: Ray Brennan, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 Validating bundle... Build properties for C:\TCR.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR.sln, SolutionName: TCR , RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/raybrennan/Library/Caches/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\maui\iOS\PairToMac, BasePath: /Users//maui/PairToMac, LogsPath: /Users/Logs, DotNetRuntimePath: /Users/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: Ray Brennan, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 Uploading 'C:\Users\maui\iOS\Archives\2025-10-23\Referee 10-23-25 3.33 PM.xcarchive\Published\Referee0.3.ipa' Build properties for C:\TCR.csproj: VisualStudioProcessId: 17564, SolutionPath: C:\TCR.sln, SolutionName: TCR, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: ios-arm64, KeepLocalOutputUpToDate: False, MessagingVersion: 26.0.10970-net10-rc.2, _DotNetRootRemoteDirectory: /Users/maui/PairToMac/SDKs/dotnet/, LocalBasePath: C:\Users\iOS\PairToMac, BasePath: /Users/raybrennan/Library/Caches/maui/PairToMac, LogsPath: /Users/raybrennan/Library/Logs, DotNetRuntimePath: /Users/maui/PairToMac/Runtimes/dotnet/dotnet, ServerSshPort: 22, ServerTcpPort: 59237, ServerUser: Ray Brennan, ContinueOnDisconnected: False, ServerAddress: 10.101.101.101 Publishing project 'Referee' completed.

In Reality Composer Pro, why is the Sky Sphere so much larger than the Sky Dome? By my estimate, the Sky Sphere has a radius of 100m, while the Sky only has a radius of only 12m.

Is there sample code on how to use VTFrameProcessorOpticalFlow?

I’ve been working on marketing my iOS app, but it’s been quite frustrating so far. ASO hasn’t brought the results I expected, and I’m not sure what to try next. I’d like to learn more about indie app marketing beyond keyword tweaks-any blogs, courses, books, or communities you’d recommend for understanding effective strategies and improving app visibility?

Hi everyone, I am developing a .NET MAUI Mac Catalyst app (sandboxed) that communicates with a custom vendor-specific HID USB device. Within the Catalyst app, I am using a native iOS library (built with Objective-C and IOKit) and calling into it via P/Invoke from C#. The HID communication layer relies on IOHIDManager and IOUSBInterface APIs. The device is correctly detected and opened using IOHIDManager APIs. However, IOHIDDeviceRegisterInputReportCallback never triggers — I don’t receive any input reports. To investigate, I also tried using low-level IOKit USB APIs via P/Invoke from my Catalyst app, calling into a native iOS library. When attempting to open the USB interface using IOUSBInterfaceOpen() or IOUSBInterfaceOpenSeize(), both calls fail with: kIOReturnNotPermitted (0xe00002e2). — indicating an access denied error, even though the device enumerates and opens successfully. Interestingly, when I call IOHIDDeviceSetReport(), it returns status = 0, meaning I can successfully send feature reports to the device. Only input reports (via the InputReportCallback) fail to arrive. I’ve confirmed this is not a device issue — the same hardware and protocol work perfectly under Windows using the HIDSharp library, where both input and output reports function correctly. What I’ve verified •Disabling sandboxing doesn’t change the behavior. •The device uses a vendor-specific usage page (not a standard HID like keyboard/mouse). •Enumeration, open, and SetReport all succeed — only reading input reports fails. •Tried polling queues, in queues Input_Misc element failed to add to the queues. •Tried getting report in a loop but no use.

When our Bluetooth device is scanned and a connection is initiated through the app on the iPhone 17, the air log shows that the iPhone sends an LL_LENGTH_REQ to execute the Data Length Update Procedure. However, our peripheral does not support the Bluetooth LE Data Length Extension, so it responds with an LL_UNKNOWN_RSP PDU with the UnknownType field set to LL_LENGTH_REQ. After receiving the LL_UNKNOWN_RSP, the iPhone 17 does not proceed with the subsequent Bluetooth LE service discovery process. The connection is maintained until the peripheral actively disconnects. Once the peripheral disconnects and continues broadcasting Bluetooth signals, the iPhone 17 repeatedly tries to connect to the peripheral and executes the aforementioned process, even if the app has been terminated. According to the Bluetooth 4.2 core specification ([Vol. 6] Part B, Section 5.1.9), which can be found here: https://www.bluetooth.com/specifications/specs/core-specification-amended-4-2/, the iPhone should accept the LL_UNKNOWN_RSP and terminate the Data Length Update Procedure after receiving it, proceeding with the subsequent operations using the default minimum parameters. Phenomenon: When the app calls the - (void)connectPeripheral:(CBPeripheral *)peripheral options:(nullable NSDictionary<NSString *, id> *)options method, the connection result callback is never received. After a period of approximately 10 seconds, it fails with a callback, displaying the message: central did fail to connect to peripheral: <TY : 45E4A697-31AE-9B5A-1C38-53D7CA624D8C, Error Domain=CoreBLEErrorDomain Code=400 "(null)">.

I’m having issues enrolling in the Apple Developer Program. My original Apple ID was unable to enroll due to an internal restriction, and after multiple calls with Support (including L2), I was advised to create a new Apple ID and use the same enrollment code I was awarded for being selected as a Swift Student Challenge 2025 winner. However, when I attempt to redeem the code with the new account, I receive an error stating that the code has already been redeemed. I have never successfully enrolled with the original account, so the code should not be marked as used. I’ve tried working through Support several times, but I’m still stuck. Could someone please review this issue or issue a new code so I can complete my enrollment? Thank you in advance for your help.

I submitted a puzzle app called “Anime Jigsaw” to App Store Connect. The App Store Connect team initially rejected the app due to minor errors. I then fixed the errors and resubmitted it, but this time they said it violated “Guideline 4.1 - Design - Copycats” and that I didn't write the code. I responded that I wrote the code and could prove it. They rejected it again, citing "Guideline 4.1 - Design - Copycats,“ and I explained that my app was different from other puzzle apps because you solve puzzles while listening to Lo-Fi music. But this time, they issued a ”Pending Termination Notice“ and started saying ”Evidence of Dishonest or Fraudulent Activity." I am definitely not a scammer. I am trying to communicate with the App Store Connect team, but they are trying to close my account and label it as “Fraudulent Activity.” Why are you doing this? How can I resolve this? My account will be closed in 30 days, and I can't communicate with anyone. Team ID: 93LGGK4LG4 Apple ID: 6751961511 Please Apple Team Help Me.

Hello all, I am new to implementing payments in an app, and thus completely at sea here. I have created a small app that I have set a one-time (non-consumable) payment for a premium version. In the Xcode simulator (on all platforms) and on any physical test devices I have tried, the payment works as expected. I have a sandbox account and various test accounts, both dummy and actual real accounts (friends and family). Everywhere everything works perfectly fine. Yet, when I submit for review I get a rejection with this contents: We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, the app still failed to load the in-app purchase. Please review the details and resources below and complete the next steps. Review device details: Device type: iPad Air (5th generation) OS version: iPadOS 18.6 Next Steps When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead. Additionally, note that the Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect before paid in-app purchases will function. Resources Learn how to set up and test in-app purchase products in >the sandbox environment. Learn more about validating receipts with the App Store. Steps I have done: I have signed all agreements and all bank account details are in order. Everything in the In-app-purchases section of the AppStoreConnect in an Active state. I have triple checked that the configuration of the in-app purchases is correct (product IDs, amounts, etc.) I have created test accounts and tested in sandbox What I don't understand from the reviewer's response is what receipts validation are they talking about? I have no payment servers (the whole concept of using Apple's in-app-purchases service is to not have to deal with my own payment implementation). The StoreKit documentation specifically reads: For each transaction that represents a current purchase, your app delivers the purchased products. To validate purchases, you can verify transactions on your server, or rely on StoreKit’s verification. So now I am confused. The reviewer's response is so vague, and so completely deprived of details that I have no idea what to do... Does the problem concern the product purchase trigger and the that in production environment it does not trigger? Is it that I haven't implemented a receipt validation? Do I need to? Although the documentation mentions that it can be done by StoreKit, I couldn't find anything concerning how to do it :( Can someone give me a hand please? Cheers, Alex

We're unable to renew our developer program with apple because there is no renew button shown to us, neither on the website, mac app nor ios app. We followed the instructions shown to us on the app connect page on how to renew it. but when where they're saying there should be a renew button, there is none or anywhere else. How are we suppose to renew? Raised this with a support ticket but haven't received any reply, case ID: 102733260138 How to get this resolved? We don't get any "phone call" option on the support page either.

Context I’m deploying large language models on iPhone using llama.cpp. A new iPhone Air (12 GB RAM) reports a Metal MTLDevice.recommendedMaxWorkingSetSize of 8,192 MB, and my attempt to load Llama-2-13B Q4_K (~7.32 GB weights) fails during model initialization. Environment Device: iPhone Air (12 GB RAM) iOS: 26 Xcode: 26.0.1 Build: Metal backend enabled llama.cpp App runs on device (not Simulator) What I’m seeing MTLCreateSystemDefaultDevice().recommendedMaxWorkingSetSize == 8192 MiB Loading Llama-2-13B Q4_K (7.32 GB) fails to complete. Logs indicate memory pressure / allocation issues consistent with the 8 GB working-set guidance. Smaller models (e.g., 7B/8B with similar quantization) load and run (8B Q4_K provide around 9 tokens/second decoding speed). Questions Is 8,192 MB an expected recommendedMaxWorkingSetSize on a 12 GB iPhone? What values should I expect on other 2025 devices including iPhone 17 (8 GB RAM) and iPhone 17 Pro (12 GB RAM) Is it strictly enforced by Metal allocations (heaps/buffers), or advisory for best performance/eviction behavior? Can a process practically exceed this for long-lived buffers without immediate Jetsam risk? Any guidance for LLM scenarios near the limit?

I’m building a macOS document based app using SwiftUI’s DocumentGroup API. By default, when a document based app launches, macOS automatically shows a file open panel or creates a new untitled document window. However, I want to suppress this default behavior and instead show a custom welcome window when the app starts — something similar to how Xcode or Final Cut Pro shows a “Welcome” or “Start Project” screen first. So basically, when the user opens the app normally, it should not open the document selector or create a document automatically. Instead, it should show my custom SwiftUI or AppKit window. Here is my Code :- //MyApp.swift import SwiftUI import AppKit @main struct PhiaApp: App { @NSApplicationDelegateAdaptor(AppDelegate.self) var appDelegate var body: some Scene { DocumentGroup(newDocument: MyDocumentModel()) { file in EditorView(document: file.document, filePath: file.fileURL) } Settings { EmptyView() } } } Current I have this code setup for my MainApp.swift, where I am using the AppDelegate to create a custom recording window using appkit and also defining the DocumentGroup to handle the custom .myapp file opens. However, when I launch the app, its showing my appkit window as well as the macOs native file Selector to select the file I want to open. I want when the user opens the app normally, it should not open the document selector or create a document automatically. Instead, it should show my custom SwiftUI or AppKit window. However, the app should still fully support opening .myapp documents by double clicking from Finder, using the standard File → Open and File → New menu options, also having multiple document windows open at once. This is my AppDelegate.swift file :- import AppKit import SwiftUI class AppDelegate: NSObject, NSApplicationDelegate { var panel: Panel? private var statusItem: NSStatusItem? func applicationDidFinishLaunching(_ notification: Notification) { showWindow() } // MARK: - Window control func showWindow() { if panel == nil { let root = RecordingViewMain() let newPanel = Panel(rootView: root) if let screen = NSScreen.main { let size = NSSize(width: 360, height: 240) let origin = NSPoint( x: screen.visibleFrame.midX - size.width / 2, y: screen.visibleFrame.midY - size.height / 2 ) newPanel.setFrame(NSRect(origin: origin, size: size), display: true) } panel = newPanel } panel?.makeKeyAndOrderFront(nil) } func hideWindow() { panel?.orderOut(nil) } @objc private func showPanelAction() { showWindow() } @objc private func quitAction() { NSApp.terminate(nil) } }

I added a new device and it's not recognizing the device model. This causes a message saying "Unable to verify" when signing an app. Has anyone else encountered this issue? This only happens with this one device, not others.