After changing Xcode 16.2 with min iOS 15.
I got error in debug mode
Assertion failed: (reconstituted == accumulator), function setFixup64, file OutputFile.cpp, line 2975.
But project still can archive to IPA.
Anyone has the same issue as me?
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello!
We're working on a large app with over 400 modules in both Swift and Objective-C, totaling more than 3 million lines of code. Since the release of Xcode 15 and 16 this summer, we’ve been experiencing issues with LLDB that have made debugging practically impossible.
Here are some of the problems we’re facing:
The first breakpoint takes a very long time to hit.
When using 'po self', we encounter the following error:
error: type for self cannot be reconstructed: type for typename "$s5MyModule10PlayerViewCD" was not found (cached)
error: Couldn't realize Swift AST type of self. Hint: using `v` to directly inspect variables and fields may still work.
We get numerous log messages like this:
Debugging will be degraded due to missing types. Rebuilding the project will regenerate the needed module files.warning: (arm64) /Users/egormerkushev/Library/Developer/Xcode/DerivedData/App-enhtbwiyebmjsffoqkqhhpshsfia/Build/Products/Debug-iphoneos/MyModule.framework/MyModule(UploadConfiguration.o) 0x000000000000079d: unable to locate module needed for external types: /Users/builder/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/169D1N0MIKBUI/Security-3BRN4UPIIGHME.pcm
error: '/Users/builder/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/169D1N0MIKBUI/Security-3BRN4UPIIGHME.pcm' does not exist
In the Derived Data folder, we find files with hash-like names, such as:
Security-3JM2E93YFDLZNYHWPPIMWNENB.d
Security-3JM2E93YFDLZNYHWPPIMWNENB.dia
Security-3JM2E93YFDLZNYHWPPIMWNENB.pcm
Security-3JM2E93YFDLZNYHWPPIMWNENB.scan
Security-3NAAT3MGN7XY96KVJW529HR41.d
Security-3NAAT3MGN7XY96KVJW529HR41.dia
Security-3NAAT3MGN7XY96KVJW529HR41.pcm
Security-3NAAT3MGN7XY96KVJW529HR41.scan
Security-3RJH8STJC01N1KKN7JCY1WK7F.d
Security-3RJH8STJC01N1KKN7JCY1WK7F.dia
Security-3RJH8STJC01N1KKN7JCY1WK7F.pcm
Security-3RJH8STJC01N1KKN7JCY1WK7F.scan
Security-3TILE9XTY0B8UV9VYL7Y0MJN.d
Security-3TILE9XTY0B8UV9VYL7Y0MJN.dia
Security-3TILE9XTY0B8UV9VYL7Y0MJN.pcm
Security-3TILE9XTY0B8UV9VYL7Y0MJN.scan
Security-3ZE8O6ZPHE4L52UZGL0PCBA59.d
Security-3ZE8O6ZPHE4L52UZGL0PCBA59.dia
...
When enabling LLDB logs with:
log enable -f /tmp/lldb.log lldb all
we end up with a 1.5GB log file containing hundreds of thousands of error messages.
Finally, the LLDB console output in Xcode ends with errors like:
error: Assertion failed: (byte_size > 0 && byte_size <= 8 && "GetMaxU64 invalid byte_size!"), function GetMaxU64, file DataExtractor.cpp, line 527
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0 LLDB 0x0000000116ccfe1c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56
1 LLDB 0x000000011682fdcc lldb_private::lldb_assert(bool, char const*, char const*, char const*, unsigned int) + 148
2 LLDB 0x000000011682944c lldb_private::DataExtractor::GetMaxU64(unsigned long long*, unsigned long) const + 72
3 LLDB 0x00000001167335a8 lldb_private::CompilerType::GetValueAsScalar(lldb_private::DataExtractor const&, unsigned long long, unsigned long, lldb_private::Scalar&, lldb_private::ExecutionContextScope*) const + 304
4 LLDB 0x000000011666f0f4 lldb_private::Value::ResolveValue(lldb_private::ExecutionContext*, lldb_private::Module*) + 388
5 LLDB 0x0000000116671e94 lldb_private::ValueObject::ResolveValue(lldb_private::Scalar&) + 104
6 LLDB 0x0000000116674d6c lldb_private::ValueObject::GetValueAsSigned(long long, bool*) + 140
7 LLDB 0x000000011650510c lldb::SBValue::GetValueAsSigned(long long) + 160
8 lldb-rpc-server 0x00000001025ebe70 rpc_server::_ZN4lldb7SBValue16GetValueAsSignedEx::HandleRPCCall(rpc_common::Connection&, rpc_common::RPCStream&, rpc_common::RPCStream&) + 92
...
13 libsystem_pthread.dylib 0x00000001917fb2e4 _pthread_start + 136
14 libsystem_pthread.dylib 0x00000001917f60fc thread_start + 8
Please file a bug report against lldb reporting this failure log, and as many details as possibleerror: Assertion failed: (byte_size > 0 && byte_size <= 8 && "GetMaxU64 invalid byte_size!"), function GetMaxU64, file DataExtractor.cpp, line 527
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0 LLDB 0x0000000116ccfe1c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56
1 LLDB 0x000000011682fdcc lldb_private::lldb_assert(bool, char const*, char const*, char const*, unsigned int) + 148
2 LLDB 0x000000011682944c lldb_private::DataExtractor::GetMaxU64(unsigned long long*, unsigned long) const + 72
3 LLDB 0x00000001167335a8 lldb_private::CompilerType::GetValueAsScalar(lldb_private::DataExtractor const&, unsigned long long, unsigned long, lldb_private::Scalar&, lldb_private::ExecutionContextScope*) const + 304
4 LLDB 0x000000011666f0f4 lldb_private::Value::ResolveValue(lldb_private::ExecutionContext*, lldb_private::Module*) + 388
5 LLDB 0x0000000116671e94 lldb_private::ValueObject::ResolveValue(lldb_private::Scalar&) + 104
6 LLDB 0x0000000116674c44 lldb_private::ValueObject::GetValueAsUnsigned(unsigned long long, bool*) + 140
7 LLDB 0x0000000116505224 lldb::SBValue::GetValueAsUnsigned(unsigned long long) + 160
8 lldb-rpc-server 0x00000001025ebf18 rpc_server::_ZN4lldb7SBValue18GetValueAsUnsignedEy::HandleRPCCall(rpc_common::Connection&, rpc_common::RPCStream&, rpc_common::RPCStream&) + 92
9 lldb-rpc-server 0x00000001025f62b8 rpc_common::Connection::PrivateHandleRPCPacket(rpc_common::RPCPacket&, rpc_common::RPCPacket&, bool&) + 628
10 lldb-rpc-server 0x00000001025f9e8c Packets::ProcessPackets() + 564
11 lldb-rpc-server 0x00000001025f9bf4 Packets::ReadThread() + 276
12 lldb-rpc-server 0x00000001025f9ad4 Packets::RunReadThread(void*) + 12
13 libsystem_pthread.dylib 0x00000001917fb2e4 _pthread_start + 136
14 libsystem_pthread.dylib 0x00000001917f60fc thread_start + 8
Please file a bug report against lldb reporting this failure log, and as many details as possiblePrinting description of self:
error: type for self cannot be reconstructed: type for typename "$s5MyModule10PlayerViewCD" was not found (cached)
error: Couldn't realize Swift AST type of self. Hint: using `v` to directly inspect variables and fields may still work.
In short, our debugger is completely unusable at this point, which is severely impacting our team's ability to develop effectively.
Do you have any suggestions on how we can resolve these issues? We would really appreciate your help. Thank you!
Hello!
I'm experiencing a persistent SwiftCompile warning that I haven't been able to resolve for several months:
<unknown>:0: warning: default will never be executed
Observations:
Appears randomly across different files during the build.
No source location or line highlighting is provided.
Persists across clean builds and project reopenings.
Occurs in both Xcode Cloud and local builds.
What I’ve tried:
Ensuring all switch statements on enums explicitly handle every case.
Removing default cases from fully covered enum switches.
Refactoring optional enum handling (e.g., using if let instead of switch).
None of these resolved the issue. Any guidance would be greatly appreciated!
Project details:
Xcode: 16.2
Swift: 6
iOS Target: 17.0+
UI: SwiftUI-only (no UIKit)
Dependencies: SwiftPM
When I finished updating the system (Mac: 15.3.1 (24D70) Xcode: Version 16.2 (16C5032a)), the following situation occurred in the Archive package:
Termination Description: DYLD, symbol '_objc_claimAutoreleasedReturnValue' not found, expected in '/usr/lib/libobjc.A.dylib', needed by '/private/var/containers/Bundle/Application/60C6E2BE-661A-4BA9-98CC-6C222F20452B/Blurams.app/Blurams'
Highlighted by Thread: 0
A startup crash occurs on a system with iOS16 or earlier
How to solve this problem? The issue is currently blocking the release of the version
Topic:
Developer Tools & Services
SubTopic:
Xcode
Xcode 16.2 (and also Apple Configurator) randomly stopped working since today morning.
Upon opening, the application crashes -> "unexpectedly quit".
I've tried restarting the Mac, I reinstalled Xcode, still the same issue.
This issue is currently on my MacBook Pro M4 on macOS Sequoia 15.3.1.
Problem Reporter shows:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Xcode [5577]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 16.2 (23507)
Build Info: IDEApplication-23507000000000000~2 (16C5032a)
App Item ID: 497799835
App External ID: 870964517
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-03-07 00:27:05.7449 +0100
OS Version: macOS 15.3.1 (24D70)
Report Version: 12
Anonymous UUID: ---------
Time Awake Since Boot: 10000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Xcode [5577]
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1975ff720 __pthread_kill + 8
1 libsystem_pthread.dylib 0x197637f70 pthread_kill + 288
2 libsystem_c.dylib 0x197544908 abort + 128
3 Xcode 0x1009af550 main.cold.1 + 28
4 Xcode 0x1009af374 main + 448
5 dyld 0x1972b8274 start + 2840
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x0000600000841120 x6: 0x000000000000000a x7: 0x0000000000000001
x8: 0x61ac7d1cc0e801aa x9: 0x61ac7d1ec01289ea x10: 0x0000000000000005 x11: 0x0000000000000005
x12: 0x000060000244c050 x13: 0x0000000000000000 x14: 0x000000019789a81d x15: 0x0000000200fc05b0
x16: 0x0000000000000148 x17: 0x00000002095ea2c0 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x0000000000000103 x21: 0x0000000200fa8920 x22: 0x0000000200fafd38 x23: 0x000000012b004230
x24: 0x00000001972b2000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000
x28: 0x0000000000000000 fp: 0x000000016f453870 lr: 0x0000000197637f70
sp: 0x000000016f453850 pc: 0x00000001975ff720 cpsr: 0x40000000
far: 0x0000000000000000 esr: 0x56000080 Address size fault
Binary Images:
0x1009ac000 - 0x1009affff com.apple.dt.Xcode (16.2) <81ab48b8-11be-3fa2-9be2-a5d6494288a5> /Applications/Xcode.app/Contents/MacOS/Xcode
0x1975f6000 - 0x197630ff7 libsystem_kernel.dylib (*) <eee9d0d3-dffc-37cb-9ced-b27cd0286d8c> /usr/lib/system/libsystem_kernel.dylib
0x197631000 - 0x19763dfff libsystem_pthread.dylib (*) <642faf7a-874e-37e6-8aba-2b0cc09a3025> /usr/lib/system/libsystem_pthread.dylib
0x1974cb000 - 0x19754cffb libsystem_c.dylib (*) <92699527-645f-3d8d-aed8-1cfb0c034e15> /usr/lib/system/libsystem_c.dylib
0x1972b2000 - 0x197333f3f dyld (*) <398a133c-9bcb-317f-a064-a40d3cea3c0f> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
0x1976a3000 - 0x197b97fff com.apple.CoreFoundation (6.9) <190e6a36-fcaa-3ea3-94bb-7009c44653da> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=884.0M resident=0K(0%) swapped_out_or_unallocated=884.0M(100%)
Writable regions: Total=804.5M written=320K(0%) resident=320K(0%) swapped_out=0K(0%) unallocated=804.1M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Kernel Alloc Once 32K 1
MALLOC 796.2M 18
MALLOC guard page 96K 6
STACK GUARD 56.0M 1
Stack 8176K 1
__AUTH 1098K 205
__AUTH_CONST 18.3M 351
__DATA 4587K 332
__DATA_CONST 13.1M 354
__DATA_DIRTY 692K 110
__FONT_DATA 2352 1
__LINKEDIT 606.2M 2
__OBJC_RW 2374K 1
__TEXT 277.8M 368
__TPRO_CONST 272K 2
page table in kernel 320K 1
shared memory 32K 1
=========== ======= =======
TOTAL 1.7G 1755
Topic:
Developer Tools & Services
SubTopic:
Xcode
My preview crashes whenever I compare my model's value to a constant's stored value.
I use struct constants with a stored value as alternatives to enums, (IIRC ever since the beginning) enums never worked at all with .rawValue or computed properties.
This crashes when it runs on Xcode 16.3 beta and iOS 18.4 in previews. It doesn't appear to crash in simulator.
@Model class Media {
@Attribute(.unique) var id: UUID = UUID()
@Attribute var type: MediaType
init(type: MediaType) {
self.type = type
}
static var predicate: (Predicate<Media>) {
let image = MediaType.image.value
let predicate = #Predicate<Media> { media in
media.type.value == image
}
return predicate
}
}
struct MediaType: Codable, Equatable, Hashable {
static let image: MediaType = .init(value: 0)
static let video: MediaType = .init(value: 1)
static let audio: MediaType = .init(value: 2)
var value: Int
}
My application crashes with "Application crashed due to fatalError in Schema.swift at line 320."
KeyPath \Media.<computed 0x000000034082a33c (MediaType)>.value points to a field (<computed 0x000000034082a33c (MediaType)>) that is unknown to Media and cannot be used.
This appears to also occur if I am using a generic/any func and use protocols to access a property which is a simple String, such as id or name, despite it being a stored SwiftData attribute.
I filed a bug report, but looking to hear workarounds.
Since iOS 18.2 the simulators have been missing the content under Apps menu for Settings. We are on to iOS 18.3 and still no Apps settings.
@dts
Hello!
I'm working on implementing SwiftUI + StoreKit2 IAP in my app, and Xcode testing has been fantastic, now I'd like to test my app with Sandbox, where I created a Sandbox account, and it works on my physical device, I can log in, make transactions, etc. (btw, feedback: please improve the UX for Sandbox testing, it's really clumsy compared to Xcode testing with Transaction Manager)
My problem is that when I'd like to log in with my Sandbox account on the simulator (Settings -> Developer -> Sandbox Apple Account (at the bottom) -> Sign in), it doesn't work, it fails silently. I know it authenticates well, because if I type in the wrong password, I get an error popup, but with the right password, it just fails silently, hides the login sheet and the "Sign in" text remains "Sign in" (on my phone when I log in, the "Sign in" is replaced with the email address of the Sandbox account).
I know many people get errors, and they recommend to go icloud.com and acccept TOS (done that), also to download the latest iOS for the simulator (also done), these are not a problem for me, as I don't get any errors. My authentication works, but for some reason the simulator still won't log in, it fails silently, and I see no errors/reason why. Tried with different simulators (latest iOS version), same result, tried to reboot the simulator, same result.
Any idea why is this happening?
Thank you,
sendai
When I try to build my project in Xcode (from Unity AR) project, it throws me these errors:
I feel like I've tried everything to make the LaunchScreen work. I downloaded xcode the night I tried running this build, so the whole deleting and redownloading and restarting everything didn't work. I've tried making sure my macbook and terminal are fully up to date. I literally can't find a solution! Please help!!
I will also say, I'm fairly new to App building, Xcode, and Unity. But this does seem like a barrier that is stopping me from testing my project.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I got this error when I upgraded to Xcode 16.2. Unfortunately, my project doesn't run anymore. Can anyone help me? I've been postponing my deadline for a week now
'/Users/vdngo/Library/Developer/Xcode/DerivedData/TMC-fiptdrksdfjwrwcdphljlfpuvmmy/Build/Intermediates.noindex/PrecompiledHeaders/TMC-Bridging-Header-swift_1IG9GDIWH1MAW-clang_UTPY7SDIWAR0.pch' for bridging header '/Users/vdngo/.../ios/TMC/Others/TMC-Bridging-Header.h'
Topic:
Developer Tools & Services
SubTopic:
Xcode
I have some formatting strings that got in my string catalog, e.g. "%@" or "(%@)".
However these strings are no longer used in my code anywhere (searching "In this project" in Xcode only matches the entries in my strings catalog), but Xcode does not remove them.
I tried editing the file in a text editor, removing them manually but they keep coming back.
Any solution for this?
Xcode Version 15.4 (15F31d)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hi, I currently have an app that connect to an arduno via CoreBluetooth. However, the app no longer discovers the arduino when the operating system was upgraded to iOS 18.3.1, however on iOS version 17.6.1 the ardiuno was discoverable I was able to test this theory on two different phones each with different iOS versions. Why are my peripherals no longer being discovered with this update? and what is the solution?
ive been using the mac m1 for almmost a year and it used to run vision pro simulator on xcode 15 quite smoothly but now its quitting unexpectedly showing errors in loading the realtiykit content
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Reality Composer Pro
visionOS
iPad and iOS apps on visionOS
I just started working with Flutter. I use a Macbook m2 and my phone is an iPhone XR. I made a very simple application but no matter what I did, I couldn't start my application on my iPhone XR. I got help from all the AIs but we couldn't do it. I deleted everything including Xcode, Android Studio and Flutter and reinstalled them and I followed the SDK installation step by step on the Flutter page but I can't run my project on Xcode. I entered my Apple account including all the signings and certificates via the .workspace file extension but it didn't work. The error I get from Xcode keeps changing. We installed podfiles with the support I got from the AIs and after some fiddling, I got the only error right now: Command PhaseScriptExecution failed with a nonzero exit code
Hi,
Our team is facing an issue where the os log message is not fully printed in the Xcode console. Even when using Debug → Attach to Process by PID or Name, the logs appear truncated (Both simulator and physical device).
We noticed that the Xcode 15.0 release notes we saw that there is some truncation made for debug lines in console. We also tried checking the logs using Console.app, but the truncation remains.
If limitation is there how much maximum lines it can print ?
Could anyone please provide guidance on how we can view the complete logs? Any suggestions or workarounds would be highly appreciated.
I received the attached crash report. The problem is that the crash report does not contain the abort reason - it appears to be thrown in the GCD library with no additional information.
Is it a possible deadlock?
2023-02-15_02-40-23.0077_+0100-94015bd052c4005658221a5e6279f28a75b9e92c.crash
Any ideas?
Hi, I currently have an app that connect to an arduno via CoreBluetooth. However, the app no longer discovers the arduino when the operating system was upgraded to iOS 18.3.1, however on iOS version 17.6.1 the ardiuno was discoverable I was able to test this theory on two different phones each with different iOS versions. I see that it is failing to find the peripheral at the scan however the logs indicate that the central state is powered on. Why are my peripherals no longer being discovered with this update? and what is the solution?
I'm using a CMake project and Xcode decided that it would ignore or completely change my file tree to some random one. It has Source files (not a folder in my project) and completely ignores my class folder and header folder. It created it's own Header Files folder.
How do I revert this? Why is this even a thing.
I am experiencing a crash when performing a batch delete and merging changes on a Core Data store that uses NSPersistentCloudKitContainer. The crash appears to be triggered when positive fractional Decimal values are stored in a TransactionSplit entity (those values are aggregated via a derived attribute in the AccountTransaction entity). If I store whole numbers or negative fractional decimals, deletion seems to work correctly. I suspect that the issue is related to the internal representation of positive fractional decimals in conjunction with a derived attribute.
Data Model Setup:
Account (1:N relationship → AccountTransaction)
AccountTransaction (1:N relationship → TransactionSplit), which contains a derived attribute (e.g., “splits.amount.@sum”) that computes the sum over the “amount” attribute on its related TransactionSplit objects.
TransactionSplit, which contains a stored Decimal attribute named “amount” (of type Decimal/NSDecimalNumber).
Steps to Reproduce:
Insert sample data where each TransactionSplit’s “amount” is set to a positive fractional value (e.g., 1000.01), by using code similar to:
func createSampleData() {
// Execute all creation on the context’s queue.
let checkingAccount = Account(context: context)
checkingAccount.id = UUID()
checkingAccount.name = "Main Checking"
let randomTransactionCount = 1000
for _ in 0..<randomTransactionCount {
let transaction = AccountTransaction(context: context)
transaction.id = UUID()
transaction.account = checkingAccount
let randomValue = Double.random(in: 5...5000)
let decimalValue = NSDecimalNumber(value: randomValue)
let split1 = TransactionSplit(context: context)
split1.id = UUID()
split1.amount = decimalValue
split1.transaction = transaction
let split2 = TransactionSplit(context: context)
split2.id = UUID()
split2.amount = decimalValue
split2.transaction = transaction
}
save()
}
The AccountTransaction’s derived attribute automatically aggregates the sum of its related TransactionSplit amounts.
Perform a batch deletion using NSBatchDeleteRequest (with resultType set to .resultTypeObjectIDs) on your entities and merge the changes back into your main context:
private func delete(_ fetchRequest: NSFetchRequest<NSFetchRequestResult>) {
let batchDeleteRequest = NSBatchDeleteRequest(fetchRequest: fetchRequest)
batchDeleteRequest.resultType = .resultTypeObjectIDs
// ⚠️ When performing a batch delete we need to make sure we read the result back
// then merge all the changes from that result back into our live view context
// so that the two stay in sync.
if let delete = try? context.execute(batchDeleteRequest) as? NSBatchDeleteResult {
let changes = [NSDeletedObjectsKey: delete.result as? [NSManagedObjectID] ?? []]
NSManagedObjectContext.mergeChanges(fromRemoteContextSave: changes, into: [context])
}
}
Save the context after deletion.
I'm trying to improve my build time on macOS by not building for x86_64. I've got the following settings:
This gets Xcode not to build x86_64 for my app, but not all the package dependencies.
I've updated most of the packages to swift-tools-version: 6.0 but FlatBuffers is still on 5.8 and .macOS(.v10_14). GPT claims:
If your deployment target is set to macOS 10.15 or earlier, Xcode may force x86_64 support for compatibility reasons.
But Xcode is building x86_64 for ALL my packages, even the ones that don't depend on FlatBuffers.
When I open a package in Xcode that depends on FlatBuffers, then it builds arm only, so that may be a red herring.
Not sure what else to try.