Search results for

build disappears

49,353 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode26 Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5196
Had the same problem Xcode 26.0.1, Unity 6000.2.6f2. Searched the forums and tried couple of methods, finally the following worked. Min version to 16.0 Other Linker Flags in target Build, removed -ld64. Other Linker Flags in UnityFramework Build, removed -ld64. Kept the rest of the flags. Clean build, cleaned Derived Data. Compiled and it worked. Hope it will be the same for you.
3w
What does it take for an app Window menu list to display the new items like Move & Resize?
Here's the result of a blank app from Xcode: https://imgur.com/a/1hMmwbO now there's only 3 items in the storyboard configuration: https://imgur.com/a/iGWWQE7 So I try to replicate that in code (some of this reproducer was generated by ChatGPT however the same issue I'm descrbing has been hit when using Python to objc bridges to construct the GUI) by specifying these 3 actions appropriately and see if the rest pops up. The code below changes the activation policy so that when I run ./a.out from the terminal it doesn't show as a window of Terminal but a separate app #import @interface AppDelegate : NSObject @end @implementation AppDelegate - (void)applicationDidFinishLaunching:(NSNotification *)notification { // Build main menu NSMenu *mainMenu = [[NSMenu alloc] initWithTitle:@MainMenu]; // --- App menu with Quit --- NSMenuItem *appMenuItem = [[NSMenuItem alloc] init]; NSMenu *appMenu = [[NSMenu alloc] initWithTitle:@App]; NSMenuItem *quitItem = [[NSMenuItem alloc] initWithTitle:@Quit action:@select
Topic: UI Frameworks SubTopic: AppKit
2
0
110
3w
ShazamKit for Android and 16 KB native library alignment
Hello, I'm working on a Flutter app targeting both Android and iOS, where I implemented ShazamKit. In order to achieve that, I first tried with the flutter_shazam_kit package, but since it's not maintained anymore, I forked it here, and tried to update it to meet the Google Play Store requirements, as you can see here: https://github.com/mregnauld/flutter_shazam_kit/tree/fix-16k Unfortunately, after trying everything, my app still doesn't meet the (not so) new 16 KB native library alignment. Also, I'm 100% sure it comes from that because the error message disappears if I remove that package from my app. So after investigating, it seems that the problem comes from the ShazamKit for Android (that you can find here: https://developer.apple.com/download/all/?q=Android%20ShazamKit), and especially the .so files in the .aar file. Is there anything I can do to fix that, or should I wait before the ShazamKit team fix that? I'm totally stuck with that so any help is highly appreciated. Thanks.
3
0
476
3w
Reply to ShazamKit for Android and 16 KB native library alignment
For your info, I made some updates to my fix-16k branch. Also, after investigating more (thanks to Claude Code), here what seems to happen: ShazamKit AAR contains libraries with 16KB alignment (0x4000) During Android build, these libraries are re-aligned to 4KB (0x1000) The Android Gradle Plugin's strip/packaging process is changing the alignment So, are we sure that ShazamKit Android AAR has been verified to work with AGP 8.5.1+ and maintains 16KB alignment through the full build process? Maybe I missed something but at this point, I really don't know.
Topic: Media Technologies SubTopic: General Tags:
3w
.disabled() doesn't VISUALLY disable buttons inside ToolbarItem on iOS 26 devices
[Also submitted as FB19313064] The .disabled() modifier doesn't visually disable buttons inside a ToolbarItem container on iOS 26.0 (23A5297i) devices. The button looks enabled, but tapping it doesn't trigger the action. When deployment target is lowered to iOS 18 and deployed to an iOS 18 device, it works correctly. It still fails on an iOS 26 device, even with an iOS 18-targeted build. This occurs in both the Simulator and on a physical device. Screen Recording Code struct ContentView: View { @State private var isButtonDisabled = false private var osTitle: String { let version = ProcessInfo.processInfo.operatingSystemVersion return iOS (version.majorVersion) } var body: some View { NavigationStack { VStack { Button(Body Button) { print(Body button tapped) } .buttonStyle(.borderedProminent) .disabled(isButtonDisabled) Toggle(Disable buttons, isOn: $isButtonDisabled) Spacer() } .padding() .navigationTitle(Device: (osTitle)) .navigationBarTitleDisplayMode(.large) .toolbar { ToolbarItem { Button(Toolba
7
0
358
3w
Reply to Xcode not showing devices as run destination
I'll explain what I experienced and how I solved it. iPhone was not detectable in any way (nor was the apple watch), I tried getting latest beta of Xcode, I tried latest stable release, nothing seemed to work. I waited for final release which came up shortly and still no luck. What ended up working was a thunderbolt cable. I went to an Apple Store and they told me to wipe the phone completely because I still had the beta installed, which attending to build number was wrong, but something was off so I wiped the phone. That fixed the issue, although I lost a couple of pictures and some minor data for apps that didn't save it in cloud. Hope this helps someone in the future :) As a side note, debugging on an Apple Watch is becoming really really difficult... sometimes it just does not want to connect
3w
Metal is not installed on Xcode 26 on Xcode Cloud
Hi there, We’re encountering this error in all of our builds when using the latest Xcode and macOS: The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. In short, all builds are failing. I’ve tried fixing this by installing Metal and applying other solutions, but none of them worked reliably. Is there a way to ensure that the Metal Toolchain is installed on the CI machine?
7
0
554
3w
Reply to Fous, FocusState and Architecture
Your post is extremely interesting and definitely requires more thought on my part. It seems that what you're doing is to build a FocusCoordinator, conceptually similar to a Navigation Coordinator (although I think that there may be some missing APIs preventing a comprehensive solution. My immediate interest is on tab-navigation and I have some new information to offer about it. It turns out that in most cases, sending a to a focueed TextField will cause focus to change, BUT if the TextField is instantiated with the axis: AXIS parameter, the is added to the TextField body instead. I don't know how Apple will classify it, but I'm calling this a bug and have reported it. (FB20505919).
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3w
Reply to DeclaredAgeRange import error in Mac Catalyst app
Thanks for the guidance. I added screenshots just to show the situation more clearly: On iOS devices the app builds and runs fine with import DeclaredAgeRange. On Mac (Catalyst) the same code fails with an import error. I also looked into filing a Feedback report, but honestly the procedure felt quite complex, and I stopped midway. I understand that Apple wants to filter out low-quality reports, but from the perspective of a busy app developer it’s hard to dedicate that much time to reporting SDK issues. So please consider this thread as a reference. For now, I’ll conditionally compile the feature with #if canImport(DeclaredAgeRange) and ship the app that way.
3w
Error accessing backing data on deleted item in detached task
I have been working on an app for the past few months, and one issue that I have encountered a few times is an error where quick subsequent deletions cause issues with detached tasks that are triggered from some user actions. Inside a Task.detached, I am building an isolated model context, querying for LineItems, then iterating over those items. The crash happens when accessing a Transaction property through a relationship. var byTransactionId: [UUID: [LineItem]] { return Dictionary(grouping: self) { item in item.transaction?.id ?? UUID() } } In this case, the transaction has been deleted, but the relationship existed when the fetch occurred, so the transaction value is non-nil. The crash occurs when accessing the id. This is the error. SwiftData/BackingData.swift:1035: Fatal error: This model instance was invalidated because its backing data could no longer be found the store. PersistentIdentifier(id: SwiftData.PersistentIdentifier.ID(backing: SwiftData.PersistentIdentifier.PersistentIdentifierBacki
1
0
134
3w
Reply to Xcode shows alert about unknown com.apple.quicklook.preview extension point when running on Apple Vision Pro Simulator
I did a sanity check and looked in Xcode, in the templates for a new target, I don't see 'Quick Look Preview Extension' in the visionOS' list (I do see 'thumbnails'). Could it not be possible yet? That would explain why no issues when making the app 'designed for iPad'. I suppose the issue disappears if you remove vision as a target for the quick look extension.. but maybe you want the extension in visionOS as well. I read some more and I came to the conclusion that the Quick Look preview extensions are not yet for visionOS, but only someone from Apple can confirm that.
3w
xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies
I'm working on a large multi-platform iOS project (iOS, iPadOS, watchOS, tvOS, visionOS) and have successfully migrated from legacy .strings files to modern String Catalogs (.xcstrings). However, I'm unable to export localizations using xcodebuild -exportLocalizations due to cross-platform framework dependency issues. (Note: I did have AI help me write this question, so apologies in advance for any errors) Project Structure Main iOS/iPad app with multiple extensions watchOS companion app tvOS app visionOS app 49 .xcstrings files successfully migrated across all targets Uses Swift Package Manager for modularization The Problem When attempting to export localizations using xcodebuild -exportLocalizations, the build fails because it tries to build all targets across all platforms, including watchOS targets that depend on third-party xcframeworks that don't include watchOS slices: xcodebuild -exportLocalizations -project MyProject.xcodeproj -scheme MyApp -localizationPath ./export -configura
5
0
180
3w
Reply to xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies
Thank you for the info! This doesn't seem to affect our normal build because the relevant watch packages don't depend on the libraries that aren't compatible. But for some reason when -exportLocalization flag is added, it attempts to build ALL targets for watch since that's declared as a platform at the top. This makes sense to me now. Xcode does indeed attempt to build each target in the package for all platforms listed in that package. The reason changing those build settings didn't work for you is because they would need to be set on the relevant package targets themselves (not the dependencies), but packages do not allow setting arbitrary build settings. Please file a Feedback report requesting that the Export feature avoid building package targets for platforms that their dependencies do not support. A sample project is helpful but not required since we now understand what the problem is.
3w