“Visual Studio Maui IOS”

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

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