“Visual Studio Maui IOS”

Since updating the OS to 26.4, the app has been crashing more often after I launch it. Please post the full crash log, using the instructions found here. Additional information: The app was developed using Unity. After contacting Unity, they indicated that based on the crash logs, it is highly likely that a “Segmentation Fault” occurred. A Segmentation Fault just means your app attempted to access invalid memory, which doesn't actually tell you very much about why you actually crashed. The document Diagnosing memory, thread, and crash issues early has a good overview of the tools that can help file this sort of issue, followed by some specific examples of what can cause this kind of failure. I suspect the “Segmentation Fault” is caused by insufficient memory. No, not really. Memory exceptions (what a seg fault is) happen because you’re accessing memory that you either never allocated or have already freed, neither of which will happen due to direct lack of memory. Keep in mind that your app can't really run o

A good rule of thumb is to set your minimum deployment target based on what you're able to test on a device. The simulator is a great development aid, but it's not a replacement for fully testing your app on a device with all of the major iOS versions that you intend to support.

I was able to replicate this issue in a very simple way, within a new project created with the standard Xcode template, to which I added a Swift Package as a library (MyLibrary). This is the Package definition: // swift-tools-version: 6.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, platforms: [.iOS(.v18)], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary] ), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: MyLibrary, path: Sources/MyLibrary ), ], swiftLanguageModes: [.v6] ) If the target name is equal to library name (MyLibrary) the preview of SwiftUIView works as expected. If I change the target name (for example

I’m experiencing the same issue on an M1 Max Mac Studio as well. The only workaround I’ve found so far is to sign out of the Claude account and sign back in immediately after the error appears. That temporarily restores functionality, but the issue returns again after a couple of hours.

Thanks fat the post. Interesting observation to an API I used as long as I can remember. Hopefully someone from foundation can jump into this thread. But my question to you is if you have encountered any issues preventing using it? What is your concern about the API? it’s been working like that since iOS 4 I believe. I’m more interested in how you going to use it. Yes, it has always been this way, and yes, it is the intended or at least, accepted and long-standing behavior. https://developer.apple.com/documentation/foundation/nsurl/appendingpathcomponent(_:)?language=objc It’s an API I have used forever, under the hood in Objective-C, NSURL was CFURL but I haven’t check so do not quote me on that. It treats whatever string you pass it as the component to append. If you pass a string containing slashes where developers intentionally appended multiple components at once (e.g., [baseURL URLByAppendingPathComponent:@Dir/Subdir/file.txt]). The documentation provides this note or discussion as it’s called

Hello sana, As the technical note states: Migrate to the scene-based life-cycle if your app meets either of the following conditions: The UIApplicationSceneManifest key is missing from your Info.plist or it has no specified configurations. You haven’t implemented the application(_:configurationForConnecting:options:) method in your app delegate. If you are getting the debug message, it means that your app is affected by either of those conditions. Failing to adopt the scene-based life cycle in the next major iOS release will prevent the app from launching. To resolve this, please follow any of the solutions explained in TN3187. That would be the quickest fix. Hoping this helps, Richard Yeh  Developer Technical Support

I used the ChatGPT feature in Xcode to suggest change to improve my alpha blending, and it suggested I add the following to my MakePipeline function: func makePipeline() { let library = device.makeDefaultLibrary() let pipelineDesc = MTLRenderPipelineDescriptor() pipelineDesc.vertexFunction = library?.makeFunction(name: vertex_main) pipelineDesc.fragmentFunction = library?.makeFunction(name: fragment_main) pipelineDesc.colorAttachments[0].pixelFormat = .bgra8Unorm // ---- New changes // Enable blending for transparent drawing pipelineDesc.colorAttachments[0].isBlendingEnabled = true pipelineDesc.colorAttachments[0].rgbBlendOperation = .add pipelineDesc.colorAttachments[0].alphaBlendOperation = .add pipelineDesc.colorAttachments[0].sourceRGBBlendFactor = .sourceAlpha pipelineDesc.colorAttachments[0].destinationRGBBlendFactor = .oneMinusSourceAlpha pipelineDesc.colorAttachments[0].sourceAlphaBlendFactor = .sourceAlpha pipelineDesc.colorAttachments[0].destinationAlphaBlendFactor = .oneMinusSourceAlpha // ---- end

Hi @Mikesch8764, sorry I missed your message. Just installed iOS 26.4.0 on a device and I can confirm the issue is solved now...