Swift 6

Still happens in beta 6

Browser version (Safari): Version 18.6 (20621.3.11.11.3) Team ID: 6........4

The issue persists in iOS 26 Beta 6 (Build 23A5318c). I have attached a new sysdiagnose collected from the latest build for your review in the FB bug.

Another point. In DataView, index should not be a State variable. Add a button in ContentView VStack { if showView && (index >= 0) && (index < data.count) { DataView(datum: data[index]) } Spacer() HStack { Text(Index: (index) -> ) Button(Next) { index += 1 if index >= data.count { index = 0 } } } } You will see that text in DataView does not change Text(DataView (datum.str)) always says DataView String 1 Now change DataView as follows to get it updated on index change by button press: struct DataView: View { /*@State*/ var datum: Data2 var body: some View { Text(DataView (datum.str)) } } Note: I renamed data to datum for an array item, to differentiate from the array. Now, I have to update my initial answer. In fact, no need for showView and Dispatch (even though that made it work). Just test index: if (index < data.count) { DataView(datum: data[index]) Without the index test, it crashes… Swift/ContiguousArrayBuffer.swift:691: Fatal error: Index out of range Reason is t

@DTS Engineer you are right, the KERN_PROTECTION_ERROR really through me off. I updated today to Xcode 26 beta 5 and with my dylib compiled with debug symbols all of the sudden I can see where the null invocation is happening However, I don't have any idea why the compiler is stripping this symbols when packaging for TestFlight/Debugging. I've already added a lot of preprocessor directives to try to keep the symbols intact. Any idea what could I try? #define EXPORT __attribute__((visibility(default), used, retain)) extern C { EXPORT void ios_prepare_request(const char *url) { NSString *urlString = [NSString stringWithUTF8String:url]; request = [NSMutableURLRequest requestWithURL:[NSURL URLWithString:urlString]]; } void force_symbol_registration() { // Force these symbols to be included in the binary by referencing them volatile void *ptrs[] = {(void *)ios_prepare_request, (void *)ios_set_request_header, (void *)ios_present_webview, (void *)ios_close_webview, (void *)ios_get_browser_cookies_for_current_url, (v

Thanks for the crash report. The standard DTS mantra is “Always ask for a crash report first.” I failed to do that in this case, to my own detriment )-: The crash report snippet in your original post, and the discussion of Rust and so on, confused me into thinking that this problem is more complex than it is. However, your crash report makes it clear as to exactly what’s going on: Thread 3 name: Thread 3 Crashed: 0 ??? 0x0000000000000000 0x0 + 0 1 sdk 0x0000000105931ec0 0x105820000 + 1121984 This isn’t a weird code signing issue. Rather, your code has simply jumped to nil. [quote='853477022, ospfranco, /thread/795348?answerId=853477022#853477022, /profile/ospfranco'] I guess cocoapods masqueraded the issue. [/quote] Possibly. I often see cross-platform code deploy the -undefined linker option, which has a tendency to turn build-time errors into run-time errors. Needless to say, I’m not a fan [1]. If you’re curious about how Mach-O symbols work, I talk about that extensively in Understanding Mach-O Symbols. Th

Both issues seem to be gone in iOS 26.0 beta 6

@lmDeveloper1 Confirmed, both issues are gone in iOS 26.0 beta 6

@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 ), ] )

hello, sgraff I can't fixed it use your method, I select swift-6.1-RELEASE.xctoolchain to build preview also failed. I delete the open source version use Xcode default 16.4 version also failed.

On beta 6, this problem is finally fixed. Thank you!

I can't speak to urgency, because that could be interpreted as a future looking timeframe. As a process, I would enable the Swift 5 stricter concurrency checking in code that you control to gauge what the important issues in your code base are, and decide what it would mean to fix them in terms of complexity. After that, try out the Swift 6 language mode, and see what other issues the complier identifies, once again with an eye for complexity. You can then take that information about the technical complexity and use that as information in your overall scheduling and mangement of your software project, and when the best time to do the work is. Since you can do that on a module-by-module basis, there's no need to jump to Swift 6 all at once. You can turn it on just for one module where perhaps there are no issues, or they are easy to address, after updating the language mode, and expand outward from there. And looking at this from the other direction, if there's a module where the iss