“translate scheme”

@DTS Engineer I just tried the SPM version of the package and found out that on release config, it crashes with a undefined symbol. I guess cocoapods masqueraded the issue. When ran with the debug scheme then it runs fine. The Package.swift is defined as follows // swift-tools-version: 5.8 import PackageDescription let package = Package( name: OpacityCore, platforms: [ .iOS(.v13) ], products: [ .library( name: OpacityCore, targets: [OpacityCoreObjc, OpacityCoreSwift]) ], dependencies: [], targets: [ .binaryTarget( name: sdk, path: sdk.xcframework ), .target( name: OpacityCoreObjc, dependencies: [sdk], path: src/objc, publicHeadersPath: ., cSettings: [ .headerSearchPath(../../include) ], linkerSettings: [ .linkedFramework(CoreTelephony), .linkedFramework(CoreLocation), .linkedFramework(WebKit), ] ), .target( name: OpacityCoreSwift, dependencies: [OpacityCoreObjc], path: src/swift ), ] )

Something odd is happening here. Here's a test to run, which I also just did for myself: Create a brand new Xcode project, static library template Set the Skip Install build setting to No since you are using archive builds Run the following commands: % xcodebuild archive -project Test.xcodeproj -scheme Test -destination=generic/iOS Simulator -archivePath /Some/Path/To/Test.xcarchive % otool -l /Some/Path/To/Test.xcarchive/Products/usr/local/lib/libTest.a | grep LC_BUILD_VERSION -A4 If that outputs anything but 7 for the platform, please open a bug report, attach your test project and the exact commands and their output from above, and then post the FB number here for my reference. In my test run with the above, I got platform 2, i.e. iOS, not the simulator, but also not Mac Catalyst as in your original post. — Ed Ford,  DTS Engineer

Yes, the .env is just for testing purposes. This entire app is just a tester app, so some quirks are fine and indeed the file does not cause any issues. Here is the crash report of my latest build crashlog.crash Here is the output of the file command $ file OpacityPod_Example OpacityPod_Example: Mach-O 64-bit executable arm64 $ file Frameworks/sdk.framework/sdk Frameworks/sdk.framework/sdk: Mach-O 64-bit dynamically linked shared library arm64 I'm sure I have ran the app with the Release config (done via changing the scheme and selecting run → release). I just tried the Isolating Code Signig Problems from Build Problems you shared. The development option is not there in Xcode 26, but I chose debugging that generated an .ipa which I installed in my device by dragging and dropping. The crash persists on that version. @DTS Engineer

/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild archive -project netcdf.xcodeproj -scheme netcdf-simulator -destination=generic/iOS Simulator, arch:x86_64, id:AB7A99B3-8D24-4F73-A42D-9BB45321928D -archivePath=archives/netcdf_simulator --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, variant:Mac Catalyst, id:00006041-0008492E3AA1801C, name:My Mac } { platform:macOS, arch:x86_64, variant:Mac Catalyst, id:00006041-0008492E3AA1801C, name:My Mac } { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00006041-0008492E3AA1801C, name:My Mac } { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } { platform:macOS, variant:Mac Catalyst, name:Any Mac } { platform:iOS, arch:arm64, id:00008101-001C61991A90001E, name:August’s iPhone } { platform:iOS Simulator

Hi @DTS Engineer , We have a similar issue in our app. Officially, we support the Croatian language only, so there are no .lproj folders for other languages as we don't want to falsely advertise supported languages on the App Store as the app is translated only to Croatian. When we set the device to Croatian, the button is in Croatian. When we set it to any other language, the button is in English (developer language / CFBundleDevelopmentRegion). So, would you say that that's the expected and okay behavior? We don't have to add .lproj for all 30+ languages iOS support, just to have that one button translated to system language, if we don't want to support all those languages in the app? Thnx!

@DTS Engineer Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project WeSplit.xcodeproj -scheme WeSplit -showdestinations Available destinations for the WeSplit scheme: { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } { platform:iOS Simulator, arch:arm64, id:69BF3E41-8164-4C23-9E15-08003079BF8A, OS:17.2, name:iPad (10th generation) } { platform:iOS Simulator, arch:arm64, id:6418F056-1788-43A7-B86D-923A017763D7, OS:18.6, name:iPad (A16) } { platform:iOS Simulator, arch:arm64, id:46BE4717-0798-4D9E-9F74-58A88107A239, OS:17.2, name:iPad Air (5th generation) } { platform:iOS Simulator, arch:arm64, id:D3F27A4C-4BC0-4031-B4BA-2B626552F111, OS:18.6, name:iPad Air 11-inch (M3) } { platform:iOS Simulator, arch:arm64, id:64AC8DDD-FF66-4805-B4F7-5BC15C15DC3F, OS:18.6, name:iPad Air 13-inc

I've gotten past this issue. My scheme was not set up properly. I was not archiving the iOS Container app.

Would you mind sharing the outputs of the following commands? xcodebuild -project YourProject.xcodeproj -scheme YourScheme -showdestinations xcodebuild -project YourProject.xcodeproj -scheme YourScheme -showBuildSettings — Ed Ford,  DTS Engineer

Is it possible to invoke live translations within the app? (without going into the Call System UI) You can enable/disable translation using CXSetTranslatingCallAction, but that's really the only API control you have. Is it possible to navigate users from app to Call System UI via an API? (and also invoking the new live translations directly) This is something developers have occasionally suggested since we changed CallKit's original behavior* during iOS 10's original beta, however, it might be worth reconsidering API for this give the new APIs options like live translation. Please file a bug asking for this, then post the bug number back here. *Ironically, when we originally introduced CallKit, call reporting automatically brought up the in call UI and we actually changed to the current behavior based on developer feedback during that beta. Will Apple support more languages apart from the current ones? (Currently I see 4 supported languages) That's a question about our futu

Universal Links are generally preferred over custom URL schemes these days. — Ed Ford,  DTS Engineer