Search results for

“Visual Studio Maui IOS”

109,114 results found

Post

Replies

Boosts

Views

Activity

BGProcessingTask expirationHandler — No way to distinguish expiration reason
The expirationHandler on BGProcessingTask is a () -> Void closure. It provides no information about why it was called. In my testing, all of the following trigger the same handler: Time expiration Resource pressure (CPU, memory, battery) Not reporting progress User tapping Stop on the Live Activity There is no way for the app to tell these apart. Questions: Q1. Is there an official, complete list of all conditions that trigger expirationHandler? The documentation only mentions time expires. Q2. What is the specific time limit before timeout? If it varies by device state, what are the conditions? Q3. A way to distinguish the reason is needed. User stop and system expiration require completely different handling. Currently this is impossible. Environment: iOS 26, physical device
1
0
74
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
3w
CarPlay: CPListImageRowItem images and CPNowPlayingTemplate buttons occasionally not displaying (requires device reboot)
Device: iPhone 17 Pro Max iOS version: iOS 26.3 CarPlay type: Wired We are encountering two intermittent UI issues in CarPlay when running our music application. The problems occur occasionally and cannot be recovered without restarting the device. Issue 1: CPListImageRowItem image not displaying On the CarPlay home page, some images occasionally fail to appear. Implementation details: The list is updated using CPListTemplate.updateSections. Each item is a CPListImageRowItem. On iOS versions below 26, images are updated using updateImages. On iOS 26, images are provided through CPListImageRowItem.elements, where each element is a CPListImageRowItemRowElement. Observed behavior: Logs confirm that the data is correctly provided. However, in failing cases the CPListImageRowItemRowElement appears with both title and subtitle equal to nil. The image is not rendered in the UI even though the item exists. Issue 2: Now Playing bottom buttons occasionally missing On the Now Playing
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
71
3w
AVAudioSession : Audio issues when recording the screen in an app that changes IOBufferDuration on iOS 26.
Among Japanese end users, audio issues during screen recording—primarily in game applications—have become a topic of discussion. We have confirmed that the trigger for this issue is highly likely to be related to changes to IOBufferDuration. When using setPreferredIOBufferDuration and the IOBufferDuration is set to a value smaller than the default, audio problems occur in the recorded screen capture video. Audio playback is performed using AudioUnit (RemoteIO). https://developer.apple.com/documentation/avfaudio/avaudiosession/setpreferrediobufferduration(_:)?language=objc This issue was not observed on iOS 18, and it appears to have started occurring after upgrading to iOS 26. We provide an audio middleware solution, and we had incorporated changes to IOBufferDuration into our product to achieve low-latency audio playback. As a result, developers using our product as well as their end users are being affected by this issue. We kindly request that this issue be investigated and addressed in a
2
0
473
3w
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
Thanks for sharing — that’s very helpful. I’m seeing a similar “unavailable” state on my side as well, even though the device is detected at lower levels (Finder sees it, trust is established on the device, and Developer Mode is enabled). I’ve already updated my Feedback report with Core Device logs from both macOS and iOS. This makes me think it may not be isolated to a single machine-specific setup.
3w
Effectively distinguish API not available and real error cases
Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as You receive this error when the system prompts a person and they decide not to share their age range with your app. , as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorith
0
0
94
3w
Reply to isEligibleForAgeFeatures: wrong minimum OS version
Since then the documentation has been updated and now the property is consistent with being available for exactly iOS 26.2+. Also there is a paragraph, related to its availability for macOS: In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. Thus we shouldn't use this property in macOS at all, which is rather inconvenient.
Topic: App & System Services SubTopic: General Tags:
3w
How to upload large videos with PHAssetResourceUploadJobChangeRequest?
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
4
0
532
3w
iOS 27 feature suggestion
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.
Topic: Design SubTopic: General Tags:
1
0
921
3w
Reply to Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
Hey @DTS Engineer Travis, A workaround would be helpful, but ideally this would be fixed in the framework so it benefits all affected apps, not just mine. I've already had to implement quite a few workarounds with iOS 26. Looking at my open feedbacks and posts here, several remain unresolved. I have workarounds for most, but could clean up my code if they weren't necessary.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3w
Family Controls entitlement request submitted on March 9, 2026 — no response or status update
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
6
0
440
3w
BGProcessingTask expirationHandler — No way to distinguish expiration reason
The expirationHandler on BGProcessingTask is a () -> Void closure. It provides no information about why it was called. In my testing, all of the following trigger the same handler: Time expiration Resource pressure (CPU, memory, battery) Not reporting progress User tapping Stop on the Live Activity There is no way for the app to tell these apart. Questions: Q1. Is there an official, complete list of all conditions that trigger expirationHandler? The documentation only mentions time expires. Q2. What is the specific time limit before timeout? If it varies by device state, what are the conditions? Q3. A way to distinguish the reason is needed. User stop and system expiration require completely different handling. Currently this is impossible. Environment: iOS 26, physical device
Replies
1
Boosts
0
Views
74
Activity
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
Replies
Boosts
Views
Activity
3w
CarPlay: CPListImageRowItem images and CPNowPlayingTemplate buttons occasionally not displaying (requires device reboot)
Device: iPhone 17 Pro Max iOS version: iOS 26.3 CarPlay type: Wired We are encountering two intermittent UI issues in CarPlay when running our music application. The problems occur occasionally and cannot be recovered without restarting the device. Issue 1: CPListImageRowItem image not displaying On the CarPlay home page, some images occasionally fail to appear. Implementation details: The list is updated using CPListTemplate.updateSections. Each item is a CPListImageRowItem. On iOS versions below 26, images are updated using updateImages. On iOS 26, images are provided through CPListImageRowItem.elements, where each element is a CPListImageRowItemRowElement. Observed behavior: Logs confirm that the data is correctly provided. However, in failing cases the CPListImageRowItemRowElement appears with both title and subtitle equal to nil. The image is not rendered in the UI even though the item exists. Issue 2: Now Playing bottom buttons occasionally missing On the Now Playing
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
1
Boosts
0
Views
71
Activity
3w
AVAudioSession : Audio issues when recording the screen in an app that changes IOBufferDuration on iOS 26.
Among Japanese end users, audio issues during screen recording—primarily in game applications—have become a topic of discussion. We have confirmed that the trigger for this issue is highly likely to be related to changes to IOBufferDuration. When using setPreferredIOBufferDuration and the IOBufferDuration is set to a value smaller than the default, audio problems occur in the recorded screen capture video. Audio playback is performed using AudioUnit (RemoteIO). https://developer.apple.com/documentation/avfaudio/avaudiosession/setpreferrediobufferduration(_:)?language=objc This issue was not observed on iOS 18, and it appears to have started occurring after upgrading to iOS 26. We provide an audio middleware solution, and we had incorporated changes to IOBufferDuration into our product to achieve low-latency audio playback. As a result, developers using our product as well as their end users are being affected by this issue. We kindly request that this issue be investigated and addressed in a
Replies
2
Boosts
0
Views
473
Activity
3w
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
Thanks for sharing — that’s very helpful. I’m seeing a similar “unavailable” state on my side as well, even though the device is detected at lower levels (Finder sees it, trust is established on the device, and Developer Mode is enabled). I’ve already updated my Feedback report with Core Device logs from both macOS and iOS. This makes me think it may not be isolated to a single machine-specific setup.
Replies
Boosts
Views
Activity
3w
StoreKit1:在 iOS 26.4 中[NSBundle mainBundle] appStoreReceiptURL 无法按预期工作
在iOS26.4中,新的交易完成后[NSBundle mainBundle] appStoreReceiptURL 获取的是历史票据,未给出新的票据
Replies
2
Boosts
0
Views
361
Activity
3w
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
I have ssen something similar on the last three beta releases. it tells me that IOS 26,4 is unavailable even though it is in the loaded list. I am running with an M3 iPad. I have two different FB reports in the last few days,
Replies
Boosts
Views
Activity
3w
Effectively distinguish API not available and real error cases
Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as You receive this error when the system prompts a person and they decide not to share their age range with your app. , as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorith
Replies
0
Boosts
0
Views
94
Activity
3w
Reply to isEligibleForAgeFeatures: wrong minimum OS version
Since then the documentation has been updated and now the property is consistent with being available for exactly iOS 26.2+. Also there is a paragraph, related to its availability for macOS: In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. Thus we shouldn't use this property in macOS at all, which is rather inconvenient.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
How to upload large videos with PHAssetResourceUploadJobChangeRequest?
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
Replies
4
Boosts
0
Views
532
Activity
3w
Reply to iOS 26.2 Simulator is not available for download
What Xcode version are you using? I took a look with Xcode 26.4 beta, and the iOS 26.2 simulator is available as a choice when looking at the same UI of available versions to install that you shared a screenshot of. — Ed Ford,  DTS Engineer
Replies
Boosts
Views
Activity
3w
iOS 27 feature suggestion
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.
Topic: Design SubTopic: General Tags:
Replies
1
Boosts
0
Views
921
Activity
3w
Reply to Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
Hey @DTS Engineer Travis, A workaround would be helpful, but ideally this would be fixed in the framework so it benefits all affected apps, not just mine. I've already had to implement quite a few workarounds with iOS 26. Looking at my open feedbacks and posts here, several remain unresolved. I have workarounds for most, but could clean up my code if they weren't necessary.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
3w
Reply to Xcode 26.3 not rendering Unicode/Emoji in Simulator or Canvas
Same here. Works normally in Physical device. Need to fallback to iOS 26.1 in Simulator. Do we have any fix/updates so far?
Replies
Boosts
Views
Activity
3w
Family Controls entitlement request submitted on March 9, 2026 — no response or status update
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
Replies
6
Boosts
0
Views
440
Activity
3w