Overview

It seems that beta 3 broke StoreKit Testing when running against an iOS 26 simulator device. Specifically, when validating product IDs, the debug console displays messages like the following: [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) [492a4cfa_SK1] Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) In addition, the SKProductsResponse (I am using the original StoreKit API), lists all requested product IDs in invalidProductIdentifiers. The products array is empty. StoreKit Testing behaves as expected when Xcode 26 beta 3 is run against an iOS 18.4 simulator device.

I've successfully signed Unix apps manually in the past. Today (after signing the new agreement) I can get it to replace the existing signature but it says "rejected" when I check it. Here are the commands I'm using: michaelleahy@Michaels-Mini ~ % sudo codesign --force --deep --options runtime --sign "Developer ID Application: Bookup Corp. (6J8PUT****)” /Users/michaelleahy/Documents/theapp /Users/michaelleahy/Documents/theapp: replacing existing signature michaelleahy@Michaels-Mini ~ % spctl -a -vvvv -t install /Users/michaelleahy/Documents/theapp /Users/michaelleahy/Documents/theapp: rejected source=Unnotarized Developer ID origin=Developer ID Application: Bookup Corp. (6J8PUT****) Here is a command (issued right after the one above) showing an older signed app is accepted: michaelleahy@Michaels-Mini ~ % spctl -a -vvvv -t install /Users/michaelleahy/Documents/olderapp /Users/michaelleahy/Documents/olderapp: accepted source=Notarized Developer ID origin=Developer ID Application: Bookup Corp. (6J8PUT****) What might I be missing? Something changed since the last time I signed an app.

I have an iPhone 14 running iOS 16.1 and my series 5 watch running watchOS 9.1. I was able to turn on Developer Mode on the phone by going to Settings--> Privacy & Security --> Developer Mode. On the watch however (I'm doing this directly on the watch and not on the watch app on the phone) once I'm in Privacy & Security, there is no option to select Developer Mode. How do I get my watch in Developer Mode in order to get a successful build in xCode?

Description: I’m developing a tvOS app using SwiftUI where we play background audio (music) in the Welcome screen, with support for offline playback via local caching. Feature Overview: App fetches audio metadata from API Starts streaming audio (HLS .m3u8) immediately In parallel, downloads the raw audio file (.mp3) Once download completes: Switches playback from streaming → local file On next launch (offline mode), app plays audio from local storage Issue: This flow works perfectly on the Simulator, but on a real Apple TV device: Audio plays for a few seconds (2–5 sec) and then stops Especially after switching from streaming → local file No explicit AVPlayer error is logged Playback sometimes stops after UI updates or periodic API refresh Implementation Details: Using AVPlayer with AVPlayerItem Background audio controlled via a shared manager (singleton) Files stored locally using FileManager (currently using .cachesDirectory) Switching playback using: player.replaceCurrentItem(with: AVPlayerItem(url: localURL)) player.play() Observations: Works reliably on Simulator On device: -- Playback stops silently -- Seems related to lifecycle, buffering, or file access No issues when continuously streaming (without switching to local) Questions: Is there any limitation or known issue with AVPlayer when switching from streaming (HLS) to local file playback on tvOS? Are there specific requirements for playing locally cached media files on tvOS (e.g., file location, permissions, or sandbox behavior)? What is the recommended storage location and size limit for cached media files on tvOS? We understand tvOS has limited persistent storage Is .cachesDirectory the correct approach for this use case? Are there known differences in AVPlayer behavior between Simulator and real Apple TV devices (especially regarding buffering or lifecycle)? What is the recommended approach for implementing offline background audio on tvOS apps? Goal: We want to implement a reliable system where: Audio streams initially Seamlessly switches to local file after download Continues playing without interruption Supports offline playback on subsequent launches Any guidance or best practices would be greatly appreciated. Thank you!

Hi, I’ve been invited to an Apple Developer account with the Developer role. I’ve already created a subscription in App Store Connect, but when I try to fetch available subscriptions in Xcode for in-app purchase, nothing appears to be available for purchase.

I'm working on an app, and currently, 2 things dont work: account creation and notifications. I want to find the root of why these errors are occurring, and I want to know if these errors are coming from Firebase, certain settings in Xcode not being checked, or my actual written code not being typed correctly. I've tried to run my issue through ChatGPT many times to pretty much no success, so any help on what to do so I can clear certain areas and make sure the bugs aren't from certain spots, and help me narrow down the issue would be great. Otherwise, if there are other guides or threads I can be linked to, and help me fully break down the issue, that would be great. Thank you for your time reading, and I hope I can get some advice.

I'm trying to submit my first In-App Purchase products with app version 1.0, but I cannot find the "In-App Purchases and Subscriptions" section on the app version page in App Store Connect. IAP Products: 1 non-consumable + 1 auto-renewable subscription. Both products have complete configurations (pricing, screenshots, descriptions, review notes). Current situation: The IAP configuration page says: "Select your In-App Purchase from the 'In-App Purchases and Subscriptions' section on the app version page" But this section does not appear on my version 1.0 page The "Submit for Review" button on the IAP product page is grayed out Status shows "Developer Action Needed" My app has been rejected twice (Guideline 2.1(b)) because the IAP products were not included with the binary Paid Apps Agreement is active Has anyone experienced this issue? How can I link my IAP products to the app version submission?

Hello, I’m experiencing a serious issue with TestFlight. I correctly set up internal testing: • Added testers via email • Assigned builds • Everything shows as “Ready to Test” However, when trying to install via TestFlight, I get: “App Name couldn’t be installed” “The requested app is not available or doesn’t exist” ⚠️ Important note: This issue is NOT limited to a single app. It happens across all apps in my account. So it does not seem to be app-specific. What I’ve already checked: • Agreements, Tax, and Banking are completed • App Privacy is fully filled • Builds are successfully uploaded and selected • I am correctly added as an internal tester • Tried logging out/in of TestFlight • Reinstalled the app and TestFlight I contacted Apple Developer Support twice but received no response. Has anyone experienced this issue affecting multiple apps? Any help or guidance would be greatly appreciated. ⸻ Additional technical details: • Developer Account Apple ID: yilmaz34muhammed(at)icloud.com • App Store Connect App ID: 6762088121 • Bundle ID: com.devyilmaz.TahlilAI • Build Version: 0.2.0 (1) This issue occurs across all apps in my account.

Hi everyone, I’m currently implementing Live Activities in my music app to display real-time lyrics on the Lock Screen. The app works fully offline, so I’m not using push updates or push tokens. Instead, I’m updating the Live Activity locally as each new line of lyrics is played (essentially near real-time updates synced with the song). However, I’m running into an issue where the Live Activity UI is not updating reliably or frequently enough. Even though I’m calling the update method for each lyric line, the changes are either delayed or not reflected at all. Here’s some additional context: • The app runs fine in the background (verified via battery usage and playback behavior) • Live Activity is successfully created and initially displayed • Updates are triggered locally (no push notifications involved) • Updates are happening quite frequently (per lyric line) • No crashes or errors are observed My questions: 1. Is there a system-imposed throttling limit on how frequently Live Activities can be updated locally? 2. Are there recommended update intervals for smooth UI updates (e.g., for use cases like lyrics or timers)? 3. Does Live Activity deprioritize updates for offline apps or background execution? 4. Are there any additional configurations or capabilities required to ensure consistent updates? 5. Is using something like AsyncStream or other concurrency patterns helpful in this case? 6. Are there any undocumented limitations or best practices for high-frequency updates? 7. Is there any private or internal API used by Apple apps (like Music) that allows smoother real-time updates? My goal is to achieve smooth, near real-time lyric updates similar to Apple Music’s Now Playing experience. Any guidance, best practices, or clarification would be greatly appreciated. Thanks in advance!

Hi everyone, I started enrolling in the Apple Developer Program but accidentally entered an incorrect address during the process. Now the enrollment form seems to be stuck/cached, and I’m unable to proceed or correct the information. I’ve already contacted Apple Developer Support and requested a reset, but haven’t received a response yet (it’s been several business days). This issue is completely blocking my enrollment. Has anyone experienced something similar? Is there any way to reset the enrollment process or update the information from my side? Any help or guidance would be greatly appreciated. Thank you!

import Cocoa class RedRotatedView: NSView { override func viewDidMoveToSuperview() { super.viewDidMoveToSuperview() DispatchQueue.main.async { self.applyRotation() } } private func applyRotation() { wantsLayer = true layer?.backgroundColor = NSColor.red.cgColor let radians = CGFloat(30 * Double.pi / 180.0) self.layer?.transform = CATransform3DMakeRotation(radians, 0, 0, 1) } override func layout() { super.layout() } } class MainView: NSView { let redView: RedRotatedView override init(frame frameRect: NSRect) { self.redView = RedRotatedView() super.init(frame: frameRect) setupRedView() } required init?(coder: NSCoder) { fatalError("init(coder:) has not been implemented") } private func setupRedView() { redView.wantsLayer = true redView.layer?.backgroundColor = NSColor.red.cgColor addSubview(redView) redView.translatesAutoresizingMaskIntoConstraints = false NSLayoutConstraint.activate([ redView.centerXAnchor.constraint(equalTo: centerXAnchor), redView.centerYAnchor.constraint(equalTo: centerYAnchor), redView.widthAnchor.constraint(equalToConstant: 200), redView.heightAnchor.constraint(equalToConstant: 200) ]) // redView.frame = NSRect(x:100,y:100,width: 200,height: 200) } } @main struct AppKitRotationTestApp { static func main() { let app = NSApplication.shared let delegate = AppDelegate() app.delegate = delegate app.run() } } class AppDelegate: NSObject, NSApplicationDelegate { var window: NSWindow! func applicationDidFinishLaunching(_ aNotification: Notification) { let mainView = MainView(frame: NSRect(x: 0, y: 0, width: 800, height: 600)) window = NSWindow( contentRect: NSRect(x: 0, y: 0, width: 800, height: 600), styleMask: [.titled, .closable, .resizable, .miniaturizable], backing: .buffered, defer: false ) window.center() window.title = "AppKit Rotation Test" window.contentView = mainView window.makeKeyAndOrderFront(nil) } func applicationWillTerminate(_ aNotification: Notification) { } func applicationSupportsSecureRestorableState(_ app: NSApplication) -> Bool { return true } } If NSLayoutConstraint is not used directly and the NSView's frame is set directly, this situation does not occur. How can I avoid the transform being reset when using NSLayoutConstraint for layout?

I logged in to macOS with my localization language. try to perform following code. but always get "Documents". What do I miss? Apple Swift version 5.2.4 macOS 10.15.6 Xcode 11.6 code let paths = NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true) if paths.count > 0 {     let doc = FileManager().displayName(atPath: paths[0])     print(doc) } result Documents

Hello, I’m experiencing a serious issue with TestFlight. I correctly set up internal testing: • Added testers via email • Assigned builds • Everything shows as “Ready to Test” However, when trying to install via TestFlight, I get: “App Name couldn’t be installed” “The requested app is not available or doesn’t exist” ⚠️ Important note: This issue is NOT limited to a single app. It happens across all apps in my account. So it does not seem to be app-specific. What I’ve already checked: • Agreements, Tax, and Banking are completed • App Privacy is fully filled • Builds are successfully uploaded and selected • I am correctly added as an internal tester • Tried logging out/in of TestFlight • Reinstalled the app and TestFlight I contacted Apple Developer Support twice but received no response. Has anyone experienced this issue affecting multiple apps? Any help or guidance would be greatly appreciated. ⸻ Additional technical details: • Developer Account Apple ID: yilmaz34muhammed(at)icloud.com • App Store Connect App ID: 6762088121 • Bundle ID: com.devyilmaz.TahlilAI • Build Version: 0.2.0 (1) This issue occurs across all apps in my account.

Hi there, I'm at a loss as to how to resolve this so hoping I can get some help/ideas here. Issue: We currently have two users who are unable to install our development iOS app. We sign the app as normal during the build process and upload it to firebase for distribution. Both of these users and their devices have been able to use this system previously, all our other dev users and devices are also still working but two of them receive an "this app cannot be installed because it's integrity could not be verified" error. What I have done to resolve: Check device UDIDs are both registered in apple developer portal Checked that the development profile has those devices included Checked that the development certificate is valid, this cert is being used with a different development app that isn't having this issue Restored the device disabled and reenabled the developer mode reinstalled the firebase distribution profile recreated the developer provisioning profile All of the above have not resolved the issue and I'm running out of ideas. If anyone has had the same issue or knows of something else we might be able to attempt that would be great. Thank you in advance John

I’ve been waiting to get my business developer account approved and it is taking a long time. Is Apple just really backed up right now? It is actually taking longer for me to get approval than actually building the app. 🤣 I still can’t get into App Store Connect because of this. So I’m really hindered with progress until this is resolved.

Hi, I need your opinion about an issue we faced while trying to implement an iOS widget in our Flutter app. Here is what we did and the problems we encountered: We created a Widget Extension (SwiftUI + WidgetKit) inside the existing Flutter iOS project. The widget files were generated correctly (Widget.swift, WidgetBundle.swift, Info.plist, etc.). However, during the integration, we faced multiple issues: Build Cycle Error We repeatedly got: “Cycle inside Runner; building could produce unreliable results” This was related to embedding the widget extension into the Runner target. Embed Problems Sometimes Xcode did not automatically create the “Embed App Extensions” phase. When we added it manually → build cycle errors appeared. When we removed it → the widget was not embedded at all (no PlugIns folder in Runner.app). Duplicate / Conflicting Embed The extension appeared both in: “Embed Foundation Extensions” “Frameworks, Libraries, and Embedded Content” Removing one often broke the build or removed the other as well. Widget Not Appearing Even when build succeeded: Widget did not appear on device PlugIns/Widget.appex was missing from build output Flutter Linking Errors In another test project, we got: Undefined symbol: _FlutterMethodChannel Undefined symbol: _FlutterBasicMessageChannel etc. This happened because the widget extension tried to link Flutter dependencies, which should not happen. App Group Confusion We also tried adding App Group (group.com.xxx), but behavior didn’t change. Conclusion: We suspect the root issue is: The Flutter template we are using was not designed for WidgetKit integration Xcode embedding phases and Flutter build scripts conflict with extension targets Question: In your opinion: Is this a known limitation with Flutter-based iOS projects? Is there a clean way to integrate WidgetKit without breaking the Runner target? Or is it better to create a separate native iOS module for the widget? Any guidance would be really appreciated. Thanks!

Trying to enroll in developer program in Korea. Foreigner resident with a visa and Korean Alien Registration Card and Korean Driver’s license, however, I am unable to complete verification as it doesn’t accept my passport (Canadian) or my Korean issued ID cards. Tried both the mobile app and through the web with no luck. Tried changing my Apple ID name to all caps etc. Now the app says I am ineligible to enroll through the app. I have a support ticket in but it seems like CS takes forever to respond. Any other avenues to contact support or resolve this? Thank you!

Hello People, I am using Xcode 26.4 macOS 26.4. We have got the Contactless Pass Entitlements from Apple. But when i am trying to build my application it is throwing error in Debug Schema but the same is working for Release Schema . I am attaching the supporting image for reference. Can anyone please help me with this ?

Update: Turns out it works for others, apparently, and I also found one of my Macs where it does work, too. So it must be something pertinent to my systems. Oddly, though, the same ones where it now fails used to work because I had TestFlight enabled there before. I have TestFlight set up on App Store Connect, and I have already about 50 testers subscribed. Today, I found that the Public Link does not work any more: Once TestFlight.app is installed, and one clicks the link to add my app to TestFlight, it always shows the error ""Unable to Open Link" in TestFlight.app: I've tried this on several Macs (Ventura and Sonoma), and with different Accounts, both where the app was already added or not. Is something generally broken, i.e. do others see the same issue with their TestFlight links, or is it just me? How do you suggest I get this resolved? Here's an example link I set up for this purpose - it only allows a handful of subscribers, so please do not actually subscribe but just see if you even get allowed to, or if you get the same error if you must try: https://testflight.apple.com/join/oV8NNojg And here's how it's set up:

Introduction The current iteration of dynamic weather wallpapers, while functional, has become visually stagnant. With the rapid advancement of Generative AI, there is a significant opportunity to transform these backgrounds from simple realistic simulations into dynamic, artistic experiences. The Core Concept The proposal is to replace or supplement standard weather backgrounds with AI-generated Vector Art that evolves in real-time. Instead of a static image, the wallpaper would be a living piece of art that adapts to: Local Time: Seamlessly transitioning from dawn's golden hues to midnight’s deep blues. Weather Conditions: Using distinct vector animations for rain, thunderstorms, or heatwaves. Location-Specific Context: Incorporating stylized vector landmarks of the user's current city. Key Features Artistic Variation: Users could choose from various styles, such as Minimalist, Flat Design, Isometric, or Cyberpunk, making the phone interface feel like a curated gallery. Information at a Glance: The vector elements themselves could convey data. For example, the intensity of "wind" animations could reflect actual wind speeds, or the "sun's" position could represent the actual UV index. Emotional Connection: Unlike realistic photos, vector art provides a "vibe" that is less cluttered and more visually soothing, improving the overall user experience and aesthetics of the Lock Screen. Conclusion Integrating AI-driven vector animations would make the Weather Wallpaper not just a tool, but a signature design feature. It would bridge the gap between utility and art, making every glance at the phone a unique experience.