Search results for

build disappears

49,310 results found

Post

Replies

Boosts

Views

Activity

DeclaredAgeRange import error in Mac Catalyst app
Hello, I’m developing an app for both iOS and macOS using Mac Catalyst. On the iOS target, the DeclaredAgeRange framework works fine: I enabled the capability, set the entitlement, and can call the APIs successfully. However, when I build the Mac Catalyst target, I get compile-time errors because DeclaredAgeRange cannot be imported. Environment Xcode 26.0.1 Deployment Target (iOS): 13.0 Mac Catalyst target enabled (same bundle ID, same source code base as iOS version) iOS build works well with DeclaredAgeRange What I tried Added the Declared Age Range capability in Signing & Capabilities for iOS target → works fine. Tried setting Mac Catalyst Deployment Target to macOS 15.0+ and rebuilding → still failed to import. Because it didn’t help, I reverted and removed the separate macOS target setting. On Catalyst, the module simply isn’t available (import DeclaredAgeRange fails). From Apple’s documentation, my understanding is that DeclaredAgeRange should also be supported on Mac Catalyst (SDK
Topic: App & System Services SubTopic: General
6
0
194
3w
Reply to Instructions for debugging recent macos kernel versions?
That was it - I built a kext collection using these pre-shipped kernels in the KDK and I was then able to boot this custom kext collection without any issues. I used the kernel.development variant for my test. Upon boot, I even verified that it was indeed using the development variant of the kernel: Fabulous! (including hopefully building a trivially modified kernel version from xnu sources and booting it) It's been a very long time since I've done this, but the main thing I remember is that you need to be very careful to ensure that you've exactly matched up versions so that everything is the same exact version (kernel source, KDK, developer tools, etc.). The problem isn't so much that it MUST be the same, it's that there are so many details and every failure basically looks the same (it doesn't boot!). That makes it really easy to waste a ton of time trying to hunt down small problems that are basically just noise. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Core OS Tags:
3w
Issue with StoreKit 2 Purchases: "unfinalized statements / unfinished backups" SQLite Crash
Hi, I’m running into a persistent error while implementing StoreKit 2 renewable subscriptions in my SwiftUI app. Context I have a two-screen flow: Screen 1: user selects a subscription plan (monthly / yearly). Screen 2: user fills out personal information and taps Subscribe that triggers the purchase function. On first launch or the first couple of purchases (on both Storekit's local and Sandbox testing), everything works fine. The App Store popup appears, the purchase goes through, and I get the transaction result. But after a few runs (3rd or 4th purchase attempt onward), my app crashes the moment the App Store purchase popup appears. Error Logs When the crash happens, the console shows: `unable to close due to unfinalized statements or unfinished backups BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /private/var/mobile/Containers/Data/Application/D8D97A11-DF06-4EF2-AC55-138C4739A167/Library/d6d2e85a60f0480c4c17834eeb827a14_MPDB.sqlite inval
Topic: App & System Services SubTopic: Tap to Pay on iPhone Tags:
1
0
64
3w
Reply to Xcode 26.0 unknown type name 'sqlite3_context'
The file shown in your screenshot is part of the iOS SDK, so it does not normally have compile errors like this. That indicates that the problem is elsewhere in your build configuration, and this file is an innocent victim of a problem elsewhere. I see a build error that says failed to emit precompiled module, so maybe start there and work backwards. Since your project involves Cocoapods, it's possible that tool's configuration is also adding to this issue, so you should work to determine if their configuration set up by their tool is part of the source here, and if that turns out to be the case, you'll want to get in contact with their support resources. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Reply to "Build input file cannot be found" error occurs in Archive.
Can you share the full build report? To collect it: Choose View > Navigators > Reports. Select the report associated with your app’s build in the navigator. Using the filter bar at the top of the build report, select the filter buttons for All and All Messages. Click Export in the filter bar to save the detailed build report. Depending on the size of your app, the report may be too big to attach to a post here in the forums. If that's the case, providing a URL where we can see a copy would also be fine. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Reply to xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies
Hi - thanks for the quick response. I'll try to answer as best as I can. Could you tell me more about these watchOS targets? My primary curiosity is how they are able to build successfully even during a normal build, if their dependencies do not support watchOS. I mentioned at the bottom of my original post that our app is [a mixture of] SPM packages and traditional target structure. This is mostly because SPM was introduced after our app was already published and created. We've slowly been migrating old features to SPM, and new features get added to SPM. The reason we love SPM is it introduces modularity for us, and enables greater code sharing. The way we decided to structure SPM within the context of all of our targets is one shared Package.swift file. This is because so many of our targets share the same code, it seemed easier at the time to keep all our various libraries within one SPM package (I hope that makes sense). So our one Package.swift declares all platforms like this: platform
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Reply to CarPlay Image Issue on iPhone 17?
Thank you for your post. For help with the CarPlay , please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers. https://discussions.apple.com/welcome If you are using a beta version of iOS (please provide the version and build) with CarPlay , please file bug reports through Feedback Assistant. https://feedbackassistant.apple.com/ Hope this helps and you find the solution quickly. Albert Pascual
  Worldwide Developer Relations.
Topic: Community SubTopic: Apple Developers Tags:
3w
Xcode Code coverage shows zero; even after 245 successful tests
I have a project inside the project structure. I have around 300 unit tests in the project. I see that for some of the subprojects, the coverage numbers show up correctly, but for other subprojects and the main project, the coverage number shows zero, even though the tests are running successfully. The log I get is: Aggregation tool emitted warnings: warning: /Users/ABC/Library/Developer/Xcode/DerivedData/projectABC-hfzmkbdgpiswoxfvvnvhrafaiqyb/Build/ProfileData/A8EEC1FB-1699-4C29-A88C-D3DDA226DBC0/0A416494-A393-4319-AA47-502D72084C9C-43351.profraw: raw profile version mismatch: Profile uses raw profile format version = 8; expected version = 10 PLEASE update this tool to the version in the raw profile, or regenerate the raw profile with the expected version. I only have one Xcode (26.0.1) on my machine. I tried cleaning the derived data, the cleaning project, and rerunning the tests, but it hasn't helped. Please help me get the coverage number back. Thank you.
Topic: Developer Tools & Services SubTopic: General Tags:
0
0
60
3w
Background GPU access in iOS 26 for iPhones
We build mobile apps for creators to edit their videos. Post editing the video, the creator has to export the video so that it can be uploaded to Youtube. The export is a time consuming and GPU intensive process. The creator can exit the app due to various reasons like receiving the call, putting the app in background etc. This causes the export to fail :( Keeping this limitation in mind there was an announcement from Apple that with the IOS 26 launch would start to support background GPU access. Here is the official documentation: https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.background-tasks.continued-processing.gpu When we tried using this feature, we were not able to get it to work on IOS 26. We stumbled upon this ticket(https://developer.apple.com/forums/thread/797538?answerId=854825022#854825022) in the Apple Developer forum, in which possibly an Apple engineer claims it is supported ONLY for iPadOS 26. This is a very big bummer for us. 96% of the us
Topic: Media Technologies SubTopic: Video
1
0
172
3w
Reply to Instructions for debugging recent macos kernel versions?
OK, so this is the part I haven't explained as well as I should. You don't actually need to build the kernel, as you already have a development build of the kernel in the KDK. That's what kernel.development.t6020 and kernel.kasan.t6020 installed by the KDK in /System/Library/Kernels are That was it - I built a kext collection using this pre-shipped kernels in the KDK and I was then able to boot this custom kext collection without any issues. I used the kernel.development variant for my test. Upon boot I even verified that it was indeed using the development variant of the kernel: $> sysctl kern.osbuildconfig kern.osbuildconfig: development Thank you very much Kevin for this very valuable help. I have several other things to read and try out (including hopefully building a trivially modified kernel version from xnu sources and booting it), but this initial step had blocked me for several months to even think of these additional experiments. For now, I will just write up these step
Topic: App & System Services SubTopic: Core OS Tags:
3w
Reply to How can I cancel my TestFlight build subscription purchase?
Hello - For the situation you describe, the only possible mechanism for cancelling the subscription purchased in a TestFlight build using a production user account is to have your app call and present the App Store manage subscriptions sheet within the app itself, as documented here. Without that in-app capability, you must wait for the Sandbox subscription to cycle through its expected six (6) renewals before automatically cancelling, as documented here. If the Sandbox subscription purchased through your TestFlight app is not automatically cancelling after 6 renewals as expected, you can provide us with more details (the app name/id, a Sandbox transaction ID, etc.) and we can investigate further to see if the renewals and cancellations are not behaving as expected. Thank you.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
3w
Reply to Enterprise account
Is there a better mechanism for this? We have been trying for 6 months to get an Enterprise Account - We have less than 100 employees, but we are contracting for a company that has a few thousand employees, who wants to MDM the app internally. The web pages to sign up keep kicking the application back, and every time we get an email from a person, it is obvious that no one is actually reading the application. The company we are contracting for logistical reasons CAN NOT USE TESTFLIGHT. They absolutely need it to be an enterprise build. Is there a better link than the one provided, because it’s very frustrating.
Topic: Business & Education SubTopic: General Tags:
3w