“Visual Studio Maui IOS”

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...

Thanks for bringing this to the forums. [quote='820659021, idopte, /thread/820659, /profile/idopte'] returns the following error: Domain: CryptoTokenKit Code: -2 [/quote] That is TKErrorCodeCommunicationError, aka TKError.Code.communicationError in Swift. This is a very generic error that basically means that something went wrong with… well… the communication with the smart card. [quote='820659021, idopte, /thread/820659, /profile/idopte'] At this point, the system appears to be stuck in a non-recoverable state which affects all readers and cards [/quote] Yeah, that’s not good. This is clearly a bug and I appreciate you filing a bug report about it (FB22339746). I took a look at your bug and noticed that you haven’t attached a sysdiagnose to it. Or, more accurately, it says that there’s an associated sysdiagnose log but it hasn’t finished uploading. Please run Feedback Assistant on the iOS device that captured the sysdiagnose log and check on its upload status. Alternatively, export the sysdiagnose l

[quote='820631021, Pavel, /thread/820631, /profile/Pavel'] Is it possible for a Network Extension … to act as a client for an XPC service hosted by a Launch Daemon … ? [/quote] Yes. The trick is to use an app group. Sign your client with an app group ID and then, in the MachServices property of the launchd daemon, set the XPC endpoint name to be a ‘child’ of that app group ID. See the discussion in App Groups Entitlement. App groups are a bit tricky on the Mac. See App Groups: macOS vs iOS: Working Towards Harmony for the full backstory. Given that your client is sandboxed, it must claim access to that app group ID. And in that case I strongly recommend that you authorise that claim via a provisioning profile. Your launchd daemon is (presumably) not sandboxed so it doesn’t need to claim access to the app group ID. However, if you decide to make that claim then my recommendation applies there as well: Authorise the claim with a provisioning profile. If you claim access to an app group and don’t author

Same here. Updated xcode & simulator yesterday and out of sudden ios apps when started show a white screen for seconds before the main application screen (i.e. a splashscreen) appears. Added print() to trace but it looks the delay happens not in user code. Looks like loading libs during the startup process takes ages before user code starts running.

So the only workaround would be for me an iBeacon put in the car - powered on while driving. There IOS recognices and is able to wake up the app - is this correct. Any examples how to? Thanks Robert

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. I suspect the “Segmentation Fault” is caused by insufficient memory, but is it possible that memory usage has increased significantly in iOS 26.4 compared to previous OS versions?

I’m experiencing the same issue on my end. Can’t test with iOS 26.3 anymore, but it works as expected on iOS 18.7.2 and macOS 15.7.4. On iOS 26.4 I’m not receiving any remote notifications, so updates are only fetched when I relaunch the app. Using CKSyncEngine under the hood.

Thank you very much for your time. The issue is still unresolved. I tried using the Instruments memory tool and enabled malloc scribble, but unfortunately, the crash has not been reproduced yet. By the way, there is a crash on the iOS 26 system, and the crash stacks for iOS 26, 18, and 17 are the same as the ones I sent earlier. I noticed that on systems below iOS 17, the crash stack has changed to a different form, and the crash occurs in [AXSpeechThread main] (in libAXSpeechManager.dylib). I have attached the crashes for iOS 26 and iOS 16. Could you please provide guidance? iOS16-AXSpeechThread-Crash.txt iOS26-crash.txt

OK by this: I tried deleting iOS 18 runtime via Xcode Settings > Components, and even removed iOS 26 runtime then re-downloaded it. But the iOS 18 runtime keeps auto-reappearing right after! I also ran sudo rm -rf against the iOS 18 asset folder, and it just throws a permission error—totally useless. I checked the Info.plist under /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/ and confirmed this folder is exactly the orphaned iOS 18.0 simulator runtime. I’m trying to delete this specific cc1f035290d244fca4f74d9d243fcd02d2876c27.asset folder but hit a wall with system permissions. I found this exact issue is already being discussed in the Apple Developer Forum thread here: Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected). It’s clearly a bug on Apple’s side with MobileAsset lifecycle management—these large orphaned simulator runtime assets get stuck in SIP