I know this is fixed in iOS 26.1, but... what I've seen is that this requires also macOS min version of 26.1 for Tahoe and 15.7.x for Sequoia. Although you use the latest iOS 26.1 version, it's not working with macOS 26.0. Is there any dependence with the underlying macOS that makes this problem (of not receiving a APNS token) again reproducible on non updated macOS? That's a problem we have with our current CI (Bitrise).

Just using this workaround with 15.0 version, and still broken in Xcode 15.1 Beta1.

@alexanderwe ok, good to know. Probably this situation is also reproducible in other scenarios. Can you check in your logs, this "Process Framework.xcframework" line in the Prepare build step is duplicated too?

@alexanderwe Can you confirm you´re using Cocoapods in your project? I found a fix for my demo project based in removing the customization on the CONFIGURATION_BUILD_DIR variable that CP does in the Module.release.xcconfig file. CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER = NO # This generates a duplication in the framework generation as you can see in the attached image # CONFIGURATION_BUILD_DIR = ${PODS_CONFIGURATION_BUILD_DIR}/Library1 GCC_PREPROCESSOR_DEFINITIONS = $(inherited) COCOAPODS=1 LIBRARY_SEARCH_PATHS = $(inherited) "${DT_TOOLCHAIN_DIR}/usr/lib/swift/${PLATFORM_NAME}" /usr/lib/swift

Here your can find a really simple project that reproduces the problem: https://github.com/osrufung/DuplicatedSignatureXcode15IssueDemoProject

Does anyone have a reproducible test project? I can try to generate one. This is really blocking our iOS17 migration process.

I use binary .xcframeworks for multiple internal libraries too, but that´s happening only in one of them. I can reproduce in Xcode 15.0 beta 2.

Thank you, I´ve included one of the crashes we receive in the Xcode Organizer: 2023-05-23_16-42-07.6249_+0200-cda5fd36efc8d2b68cefdf75451f843003a06fda.crash