“Visual Studio Maui IOS”

Dear Quinn, In February 2021, when an Entitlement was added to Team ID WEJZZZZZZZ, I received the following email from Apple and learned how to add the Entitlement to a provisioning profile: Hi, Does Apple add entitlement to my team ? (== App ID: WEJZZZZZZZ) Yes, the entitlement was actually added to your “team”. That gives you the ability to add the entitlement to any app that’s managed by your “team”. Here is the configuration information you can use to check the current status and/or configure your own project: -To use the entitlement, you need to codesign your app with a provisioning profile that includes it. In the Apple developer portal website, you’ll need >to do the following: In the “Provisioning Profiles” section, click the “+” and to create a new profile In the “What type of provisioning profile do you need?” section, select “iOS App Development” Walk through the creation process and directly after the “Select devices.” section, you should see a new section titled “Do you need additiona

Thank you for the response! I think there may be a slight misunderstanding of my question. I am already linking each LeaderboardScore record to a user via a reference field. My challenge is how to efficiently calculate and determine the user’s rank, since I am not storing a rank field in the records and instead compute it client-side. Please see attached photo for visual reference. Current Implementation Fetch LeaderboardScore records sorted by score (descending): let query = CKQuery(recordType: LeaderboardScore, predicate: predicate) query.sortDescriptors = [NSSortDescriptor(key: score, ascending: false)] Assign rank based on position in the sorted results: entries = scores.enumerated().map { index, score in score.asLeaderboardEntry( rank: index + 1, // Rank assigned client-side isCurrentUser: score.profile.id == currentProfileID ) } This works well when the current user is within the fetched results (e.g., top 15–20). In that case, I can determine their rank directly from the local data. However, i

I am seeing a similar issue, but only for my Mac Catalyst archive on XCode 26. My app is a SwiftUI application that embeds an Objective-C framework built from a separate Xcode project. The framework binary itself does have UUIDs, but when I inspect the .xcarchive, the corresponding framework dSYM is missing from the archive’s dSYMs folder. What is confusing is that this does not happen for the iOS build. I use the same framework target, and when I archive the iOS app and upload to TestFlight, I do not get the warning. The problem only appears when I archive the Mac Catalyst version. So in summary: • The embedded framework binary is present in the archive • The framework executable has valid UUIDs • The app archive’s dSYMs folder does not contain the matching dSYM for that embedded framework • This only happens for Mac Catalyst • The same setup works correctly for iOS Has anyone seen Catalyst archives skip generating or packaging dSYMs for embedded frameworks, even though the binary

> I have a custom hardware board that I want to communicate serially with from an iPad. Should I use the DriverKit route or the MFi route? Depends on exactly what your needs are and the hardware you're working with. Starting with MFi, the biggest advantage is that the software side (ExternalAccessory framework) is far simpler to use and includes support for background access (DriverKit does not). The main downside is that it requires a certain amount of custom hardware and the certification process. Comparing it with DriverKit is... complicated. The software side of DriverKit is FAR more complicated. To start with, the DriverKit API is a somewhat odd derivative of the IOKit kernel API. For someone who's familiar with IOKit, it's similar enough to be understandable, but for a new developer, the learning curve can be quite significant. None of this is helped by the fact that DriverKit is poorly documented[1], to the point that my standard advice to new developers is to study the IOKit kernel API (which has o

We have a custom MFI-certified accessory communicating over USB-C using ExternalAccessory. The app calls EASession(accessory:forProtocol:) after receiving EAAccessoryDidConnect, but it always returns nil. We never get past session creation. A few questions: Ruling out an obvious issue, you're testing on a real iOS device, not the simulator, correct? Is this a SwiftUI or UIKit app? If this is a SwiftUI app, try integrating ExternalAccessory support into a basic UIKit project and then retest. I'm not sure what the current situation is, but there are longstanding issues with the ExternalAccessory framework and SwiftUI, and #3 is the easiest way to rule out any other issues. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thank you for reporting this — it's a clear and well-documented write-up. I was able to reproduce this on a MacBook M5 Max running macOS 26.3.1 (25D2128). I built a small test app that exercises both CGSetDisplayTransferByTable and CGSetDisplayTransferByFormula with several different gamma tables (identity, warm tint, inverted, red-only, gamma 1.8). On the M5 Max: Both APIs return kCGErrorSuccess Reading back the table with CGGetDisplayTransferByTable returns the correct values that were just set No visual change occurs on the display The same test app works correctly on an M5 (non-Max) machine running the same macOS build — all gamma changes are immediately visible on screen. This suggests the gamma tables are being stored correctly at the CoreGraphics level, but are not being applied to the display pipeline on M5 Max hardware. Tested on both built-in and external displays. I've related your two bugs (FB22273730 and FB22273782) together and attached the sample project I used to reproduce the problem

Your code that wraps UIActivityViewController with UIViewControllerRepresentable and presents it in SwiftUI looks good to me. I've tried running the code on my iOS simulator (iOS 26.2 23C54) and here is the behavior I see: When sharing one single item, the code demonstrates the behavior as I described. When sharing two items (by using var shareItems: [Any] { [textItem1, textItem1] }), the Save as field isn't editable, and so there is indeed no way to specify the file names. Also, two files are generated, one for each item. So it's not that the way you present UIActivityViewController has anything wrong; it's that UIActivityViewController doesn't allow you to specify the file names when sharing multiple items. I don't see any way that can change the behavior because the UI of UIActivityViewController is system-provided. Please feel free to file a feedback report to request the feature you would like to have. For now, you might consider sharing one single item, if that is appropriate to your u

Same issue for me as well and my ability to test on a real device is totally blocked and has been actually since some time back in Nov.! Xcode 26.3 iOS 26.3.1 watchOS 26.3 Watch was paired to Xcode but would never connect due to the same tunneling errors mentioned by others. After unpairing via Xcode Devices and Simulators the watch cannot be repaired even though I have unpaired and repaired it with iPhone and unpaired and repaired the iPhone to Xcode. NOTHING will cause Xcode to find the watch again. Damn it Apple this crap has been an ongoing issue since Xcode 26.0 How do you have 3 dot releases and not fix something like this?! Might have gotten the watch re-connected via another suggestion in higher up in this thread to connect mack to iPhone via Hotspot. I can see the watch again in Devices and Organizers, but the setup is taking foreeeeeevvverrr so not sure what happen when I switch the mac back to regular wifi.

I’ve not heard of widespread problems with iCloud Private Relay on the iOS 26.4 betas, but that doesn’t mean that this problem isn’t real. My general advice on this front is that you file a bug. Or, in this case, encourage your user to file a bug. They can do that using Feedback Assistant. Ideally they’d do that immediately on seeing the problem, so that the sysdiagnose log attached by Feedback Assistant captures the issue in progress. If they do this, ask them to pass the bug number along and then post it here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There’s no general-purpose way to get Wi-Fi scan results on iOS. Depending on your specific scenario, there may be special-purpose ways to achieve your goals. TN3111 iOS Wi-Fi API overview has more about that. Please read that and then reply back here if you have follow-up questions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com