“Visual Studio Maui IOS”

When setting the language in iOS/macOS to German (or other languages with “,” decimal separator) and number format to “1.234.567,89” in iOS 26.2, 26.3 and 26.4 Beta, Safari inserts the wrong decimal separator in elements. It should use the local German decimal separator comma “,” instead it uses the english/international period “.” Here is a screenshot of iOS 26.2 when visiting a website with just 2 number inputs in Safari: It behaves the following way: On the first input, enter a number with decimals like “12,34”, clicking “,” on the onscreen-keyboard, a “.” instead of a “,” is added. The number then is formatted in international/English: “12.34”. The input set programatically shows the right decimal separator for German: 5,6. But deleting the “,” and pressing “,” on the onscreen-keyboard again adds a dot instead of a comma and shows the number in international/english: “5.6”. The same issue also happens on desktop Safari on MacOS 26.2 and newer and iOS apps using webvie

Good morning, Apple devs. I'm looking for resources and help designing a BLE hardware peripheral that is compatible with iOS and iPad. I've seen the MFi program, but I've also seen plenty of peripheral devices that work with iOS and iPad that are not listed in the MFi compatibility lists. Can anyone refer me to the proper channels to get support for development of a hardware device? Thank you.

Hello, I am wondering if an app that does the following is possible or is impossible due to ios limitations for apps? An app that access all sms messages, and or all phone calls logs? (goal is to save them and not have to filter them manually) An app that control OTHER apps permissions and or read permissions status of all other apps?

I’m looking for clarification on how rate limiting works for the App Attest service, especially in production environments. According to the entitlement documentation (https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.devicecheck.appattest-environment), iOS ignores the environment setting once an app is distributed through TestFlight, the App Store, or Enterprise distribution, and always contacts the production App Attest endpoint. With that context, I have two questions: Rate‑Limiting Thresholds How exactly does rate limiting work for App Attest? Is there a defined threshold beyond which attestation requests begin to fail? The Preparing to Use the App Attest Service documentation (https://developer.apple.com/documentation/devicecheck/preparing-to-use-the-app-attest-service) recommends ramping up no more than 10 million users per day per app, but I’m trying to understand what practical limits or failure conditions developers should expect. Per‑AppID Budgeting

I'm trying to download the iOS 26.2 simulator, but it fails both in Xcode and via the command line. When I run: xcodebuild -downloadPlatform iOS -buildVersion 26.2 -exportPath ~/Downloads It returns: iOS 26.2 is not available for download. I would like to know: Why iOS 26.2 simulator cannot be downloaded at the moment. Whether iOS 26.2 simulator is still available, or if it has been removed or replaced. How to properly get and install the iOS 26.2 simulator. Any official explanation or solution would be greatly appreciated. Thank you!

Hi everyone, We recently submitted our first B2B iOS app and had a quick question about expected review timing. The application is intended for registered wholesale clients of a food distribution company and the launch is coordinated with the rollout of our ordering platform for customers. Since the launch communication with clients is already scheduled, we wanted to confirm whether there is anything missing in the submission that could delay the review. If anyone from the App Review team can take a quick look or confirm the submission is complete, we would greatly appreciate it. App ID: 6759172913 Thank you!

I have a bunch of Audio Unit v3 plugins that are approaching release, and I was considering using subscription-model pricing, as I have done in a soon to be released iOS app. However, whether this is possible or not is not at all obvious. Specifically: The plugin can, depending on the host app, be loaded in-process or out-of-process - yes, I know, Logic Pro and Garage Band will not load a plug-in in-process anymore, but I am not going to rule that out for other audio apps and force on them the overhead of IPC (I spent two solid weeks deciphering the process to actually make it possible for an AUv3 to run in-process - see this - https://github.com/timboudreau/audio_unit_rust_demo - example with notes) Depending on how it is loaded, the value of Bundle.main.bundleIdentifier will vary. If I use the StoreKit API, will that return product results for my bundle identifier when being called as a library from a foreign application? I would expect it would be a major security hole if random apps could query a

Hello, We are experiencing an issue related to push notifications after updating devices to iOS 26.4 Beta. Our system stores push notification tokens on the server by associating the device token with the device’s IDFV in the app. After updating a device to iOS 26.4 Beta, we observed that the device token from a previously uninstalled version of the app remains valid for more than a week. As a result, two push notifications are delivered to the same device. The situation is as follows: The user installs the app and a device token is generated. The user uninstalls the app. Later, the user installs the app again and a new device token is generated. However, the previous device token does not become invalid, even after more than a week. Because IDFV changes when the app is reinstalled, our server cannot determine that the device belongs to the same user. Therefore, we cannot overwrite the old token with the new one on the server side. Could you please advise: Is this behavior expected in iOS

I am building a simple iOS app that shows the total phone usage time for today using the Screen Time APIs. Architecture: Main app → requests authorization using AuthorizationCenter.shared.requestAuthorization(for: .individual) → displays a DeviceActivityReport Report extension → DeviceActivityReportExtension → calculates total usage using DeviceActivityResults → shows the number in a SwiftUI view The report works correctly. The extension successfully calculates the total usage and displays it on screen. Example logic inside the report extension: for await activityData in data { for await segment in activityData.activitySegments { totalSeconds += segment.totalActivityDuration } } let totalMinutes = Int(totalSeconds / 60) The problem: I need the main app to access that number so I can store it daily in my own database. I tried to send the value from the extension to the main app using: App Group + UserDefaults(suiteName:) App Group + shared file (FileManager.containerURL) writing inside makeConfigurati

Hello App Review team and iOS developer community, I submitted an updated version of my app on App Store Connect on February 5, 2026, and it entered the review process on February 7, 2026. However, I do not understand why, as of today (March 8, 2026), its status is still In Review. I have already contacted Developer Support on February 27, 2026 but have only received the following automated reply: “Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible.” More than a month has passed, and I still haven’t received any official follow-up or updates from Apple regarding this issue My case ID : 102831527320 Apple ID : 1628986976 I would greatly appreciate your help in reviewing and approving this update as soon as possible, as the delay is affecting many users. Thank you for your support.

My app was rejected because Apple’s reviewers couldn’t sign in with Google or iCloud on iOS 26.3. The problem is, I can’t reproduce the issue on any iOS 26.x version, including 26.3.1, which I suspect actually fixes whatever was broken in 26.3. I’ve replied to App Review asking for more details and a screen recording, but now I’m stuck waiting 3 days for a response while Apple’s own review system is apparently still running the buggy 26.3 build. Has anyone else been rejected for this recently? And does anyone know if there’s a way to get the iOS 26.3 simulator runtime now that Components only offers 26.3.1? Any tips for speeding up the back-and-forth with App Review in a case like this would also be appreciated.

We've been waiting since the 5th of February with zero movement, and nothing to suggest anything is likely to change. Phone support, who I've reached out to twice, has no oversight or influence, and I waited over 2 weeks for an 'automated' reply to my support request email. I'm not sure what to do... Every day that passes is momentum/money/time/enthusiasm lost. It's affecting our launch momentum and cross-platform availability for users who are expecting the iOS version to be live alongside Android, which is extremely stressful and upsetting! We would be extremely grateful if the review could be expedited so we can support our users on both platforms. If someone could tell me what, if anything, I can do to speed this up - I'd be most grateful.

Our watchOS app is exploring adding audio VOIP calling capability using our in-home platform. We are using LiveCommunicationKit for this and have that all hooked up nicely in a proof of concept implementation. Our use case is primarily based around supporting end-users through various tasks with assistance from a remotely based expert. We would like for our platform to be able to display visual content on the watch's screen during the call – in other words, we would like to be able to treat this as a video call. LiveCommunicationKit fully supports all video-related flags on watchOS and doesn't appear to have any different symbol availability versus its iOS version. This high-quality thread (https://developer.apple.com/forums/thread/798090) from a DTS engineer suggests that our use case should be valid (i.e. whiteboarding apps) and that the system's response to an accepted income video call is to dismiss the LCK's incoming call screen and bring the target app to the foreground, allowing it to