Visual Studio Maui IOS

First, our app communicates with our blood glucose monitor (CGM) using Bluetooth Low Energy (BLE). On an iPhone 14 Pro with iOS 26.0.1, Bluetooth communication works properly even when the app is in the background and locked. Even if the phone and CGM are disconnected, the app continues to scan in the background and reconnects when the phone and CGM are back in close proximity. It won't be dormant in the background or when the screen is locked. This effectively ensures that diabetic users can monitor their blood glucose levels in real time. However, after using iOS 26.0.1 on the iPhone 17, we've received user feedback about frequent disconnections in the background. Our logs indicate that Bluetooth communication is easily disconnected when switching to the background, and then easily dormant by the system, especially when the user's screen is locked. This situation significantly impacts users' blood glucose monitoring, and users are unacceptable. What can be done?

It's a Broadcast Extension issue: on iOS 26.1 beta the extension never launches—after you tap “Start Broadcast” in the system picker the countdown disappears after 3 s and no broadcast starts, so every live-streaming app（and all other non-system apps that use Broadcast Extension） fails to go live (only the native Photos screen recording still works). Is this a known regression or is a new entitlement required?

Hi, I have a workout app in the App Store which mirrors workout data between the phone and watch. Since iOS 26.x I've been having issues and received reports of the mirroring no longer working. Users in iOS 18 have no problems with this functionality. Bug description: A workout session is started from the phone app and starts mirroring to the watch companion device. The watch starts the workout session and then the mirroring session is disconnected / lost. Sending data to the companion device fails and ending the session on the phone doesn't end the session on the watch...essentially they become completely disconnected. Please note I am testing this on physical devices...not simulators. As a sanity check I've also tried the Building a multidevice workout app sample code and it has the same problem. To re-create on the sample app, I start a workout from the phone, the watch workout starts and then the mirroring session seems to disconnect and is unable to send data. This is the log from the B

I have spent nearly an hour trying to get my iPhone 7 with iOS 15.8 to be recognized within xCode 26. I did not have this issue with the previous version of xCode. I have tried rebooting my Mac, rebooting my iPhone 7, removing the iPhone 7 from the list of devices that belong to my account, verified that I have support files for iOS 15.8 installed, signing out of my Apple account and signing back in....nothing works. Every time I go to Windows > Devices I see the iPhone 7, but I get a never-ending spinning circle next to the iPhone 7 (which is shown as connected) along with a banner that says xCode will continue when Joe's iPhone 7 is finished. I can leave the phone connected to my Mac for an hour, and this message and the spinning circle next to the iPhone 7 never changes.

I am experiencing a critical issue with the IOS Development Portal where certificates are being created under the incorrect Team ID despite being logged into the correct team context. in the Portal also in Xcode. I am logged into the Apple Developer Portal under Company LLC (Team ID: 12345678) However, when creating Apple Development certificates through the portal, they are being assigned Team ID 987654321 (my personal developer account) This occurs even when explicitly creating certificates from within the Company LLC team context. Also the same if i create the IOS Development in Xcode as well. This is preventing me from Archive my app in Xcode so i can upload the new version in the App Store. Please Help. Thank you in advance.

I am experiencing a critical issue with the Apple Developer Portal where certificates are being created under the incorrect Team ID despite being logged into the correct team context. I am logged into the Apple Developer Portal under Company LLC (Team ID: 12345678) However, when creating Apple Development certificates through the portal, they are being assigned Team ID 987654321 (my personal developer account) This occurs even when explicitly creating certificates from within the Company LLC team context. The same is happening if I tried to create the IOS Development Certificate in Xcode, same issue, creates the certificate with the wrong Team ID This is preventing me from Archive my app in Xcode so i can upload the new version of my App in the App Store. Please Help. Thank you in advance

With the latest (26) version of Apple's developer tools, is there a way to manually attach a debugger (other than lldb) to an iOS app launched with devicectl device process launch --start-stopped? In the past, this was possible via the ios-deploy third-party tool (now defunct), which provided a debugserver port. This information is notably missing when using devicectrl – although the process ID of the launch process is provided, and the tool is clearly aimed at letting you launch and attach to processes from the command line. lldb can, of course, attach via its built-in support for this using the device set of commands. But I'm explicitly looking for a way to attach my own debugger via the GDB-compatible debug proxy.

Hi everyone, Our recent app update was rejected under Guideline 2.1 – App Completeness, with the note: “The app was unresponsive when we tapped on Sign in with Apple.” Device: iPad Air (5th generation) OS: iPadOS 26.1 However, we’ve tested this thoroughly and can’t reproduce the problem at all. Here’s what we’ve done so far: Tested both on simulator and real devices (iPhone and iPad). Tried combinations of: Logged in / not logged in to iCloud Apple ID linked / not linked to our app In all cases, Sign in with Apple works as intended — no freezing or unresponsiveness. We also recorded videos showing successful sign-in on simulator (iPad Air, iOS 26) and iPhone 13 mini simulator: We replied to App Review asking whether they were using a simulator (since “Sign in with Apple” often fails there unless the test Apple ID is properly set up). We also provided steps and links explaining that you need to: Create a test account with a real email. Sign in at iCloud.com, and complete security setup / agree to term