Visual Studio Maui IOS

At the current time, I am unable to update any of my apps. I am on iOS 26.1 beta four. Whether it’s from the App Store or from TestFlight. and the App Store they show update available and they are grayed out on homepage saying waiting… the only resolution I have found is to go into the App Store. Tap the update wait a few seconds tap the circle it will return to update and then the app is unlocked so I can continue to use the old version. TestFlight is acting similar, but tapping the spinning circle, only brings it back to a resume icon and the app is not usable. This is a critical situation because I am testing Two Factor authentication app. I have not tried installing any new apps.

Since updating to iOS 26.0 (and confirmed on 26.1), ARBodyTrackingConfiguration no longer detects a valid ARBodyAnchor on devices with LiDAR (e.g., iPhone 15 Pro, iPhone 17 Pro Max). This issue reproduces in custom projects and Apple’s official sample “Capturing Body Motion in 3D”. The AR session runs normally, but the delegate call: func session(_ session: ARSession, didUpdate anchors: [ARAnchor]) never yields an ARBodyAnchor with valid joint transforms. All joints return nil when calling: body.skeleton.modelTransform(for: jointName) resulting in 0 valid joints per frame. Environment • Device: iPhone 17 Pro Max (LiDAR) • iOS: 26.0 / 26.1 • Xcode: 16.0 (stable) • Framework: ARKit + RealityKit • Configuration used: config.worldAlignment = .gravityAndHeading config.isAutoFocusEnabled = true config.environmentTexturing = .none session.run(config) Also tested: with and without frameSemantics = .bodyDetection Expected Behavior ARBodyAnchor should be detected and body.skeleton should contain ~89 v

Hello. I work on Windows with Visual Studio 2026 Insider , .Net 10 rc1, MAUI , wifi connected to Mac Mini , XCode 16 and upload to App Store to the public. This was all working fine. Yesterday Apple forced me to update XCode to 26.0.1. Now I cannot publish to the Store like I used to. I do not get any errors , instead I get Publishing project 'Referee' completed. , but the app never shows up in App Store Connect like it usually does. I tried this many times with two different apps that were fine last week. After the XCode update, do I need to reconnect something to somewhere? . . (I shortened paths here for character limit) Validating Mac operating system version compatibility... Checking Xcode version compatibility... Validating Xcode license state... Verifying installed Xcode tools... Initializing Build agent... Checking Build 26.0.10970-net10-rc.2 installation... Starting Build 26.0.10970-net10-rc.2 in port 59237... Agent Build 26.0.10970-net10-rc.2 is running Build 26.0.10970-ne

If I'm reading this guide correctly, macOS will automatically/implicitly startAccessingSecurityScopedResource for files opened via drag to Dock icon or NSOpenPanel. And I'm expected to call stopAccessingSecurityScopedResource to balance it once I'm done. Does that mean that if I don't, I'm leaking kernel resources as per the docs? If you fail to relinquish your access to file-system resources when you no longer need them, your app leaks kernel resources. If sufficient kernel resources leak, your app loses its ability to add file-system locations to its sandbox, such as with Powerbox or security-scoped bookmarks, until relaunched. What is this limit in practice for macOS and iOS? I've seen number ranging from 1000-2500. From my testing, iOS does not provide the same implicit startAccessingSecurityScopedResource when using UIDocumentPickerViewController. Is this a correct observation/per design? Now, in the cases where I'm creating an NSURL by resolving a saved bookmark, I'm expected to explic

My app has the following UI layout: NSSplitViewController as the windows contentViewController NSPageController in the content (right) split item NSTabViewController as the root items of the NSPageController NSViewController with a collection view in the first tab of that NSTabViewController The collection view is using a NSCollectionViewCompositionalLayout in which the sections are set up to have a header using NSCollectionLayoutBoundarySupplementaryItem with pinToVisibleBounds=true and alignment=top With macOS 26, the pinned supplementary item automatically gets a blurred/semi-transparent background that seamlessly integrates with the toolbar. When the window's title bar has a NSTitlebarAccessoryViewController added, the said semi-transparent background gets a bottom hard edge and a hairline to provide more visual separation from the main content. During runtime, my NSPageController transitions from the NSTabViewController to another view controller. When transitioning back, the semi-transparent bl

Issue with App Clip Card Showing App Clip unavailable for DIGI LIVE App In my DIGI LIVE application, I have an App Clip configured for iOS 17.6+ (the file exceeds the 15 MB limit), and I have made all the necessary preparations for the App Clip to work correctly. However, the App Clip card constantly displays an App Clip unavailable error for various users (depending on their system language). The URL associated with the App Clip invocation is: https://ar.digi-live.de The AASA file is located at /.well-known/apple-app-site-association and contains the required fields for the App Clip: { applinks: { details: [ { appIDs: [N9QR6LF765.de.digilive.app], components:[ { #: no_universal_links, exclude: true, comment: Matches any URL whose fragment equals no_universal_links and instructs the system not to open it as a universal link }, { /: *, comment: Matches any URL like ar.digi-live.de } ] } ] }, appclips: { apps: [N9QR6LF765.de.digilive.app.Clip] } } If I use the default App Clip link (https://appclip.app