“Visual Studio Maui IOS”

I'm implementing a PHBackgroundResourceUploadExtension to back up photos and videos from the user's library to our cloud storage service. Our existing upload infrastructure uses chunked uploads for large files (splitting videos into smaller byte ranges and uploading each chunk separately). This approach: Allows resumable uploads if interrupted Stays within server-side request size limits Provides granular progress tracking Looking at the PHAssetResourceUploadJobChangeRequest.createJob(destination:resource:) API, I don't see a way to specify byte ranges or create multiple jobs for chunks of the same resource. Questions: Does the system handle large files (1GB+) automatically under the hood, or is there a recommended maximum file size for a single upload job? Is there a supported pattern for chunked/resumable uploads, or should the destination URL endpoint handle the entire file in one request? If our server requires chunked uploads (e.g., BITS protocol with CreateSession → Fragment → CloseSession), is this ext

I am requesting a dedicated toggle in Settings > Display & Brightness (or Accessibility) to enable/disable the Liquid Glass UI effects so that I am able to get frosted glass thingy effect that was in iOS 18 back.

Hi, I submitted a Family Controls (Distribution) entitlement request on March 9, 2026 for my iOS app, but I still have not received any approval, rejection, or other status update. At this point, I’m mainly trying to understand: whether this waiting time is currently normal, whether there is any way to check if the request is actually under review, and whether Apple provides any follow-up if more information is needed. This is blocking my progress, because the app depends on the Screen Time / Family Controls APIs. Has anyone recently experienced similar delays, and is there any recommended next step besides waiting? Thanks. Imi

Why is my App new build not showing on App Store Connect if it is ready for Distribution? It only shows the previous build. I received this confirmation email about 12 hours ago. Dear Our Maids, Inc., The following build has completed processing: Platform: iOS App Name: OurMaids Build Number: 10 Version Number: 1.1.1 App SKU: com.ourmaids.mobileapp App Apple ID: 6760357291 You can now use this build for TestFlight testing or submit it for distribution. If you have any questions regarding your app, contact us.

We are implementing promo/offer codes for our iOS app’s subscription in-app purchases and have several technical questions regarding validation, receipt data, and integration. Could you please provide guidance on the following points? Testing/Validating Custom Codes Without Production Release: How can we validate custom promo/offer codes in a non-production environment? Current documentation indicates promo codes only work in production, requiring app submission and future release date setup for testing. Receipt Data for Redeemed Codes: The receipt currently includes only offer_code_ref_name, not the exact redeemed code (e.g., “ABC123”) entered by the user. Is there a way to retrieve the specific offer code used via receipts, App Store Server API, or other endpoints? Server-Side Validation Best Practices: What are the recommended best practices for server-side validation of offer codes, including using App Store Server API for transaction verification? Passing appAccountToken for Coupons: How can we

Every new build of macOS 26 further breaks some part of text-to-speech or voice control. I have filed multiple bug reports on this, yet the situation gets worse, not better, with each new build. I am begging you to fix this! I am disabled and rely on these features to work. Accessibility in macOS is more than 50% of my reasons for choosing Macs over Windows. Here's some of what is currently broken: Speak announcements only works if the Samantha voice is selected. If other voices are selected either the announcements don't speak, or they default to the Samantha voice. This became broken with 26.1. Announce the time only works with some voices. I would like to use Australian English Siri 2 but with that voice selected it defaults to Samantha. This became broken with 26.4. With voice control enabled there are two menu bar icons. The blue voice control icon and an orange microphone an application is accessing the microphone icon. This orange icon started appearing with 26.3. For four years of macOS releases, the

Hello App Review Team and iOS Developer Community, We submitted our iOS application on February 25, and within a few hours its status changed to “In Review.” Shortly after that, we received a call from the App Review team requesting some clarification. We provided the requested information during the call, and the same request was later posted in App Store Connect as an unresolved issue. We responded to the request within an hour, providing all the necessary details. However, since then we have not received any further updates regarding the review status. Because this application is related to upcoming sports events, the timing is quite critical. Our client, who owns the sports rights, had planned a launch event on March 6, but unfortunately it had to be postponed because the iOS app was not yet available on the App Store. The sports events are scheduled to begin next week, and our client is planning a marketing campaign ahead of the events, which depends on the app being available.

Greetings! I'm facing a problem handleling full keyboard access in my app. This is a simpler version of the code: struct PrimerTest: View { @FocusState private var focusedImage: Int? var body: some View { VStack(alignment: .leading, spacing: 20) { Link(Go to google or smth, destination: URL(string: https://google.com)!) .font(.headline) Text(First text) Text(Second text) HStack { Text(Label) .accessibilityHidden(true) Spacer() Button(Play) { print(Im a button) } } Text(Selecciona un perfil con el teclado (Tab):) .font(.caption) .foregroundColor(.secondary) HStack { ForEach(0..<5, id: .self) { index in Image(systemName: person.circle.fill) .resizable() .frame(width: 30, height: 30) .focusable(true) .focused($focusedImage, equals: index) .foregroundStyle(focusedImage == index ? Color.blue : Color.gray) .scaleEffect(focusedImage == index ? 1.2 : 1.0) .animation(.easeInOut, value: focusedImage) .accessibilityHidden(true) } } } .navigationTitle(Title n stuff) .padding() } } And the focus behaves as expected and