Search results for

“Visual Studio Maui IOS”

109,080 results found

Post

Replies

Boosts

Views

Activity

Reply to Video Audio + Speech To Text
This is actually possible, though it requires a different approach than the typical single-AVAudioEngine setup. The key insight is that iOS allows multiple AVCaptureSession instances to coexist under certain conditions. You can configure two separate audio routes: Use AVCaptureSession with the AirPods as the input device for your speech recognition pipeline. Set the audio session category to .playAndRecord with .allowBluetooth option. For video recording with the built-in mic, use a second AVCaptureSession (or the camera API you are already using). The built-in mic can be explicitly selected as the audio input for this session. The catch is you need to manage the audio session category carefully. The .mixWithOthers option is essential here — without it, one session will interrupt the other. Another approach that avoids the dual-session complexity: use a single AVCaptureSession that captures from the built-in mic for video, and run SFSpeechRecognizer (or the new SpeechAnalyzer on macOS 26 / iOS
Topic: Media Technologies SubTopic: Audio Tags:
1w
App stuck in “Waiting for Review” for a long time – need guidance
Hi everyone, I’m looking for some guidance regarding my app review process. I submitted my iOS app (version 1.0) and it has been in “Waiting for Review” status for quite some time now. I understand that review times can vary, but this is taking longer than I expected, and I’m not sure if this is normal or if there might be an issue with my submission. For some additional context: The first time I submitted the app, it was rejected. Since I’m new to the Apple Developer platform, I mistakenly removed the rejected build instead of addressing the rejection and resubmitting. After that, I submitted the app again, and now it’s been waiting for review. My question is: Could removing the rejected build have caused any delays or issues with the review process? Or is the current waiting time unrelated to that? I would really appreciate any advice from experienced developers on whether I should just continue waiting or if there’s something specific I should check or do. Thank you in advance for your help!
6
0
304
1w
App stuck in “Waiting for Review” for 7+ days, no response from support
Hi everyone, I submitted my iOS app for review on Thursday, March 12th, and it has been stuck in Waiting for Review for over 7 days with no progress. App ID: 458288241 Submission ID: 414b4291-d78e-4394-9ee6-685bc21bf4d2 I have already contacted Apple Developer Support (Case ID: 102847389838) and submitted an Expedited Review request 2 days ago, but the status has not changed and I haven't received any response so far. At this point, I'm concerned that the submission might be stuck or not being processed correctly. This version includes a critical update to a key feature of our app, and the delay is significantly impacting user experience and our revenue. Has anyone experienced a similar situation recently where the app remained in Waiting for Review for this long? Is there any additional step I should take to get this reviewed or escalated? Any guidance would be greatly appreciated. Thank you 🙏
1
0
75
1w
Reply to IsEligibleForAgeFeatures behavior in Brazil
Hi @tomatomato, @jarrodlombardo-eventbase, @raphaelkohncr, Thanks for your continued patience. Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. You wrote: 1. What's the return value of IsEligibleForAgeFeatures for a Brazilian user who has NOT touched the age range feature at all, thus hasn't picked one of the three options? The intended usage of isEligibleForAgeFeatures is to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. If your app is eligible for age-gated features and needs to support age assurance for the current user, the property returns true; otherwise, it returns false. It's a simple boolean value—if you require more granularity for the specific regulatory requirements, use requiredRegulatoryFeatures as well. Next, you wrote: 2. How can we test these cases? From the updated sandbox doc, there
Topic: App & System Services SubTopic: General Tags:
1w
Reply to Display Zoom
Hello @joscar, The system doesn't have any APIs to control system level zoom on iOS. You can create one that works within your app by creating alternate views or modifiers for each intended zoom level, and have the app manage the zoom state.  Travis
1w
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records?
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records? I'm building a leaderboard feature using CloudKit's public database and need advice on the best approach to calculate a user's rank efficiently. Current Setup Record Structure: Record Type: LeaderboardScore Fields: period (String): daily, weekly, monthly, allTime score (Int): User's score profile (Reference): Link to user's profile achievedAt (Date): Timestamp Leaderboard Display: Initially fetch first 15 users (sorted by score descending) Paginate to load more as user scrolls Show total player count Show current user's rank (even if not in top 15) The Challenge I can fetch the first 15 users easily with a sorted query, but I need to display the current user's rank regardless of their position. For example: User could be ranked #1 (in top 15) ✅ Easy User could be ranked #247 (not in top 15) ❌ How to get this efficiently? My Current Approach Query records with scores higher than the user's score and count them: // Count how
3
0
145
1w
sandbox purchase completes but app review gets stuck
Hi all, currently using auto renewable subscriptions (monthly + yearly) using RevenueCat. App Review on iPhone 17 Pro Max and iPad Air 11 (M3) running iOS/iPadOS 26.3.1 reports that after attempting to purchase a subscription in sandbox, the subscription screen loads indefinitely / they can’t proceed (Guideline 2.1(b)). I can reproduce successful purchases on physical devices via TestFlight using fresh sandbox tester accounts (along with 3 other internal users), and I’ve implemented post-purchase syncPurchases() + CustomerInfo refresh/backoff, restore fallback, and a dedicated “confirming purchase” screen to avoid the paywall blocking. Has anyone seen review-environment sandbox sessions where purchase succeeds but entitlement/receipt validation never completes on certain devices/OS versions, and is there any recommended approach for making review more reliable? Currently have another review pending and I attached a screen recording of everything working with a fresh sandbox account + physical device.
1
0
104
1w
Reply to isEligibleForAgeFeatures and different legal requirements for different regions
Hi @jarrodlombardo-eventbase, You wrote: How can we determine if the user is eligible for the TX versus other state requirements? Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. The Declared Age Range framework provides two ways of determining eligibility and requirements based on the person using your app: isEligibleForAgeFeatures requiredRegulatoryFeatures Use isEligibleForAgeFeatures to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. Use requiredRegulatoryFeatures, in addition to isEligibleForAgeFeatures, to determine which regulatory features apply to your app based on the person's region and account settings. Note: Regulatory features added in upcoming regulations (for example, after iOS 26.4) may or may not be included in the existing set of RegulatoryFeature types in iOS 26.4,
Topic: App & System Services SubTopic: General Tags:
1w
Glass Effect Label Shadow Clipping During Morph Animation
Hi all, I’m experiencing a visual bug when applying the glass effect to a Label in Liquid Glass (current version 26.2 on simulator; also reproducible in 26.3.1 on device). Issue: On a label with .glassEffect(.regular), when collapsing via morph animation, the shadow is clipped during the animation, and then suddenly pops back to its un-clipped state, resulting in a jarring visual effect. Minimal Example: import SwiftUI struct ContentView: View { var body: some View { Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.regular) } } } #Preview { ContentView() } I am not sure if I am misusing the .glassEffect() on the label and maybe there is another more native way of achieving this look? Any advice or workaround suggestions would be greatly appreciated!
2
0
91
1w
Reply to Glass Effect Label Shadow Clipping During Morph Animation
If you’re set on using native views in iOS 26 (rather than custom LiquidContainers) and have encountered visual glitches, like shadow clipping or view hierarchy issues, when applying .glassEffect to Menu labels, this thread should be helpful. After some research, I found a useful suggestion on Stack Overflow. TLDR; Wrapping your label in .compositingGroup() significantly improves rendering, especially when using more complex labels inside a Menu. To achieve the cleanest appearance, I recommend combining .compositingGroup() with .glassEffect(.clear). Here’s a sample demonstrating this approach: Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { VStack(alignment: .leading) { Text(Title) .tint(.primary) Text(Subtitle) .tint(.secondary) } .frame(maxWidth: .infinity, alignment: .leading) .padding() .glassEffect(.clear) } .compositingGroup()
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1w
Reply to Glass Effect Label Shadow Clipping During Morph Animation
It seems like there are two ways of approaching this. One (bad one) is: Adding the padding on the label view to compensate the native shadow. Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.regular) .padding(40) // <- Here } Another one, much better: Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.clear) } Both have tradeoffs, one is a spatial one, since you have to provide space for it, but maybe useful for someone who is not constrained by space. Another one - visual, since the glass effect .clear, doesn't have a frost. I guess this could be improved by overlaying a white color with low opacity to simulate the same effect.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1w
Back gesture not disabled with navigationBarBackButtonHidden(true) when using .zoom transition
[Submitted as FB22226720] For a NavigationStack destination, applying .navigationBarBackButtonHidden(true) hides the back button and also disables the interactive left-edge back gesture when using the standard push navigation transition. However, when the destination uses .navigationTransition(.zoom), the back button is hidden but the left-edge back gesture is still available—it can still be dismissed even though back is intentionally suppressed. This creates inconsistent behavior between navigation transition styles. navigationBarBackButtonHidden(_:) works with a standard push transition, but not with .navigationTransition(.zoom). In the code below, .interactiveDismissDisabled(true) is also applied as another attempt to suppress the back-swipe gesture, but it has no effect. As a result, there’s currently no clean way to prevent back navigation when using the zoom transition. REPRO STEPS Create an iOS project then replace ContentView with code below, build and run. Leave nav type set to List Push. Op
2
0
605
1w
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diag
1w
Reply to Video Audio + Speech To Text
This is actually possible, though it requires a different approach than the typical single-AVAudioEngine setup. The key insight is that iOS allows multiple AVCaptureSession instances to coexist under certain conditions. You can configure two separate audio routes: Use AVCaptureSession with the AirPods as the input device for your speech recognition pipeline. Set the audio session category to .playAndRecord with .allowBluetooth option. For video recording with the built-in mic, use a second AVCaptureSession (or the camera API you are already using). The built-in mic can be explicitly selected as the audio input for this session. The catch is you need to manage the audio session category carefully. The .mixWithOthers option is essential here — without it, one session will interrupt the other. Another approach that avoids the dual-session complexity: use a single AVCaptureSession that captures from the built-in mic for video, and run SFSpeechRecognizer (or the new SpeechAnalyzer on macOS 26 / iOS
Topic: Media Technologies SubTopic: Audio Tags:
Replies
Boosts
Views
Activity
1w
How to delete rogue iOS simulators and reclaim disk space?
I have three rogue iOS simulators, how to correctly delete them and reclaim the disk space? These img files are costing me 18gb of storage.
Replies
6
Boosts
0
Views
455
Activity
1w
Reply to How to delete rogue iOS simulators and reclaim disk space?
Yeah, that's probably a bug in the iOS Simulator runtime that incorrectly annotated some of the files within the data directory. I bet if you look in that directory, you'll see some leftover spotlight files. I think you can delete them manually with sudo rm -rf ~/Library/Developer/CoreSimulator/Devices/...
Replies
Boosts
Views
Activity
1w
App stuck in “Waiting for Review” for a long time – need guidance
Hi everyone, I’m looking for some guidance regarding my app review process. I submitted my iOS app (version 1.0) and it has been in “Waiting for Review” status for quite some time now. I understand that review times can vary, but this is taking longer than I expected, and I’m not sure if this is normal or if there might be an issue with my submission. For some additional context: The first time I submitted the app, it was rejected. Since I’m new to the Apple Developer platform, I mistakenly removed the rejected build instead of addressing the rejection and resubmitting. After that, I submitted the app again, and now it’s been waiting for review. My question is: Could removing the rejected build have caused any delays or issues with the review process? Or is the current waiting time unrelated to that? I would really appreciate any advice from experienced developers on whether I should just continue waiting or if there’s something specific I should check or do. Thank you in advance for your help!
Replies
6
Boosts
0
Views
304
Activity
1w
App stuck in “Waiting for Review” for 7+ days, no response from support
Hi everyone, I submitted my iOS app for review on Thursday, March 12th, and it has been stuck in Waiting for Review for over 7 days with no progress. App ID: 458288241 Submission ID: 414b4291-d78e-4394-9ee6-685bc21bf4d2 I have already contacted Apple Developer Support (Case ID: 102847389838) and submitted an Expedited Review request 2 days ago, but the status has not changed and I haven't received any response so far. At this point, I'm concerned that the submission might be stuck or not being processed correctly. This version includes a critical update to a key feature of our app, and the delay is significantly impacting user experience and our revenue. Has anyone experienced a similar situation recently where the app remained in Waiting for Review for this long? Is there any additional step I should take to get this reviewed or escalated? Any guidance would be greatly appreciated. Thank you 🙏
Replies
1
Boosts
0
Views
75
Activity
1w
Reply to IsEligibleForAgeFeatures behavior in Brazil
Hi @tomatomato, @jarrodlombardo-eventbase, @raphaelkohncr, Thanks for your continued patience. Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. You wrote: 1. What's the return value of IsEligibleForAgeFeatures for a Brazilian user who has NOT touched the age range feature at all, thus hasn't picked one of the three options? The intended usage of isEligibleForAgeFeatures is to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. If your app is eligible for age-gated features and needs to support age assurance for the current user, the property returns true; otherwise, it returns false. It's a simple boolean value—if you require more granularity for the specific regulatory requirements, use requiredRegulatoryFeatures as well. Next, you wrote: 2. How can we test these cases? From the updated sandbox doc, there
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Display Zoom
Hello @joscar, The system doesn't have any APIs to control system level zoom on iOS. You can create one that works within your app by creating alternate views or modifiers for each intended zoom level, and have the app manage the zoom state.  Travis
Replies
Boosts
Views
Activity
1w
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records?
CloudKit: Efficient way to get user's rank in leaderboard without fetching all records? I'm building a leaderboard feature using CloudKit's public database and need advice on the best approach to calculate a user's rank efficiently. Current Setup Record Structure: Record Type: LeaderboardScore Fields: period (String): daily, weekly, monthly, allTime score (Int): User's score profile (Reference): Link to user's profile achievedAt (Date): Timestamp Leaderboard Display: Initially fetch first 15 users (sorted by score descending) Paginate to load more as user scrolls Show total player count Show current user's rank (even if not in top 15) The Challenge I can fetch the first 15 users easily with a sorted query, but I need to display the current user's rank regardless of their position. For example: User could be ranked #1 (in top 15) ✅ Easy User could be ranked #247 (not in top 15) ❌ How to get this efficiently? My Current Approach Query records with scores higher than the user's score and count them: // Count how
Replies
3
Boosts
0
Views
145
Activity
1w
sandbox purchase completes but app review gets stuck
Hi all, currently using auto renewable subscriptions (monthly + yearly) using RevenueCat. App Review on iPhone 17 Pro Max and iPad Air 11 (M3) running iOS/iPadOS 26.3.1 reports that after attempting to purchase a subscription in sandbox, the subscription screen loads indefinitely / they can’t proceed (Guideline 2.1(b)). I can reproduce successful purchases on physical devices via TestFlight using fresh sandbox tester accounts (along with 3 other internal users), and I’ve implemented post-purchase syncPurchases() + CustomerInfo refresh/backoff, restore fallback, and a dedicated “confirming purchase” screen to avoid the paywall blocking. Has anyone seen review-environment sandbox sessions where purchase succeeds but entitlement/receipt validation never completes on certain devices/OS versions, and is there any recommended approach for making review more reliable? Currently have another review pending and I attached a screen recording of everything working with a fresh sandbox account + physical device.
Replies
1
Boosts
0
Views
104
Activity
1w
Reply to isEligibleForAgeFeatures and different legal requirements for different regions
Hi @jarrodlombardo-eventbase, You wrote: How can we determine if the user is eligible for the TX versus other state requirements? Before I begin, the answer below applies to current regional requirements as of the iOS 26.4 release, and should also be used as guidance for any upcoming regional regulations. The Declared Age Range framework provides two ways of determining eligibility and requirements based on the person using your app: isEligibleForAgeFeatures requiredRegulatoryFeatures Use isEligibleForAgeFeatures to determine whether associated laws or regulations may apply to your app based on the person's region and account settings. Use requiredRegulatoryFeatures, in addition to isEligibleForAgeFeatures, to determine which regulatory features apply to your app based on the person's region and account settings. Note: Regulatory features added in upcoming regulations (for example, after iOS 26.4) may or may not be included in the existing set of RegulatoryFeature types in iOS 26.4,
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Glass Effect Label Shadow Clipping During Morph Animation
Hi all, I’m experiencing a visual bug when applying the glass effect to a Label in Liquid Glass (current version 26.2 on simulator; also reproducible in 26.3.1 on device). Issue: On a label with .glassEffect(.regular), when collapsing via morph animation, the shadow is clipped during the animation, and then suddenly pops back to its un-clipped state, resulting in a jarring visual effect. Minimal Example: import SwiftUI struct ContentView: View { var body: some View { Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.regular) } } } #Preview { ContentView() } I am not sure if I am misusing the .glassEffect() on the label and maybe there is another more native way of achieving this look? Any advice or workaround suggestions would be greatly appreciated!
Replies
2
Boosts
0
Views
91
Activity
1w
Reply to Glass Effect Label Shadow Clipping During Morph Animation
If you’re set on using native views in iOS 26 (rather than custom LiquidContainers) and have encountered visual glitches, like shadow clipping or view hierarchy issues, when applying .glassEffect to Menu labels, this thread should be helpful. After some research, I found a useful suggestion on Stack Overflow. TLDR; Wrapping your label in .compositingGroup() significantly improves rendering, especially when using more complex labels inside a Menu. To achieve the cleanest appearance, I recommend combining .compositingGroup() with .glassEffect(.clear). Here’s a sample demonstrating this approach: Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { VStack(alignment: .leading) { Text(Title) .tint(.primary) Text(Subtitle) .tint(.secondary) } .frame(maxWidth: .infinity, alignment: .leading) .padding() .glassEffect(.clear) } .compositingGroup()
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
1w
Reply to Glass Effect Label Shadow Clipping During Morph Animation
It seems like there are two ways of approaching this. One (bad one) is: Adding the padding on the label view to compensate the native shadow. Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.regular) .padding(40) // <- Here } Another one, much better: Menu { Button(Duplicate, action: {}) Button(Rename, action: {}) Button(Delete…, action: {}) } label: { Label(PDF, systemImage: doc.fill) .padding() .glassEffect(.clear) } Both have tradeoffs, one is a spatial one, since you have to provide space for it, but maybe useful for someone who is not constrained by space. Another one - visual, since the glass effect .clear, doesn't have a frost. I guess this could be improved by overlaying a white color with low opacity to simulate the same effect.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
1w
Back gesture not disabled with navigationBarBackButtonHidden(true) when using .zoom transition
[Submitted as FB22226720] For a NavigationStack destination, applying .navigationBarBackButtonHidden(true) hides the back button and also disables the interactive left-edge back gesture when using the standard push navigation transition. However, when the destination uses .navigationTransition(.zoom), the back button is hidden but the left-edge back gesture is still available—it can still be dismissed even though back is intentionally suppressed. This creates inconsistent behavior between navigation transition styles. navigationBarBackButtonHidden(_:) works with a standard push transition, but not with .navigationTransition(.zoom). In the code below, .interactiveDismissDisabled(true) is also applied as another attempt to suppress the back-swipe gesture, but it has no effect. As a result, there’s currently no clean way to prevent back navigation when using the zoom transition. REPRO STEPS Create an iOS project then replace ContentView with code below, build and run. Leave nav type set to List Push. Op
Replies
2
Boosts
0
Views
605
Activity
1w
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diag
Replies
Boosts
Views
Activity
1w