Visual Studio Maui IOS

The provided workarounds appear to no longer work on iOS 26. Anyone else experiencing the same?

However, we are trying our hardest to maintain a unified codebase going forward, so we are very much trying to prioritize finding a way to make the original python build work. That's all well and good. But Apple's priority is obviously Swift apps for iOS. I have no reason to think that the workflow is the source of this issue I didn't say the workflow is the source of the issue. I said the workflow is the easy part. The difficult part will be getting the Python app to run once it's been notarized. That's a significantly different runtime environment. I wasn't able to find any resources in the documentation about the nuances of notarizing python apps. And you won't. You can search this forum for either python or any variant of notarized and find dozens of posts about notarizing Python apps. Apple Developer support usually tries very hard to help, but it's always painful.

I installed iOS 26.1 Beta 4, hoping the SpriteKit issues were fixed. But alas, they're still there. You can try this additional test: on any SpriteKit scene with a running animation, place a SwiftUI Menu on top. Each time the menu is opened, SpriteKit drops frames. This makes SwiftUI unusable alongside SpriteKit when the scene is animated or live-recorded. SpriteKit used to run predictably and efficiently. iOS 26 has broken too much in terms of performance and usability. The current state of things isn’t reassuring at all.

To stop receiving iOS betas, see Unenroll your Devices. If you need any other help managing storage on iPhone, please ask the Apple Support Community as the Apple Developer Forums are for questions about APIs and features intended specifically for developers.

Ha. got an iOS version of the app together. Validated OK. Took a long time to upload but completed OK. Remember this includes the modified model in the app bundle. Got an email from App Store Connect. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90558: Thinned app size is too large - The “/Payload/PK-LLM.app” app bundle in the universal variant is 4 GB, which exceeds the maximum allowable size. Looks like I'm going to upload the specialized model to HuggingFace. Also, the current macOS version give an error after compiling (but not always). Could not launch “PK-LLM” Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. The logs are full of a lot of stuff I don't understand. Maybe uploading to HuggingFace is the way to go.

This is slightly different on iOS 26.1 beta 4. The initial page load still displays the same issue, but if you tap a link somewhere on the page and navigate, the blur updates to extend down to the bottom of the bar view.

Good evening, thanks so much for your reply. That however is also not an issue for me, as I can still code and test the older structured app by using Xcode 12 for that and an Apple Watch Series 5 with watchOS 6.2 I have for such testing purposes. Once that is done I won't change that version by much anymore, I just need to import it to the existing project for compatibility with the basic functions. As the core of my app will be a pretty basic but for some people daily used functionality I want to have as much compatibility as possible so everyone can use it, not only people with reasonably new hardware. More special features that are not as important for the core function can still be implemented for newer versions, and that will be where my attention is going to be for future development. Debugging of the storyboard version won't be necessary once it is in that project, as nothing will really change for that. I just want to have that base line of functionality for everyone. Maybe I could explain my motivati

I got the same issue after updating to Tahoe. I haven't changed anything in the project, and it still makes a sound in iOS 26, but it doesn't work on Tahoe. The sound works if I use AVAudioPlayer.