Search results for

“Visual Studio Maui IOS”

109,113 results found

Post

Replies

Boosts

Views

Activity

iOS 17+: Spotlight only shows app-indexed keywords after 4+ characters — intended behavior or bug?
We’re seeing a change in Spotlight search behavior on iOS 17 and later: Observation: User‑visible keywords we index (e.g. via Core Spotlight / CSSearchableItemAttributeSet with keywords) only start appearing in Spotlight suggestions after the user has typed more than 3 characters. With 1–3 characters, our app’s content often doesn’t show up at all, even when it clearly matches. Before iOS 17: The same indexed content could appear with fewer characters (e.g. 1–3 characters). Environment: Reproduced on multiple devices running iOS 17.x / 18.x; behavior is consistent. We’d like to confirm: Is this a documented change in iOS 17 (e.g. minimum character threshold for third‑party Spotlight results)? If yes, where is it documented? If it’s not intentional, could this be treated as a bug and considered for a fix in a future release? We’re happy to provide a sample project or more detail if that would help. Thank you.
Topic: App & System Services SubTopic: General Tags:
0
0
68
3w
Pls Can You Make a New Game..
Can you Make an GLOBAL IN REAL LIFE SIMULATOR ROLEPLAY.. Try to get 8 Different Developers to Help do it.. (Similar to Sims Play others Kind of that as well.. Gta Greenfiel rp in Roblox Minigame others as well..) Family Life Simulator Make it Realistic as can be.. The Server Could Add Billionaires or More then That on the Server & Add Multiple ppl on there in Online & Offline.. They Could Play it on ALL KINDS OF DEVICES & Android IPad Google Play IOS other Stuff too) Pls Pls Pls Pls.. I will Make a Image of it then I will Show it to you Guys to See what I want to be in the Game thnxs.. they could Have Wifi/Internet Hotspots & Offline..
Topic: Community SubTopic: Apple Developers Tags:
1
0
714
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
@HolgerDe Thank you for your comment. I have the same understanding as you. In our case, we observed the following behavior on iOS 26.4 Beta: The app was installed on the device before the OS was updated. The device was then updated to iOS 26.4 Beta. After the OS update, the user uninstalled the app and reinstalled it. The app obtained a new device token after reinstalling. After that, we sent push notifications using both: the device token that was obtained before the uninstall, and the new device token obtained after reinstalling the app. As a result, we observed that two push notifications were delivered to the same device.
Topic: App & System Services SubTopic: Notifications Tags:
3w
Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
When using the official Wi-Fi Aware demo app on iOS, with the iOS device configured as a NAN Subscriber, after successfully establishing a peer-to-peer connection with another device via Wi-Fi Aware (NAN), the network path object nwPath.availableInterfaces does not list the nan0 virtual network interface. The nan0 interface is the dedicated NAN (Neighbor Aware Networking) interface used for Wi-Fi Aware data communication. Its absence from availableInterfaces prevents the app from correctly identifying/using the NAN data path, breaking expected Wi-Fi Aware data transmission logic. log: iOS works as subscriber: [onPathUpdate] newPath.availableInterfaces: [en0] iOS works as publisher: [onPathUpdate] newPath.availableInterfaces: [nan0]
Topic: App & System Services SubTopic: Networking
9
0
299
3w
XCode 26 - xcodebuild command hangs on XCFail
On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4, and is likely introduced in XCode 26. Related
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
130
3w
Team ID and App ID prefix mismatch for macOS
I have an app for iOS already on the AppStore and I'm trying to add a macOS version of it. The AppID prefix for this app is different than my Team ID. This mismatch was always fine for submitting my iOS app. However for some reason, the macOS version gets rejected when I upload it. It tells me the AppID prefix must match my Team ID. I do not control my TeamID and I do not control my AppID prefix, they are both given to me by Apple. Yet the error message tells me they must match. How do I get past this? Here is the error message: Validation failed Invalid code signing entitlements. Your application bundle's signature contains code signing entitlements that aren't supported on macOS. Specifically, the APPID_PREFIX.MY_BUNDLE_ID value for the com.apple.application-identifier key in MY_PACKAGE isn't supported. This value should be a string that starts with your Team ID, followed by a dot ('), followed by the bundle ID. (ID: 930b77ae-099f-4798-a14a-2803f2a9be9e) Thanks in advance for any pointer.
Topic: Code Signing SubTopic: General Tags:
1
0
85
3w
Reply to Sandbox subscription test is triggering multiple transaction events for a single purchase attempt
Oof, good luck with ReactNative. I haven't used any IAP ReactNative library, so I'll speak in terms of native StoreKit. On a somewhat relieving note, I also have this issue in my Swift-native iOS app, and I made a post about it on the forums, too. It happens both in Sandbox and production, but NOT when using Local StoreKit Testing configuration files. There are multiple ways for you to observe StoreKit updates. You can observe transactions with Transaction.updates, and also just the subscription updates themselves with SubscriptionStatus.updates. Technically, these are different, but of course a new transaction means potential for a subscription status update. Basically, I had to implement logic to de-duplicate subscription updates that were redundant. For every Subscription update I get, I map it to an array for what I see as active subscriptions. The rest of my app will watch for if my array of active subscriptions changes. If it changes, then we will enabled/disable features. Duplicate transaction
Topic: App & System Services SubTopic: StoreKit
3w
Reply to Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
Similar situation. First time app, macOS and iOS versions, no login, no account, no server - just plain SwiftData, CloudKit, and one in-app purchase to unlock lifetime access. TestFlight: macOS build: submitted Feb 09, 2026 -> approved Feb 11, 2026 iOS build: submitted Feb 09, 2026 -> waiting -> re-submitted by incrementing build number Feb 18, 2026 -> still waiting, status on Mar 12, 2026: 'Waiting for Review' In-app purchase: didn't require submission I got enough feedback from my macOS beta testing that I decided to go ahead with the final app approval submission. Production: macOS build: submitted Mar 06, 2026 -> approved Mar 09, 2026 iOS build: submitted Mar 06, 2026 -> still waiting, status on Mar 12, 2026: 'Waiting for Review' In-app purchase: status on Mar 12, 2026: 'In Review' Without the IAP approval, it doesn't even make sense to announce my macOS release to my network because the app will just lock up after 14 days if they're unable to purchase. Why are
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
3w
Reply to Data Disappeared
Thanks for taking the time to share your question here. After reading your question, I’m finding myself with more questions than answers right now. Could you tell me what database you’re using (SwiftData)? Also, please specify the programming languages, frameworks, or tools you’re working with. The more details you can share, including code snippets and the versions of the tools you’re using (like Xcode, macOS, iOS, etc.), the better. Lastly, could you let me know which platform you’re aiming for? I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.
Topic: Programming Languages SubTopic: Swift
3w
Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
4
0
141
3w
Update for existing app (6759172913) waiting for review – verifying submission
Hi everyone, We recently submitted an update for our existing iOS application and just wanted to verify that everything looks correct on our side in App Store Connect. The previous version of the app was approved and is currently live on the App Store. This new submission is a small update that improves some UI elements and adds minor usability improvements for our customers. At the moment the build is still waiting for review, and since we are coordinating this update with our client rollout schedule, we wanted to confirm that there are no issues with the submission metadata or the selected build. If anyone from the App Review team happens to see this and can confirm that the submission looks complete, we would really appreciate it. App ID: 6759172913 Thank you very much for your time and support. Kind regards, José Rodríguez
Topic: App Store Distribution & Marketing SubTopic: App Review
3
0
122
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
5
0
164
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
1
0
74
3w
iOS 17+: Spotlight only shows app-indexed keywords after 4+ characters — intended behavior or bug?
We’re seeing a change in Spotlight search behavior on iOS 17 and later: Observation: User‑visible keywords we index (e.g. via Core Spotlight / CSSearchableItemAttributeSet with keywords) only start appearing in Spotlight suggestions after the user has typed more than 3 characters. With 1–3 characters, our app’s content often doesn’t show up at all, even when it clearly matches. Before iOS 17: The same indexed content could appear with fewer characters (e.g. 1–3 characters). Environment: Reproduced on multiple devices running iOS 17.x / 18.x; behavior is consistent. We’d like to confirm: Is this a documented change in iOS 17 (e.g. minimum character threshold for third‑party Spotlight results)? If yes, where is it documented? If it’s not intentional, could this be treated as a bug and considered for a fix in a future release? We’re happy to provide a sample project or more detail if that would help. Thank you.
Topic: App & System Services SubTopic: General Tags:
Replies
0
Boosts
0
Views
68
Activity
3w
Pls Can You Make a New Game..
Can you Make an GLOBAL IN REAL LIFE SIMULATOR ROLEPLAY.. Try to get 8 Different Developers to Help do it.. (Similar to Sims Play others Kind of that as well.. Gta Greenfiel rp in Roblox Minigame others as well..) Family Life Simulator Make it Realistic as can be.. The Server Could Add Billionaires or More then That on the Server & Add Multiple ppl on there in Online & Offline.. They Could Play it on ALL KINDS OF DEVICES & Android IPad Google Play IOS other Stuff too) Pls Pls Pls Pls.. I will Make a Image of it then I will Show it to you Guys to See what I want to be in the Game thnxs.. they could Have Wifi/Internet Hotspots & Offline..
Topic: Community SubTopic: Apple Developers Tags:
Replies
1
Boosts
0
Views
714
Activity
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
@HolgerDe Thank you for your comment. I have the same understanding as you. In our case, we observed the following behavior on iOS 26.4 Beta: The app was installed on the device before the OS was updated. The device was then updated to iOS 26.4 Beta. After the OS update, the user uninstalled the app and reinstalled it. The app obtained a new device token after reinstalling. After that, we sent push notifications using both: the device token that was obtained before the uninstall, and the new device token obtained after reinstalling the app. As a result, we observed that two push notifications were delivered to the same device.
Topic: App & System Services SubTopic: Notifications Tags:
Replies
Boosts
Views
Activity
3w
Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
When using the official Wi-Fi Aware demo app on iOS, with the iOS device configured as a NAN Subscriber, after successfully establishing a peer-to-peer connection with another device via Wi-Fi Aware (NAN), the network path object nwPath.availableInterfaces does not list the nan0 virtual network interface. The nan0 interface is the dedicated NAN (Neighbor Aware Networking) interface used for Wi-Fi Aware data communication. Its absence from availableInterfaces prevents the app from correctly identifying/using the NAN data path, breaking expected Wi-Fi Aware data transmission logic. log: iOS works as subscriber: [onPathUpdate] newPath.availableInterfaces: [en0] iOS works as publisher: [onPathUpdate] newPath.availableInterfaces: [nan0]
Topic: App & System Services SubTopic: Networking
Replies
9
Boosts
0
Views
299
Activity
3w
XCode 26 - xcodebuild command hangs on XCFail
On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4, and is likely introduced in XCode 26. Related
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
130
Activity
3w
Team ID and App ID prefix mismatch for macOS
I have an app for iOS already on the AppStore and I'm trying to add a macOS version of it. The AppID prefix for this app is different than my Team ID. This mismatch was always fine for submitting my iOS app. However for some reason, the macOS version gets rejected when I upload it. It tells me the AppID prefix must match my Team ID. I do not control my TeamID and I do not control my AppID prefix, they are both given to me by Apple. Yet the error message tells me they must match. How do I get past this? Here is the error message: Validation failed Invalid code signing entitlements. Your application bundle's signature contains code signing entitlements that aren't supported on macOS. Specifically, the APPID_PREFIX.MY_BUNDLE_ID value for the com.apple.application-identifier key in MY_PACKAGE isn't supported. This value should be a string that starts with your Team ID, followed by a dot ('), followed by the bundle ID. (ID: 930b77ae-099f-4798-a14a-2803f2a9be9e) Thanks in advance for any pointer.
Topic: Code Signing SubTopic: General Tags:
Replies
1
Boosts
0
Views
85
Activity
3w
Reply to Sandbox subscription test is triggering multiple transaction events for a single purchase attempt
Oof, good luck with ReactNative. I haven't used any IAP ReactNative library, so I'll speak in terms of native StoreKit. On a somewhat relieving note, I also have this issue in my Swift-native iOS app, and I made a post about it on the forums, too. It happens both in Sandbox and production, but NOT when using Local StoreKit Testing configuration files. There are multiple ways for you to observe StoreKit updates. You can observe transactions with Transaction.updates, and also just the subscription updates themselves with SubscriptionStatus.updates. Technically, these are different, but of course a new transaction means potential for a subscription status update. Basically, I had to implement logic to de-duplicate subscription updates that were redundant. For every Subscription update I get, I map it to an array for what I see as active subscriptions. The rest of my app will watch for if my array of active subscriptions changes. If it changes, then we will enabled/disable features. Duplicate transaction
Topic: App & System Services SubTopic: StoreKit
Replies
Boosts
Views
Activity
3w
Reply to Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
Similar situation. First time app, macOS and iOS versions, no login, no account, no server - just plain SwiftData, CloudKit, and one in-app purchase to unlock lifetime access. TestFlight: macOS build: submitted Feb 09, 2026 -> approved Feb 11, 2026 iOS build: submitted Feb 09, 2026 -> waiting -> re-submitted by incrementing build number Feb 18, 2026 -> still waiting, status on Mar 12, 2026: 'Waiting for Review' In-app purchase: didn't require submission I got enough feedback from my macOS beta testing that I decided to go ahead with the final app approval submission. Production: macOS build: submitted Mar 06, 2026 -> approved Mar 09, 2026 iOS build: submitted Mar 06, 2026 -> still waiting, status on Mar 12, 2026: 'Waiting for Review' In-app purchase: status on Mar 12, 2026: 'In Review' Without the IAP approval, it doesn't even make sense to announce my macOS release to my network because the app will just lock up after 14 days if they're unable to purchase. Why are
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
3w
Reply to Data Disappeared
Thanks for taking the time to share your question here. After reading your question, I’m finding myself with more questions than answers right now. Could you tell me what database you’re using (SwiftData)? Also, please specify the programming languages, frameworks, or tools you’re working with. The more details you can share, including code snippets and the versions of the tools you’re using (like Xcode, macOS, iOS, etc.), the better. Lastly, could you let me know which platform you’re aiming for? I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.
Topic: Programming Languages SubTopic: Swift
Replies
Boosts
Views
Activity
3w
Waiting for Review: TestFlight 25+ days, Production 10 days, no communication.
Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
4
Boosts
0
Views
141
Activity
3w
Reply to MacOS 26.4 beta “Failed to prepare software update”
I’ve had exactly the same problem on both a m3 Studio and a MacBook Air. If I go to recovery mode, reinstalling the beta seem to successfully solve the problem. The problem occurs after the beta update has completed and the verification phase starts. It sits at 5 minutes for about 5 minutes and then fails. This is happening consisteltly.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
3w
Reply to Ad Hoc .ipa for iOS 12.5.8
Same issue, add hoc build compiled with Xcode 26 cannot be run on iOS 12. No crash report only logs. Launch screen is shown for a second and in a moment app is closed
Topic: Business & Education SubTopic: General Tags:
Replies
Boosts
Views
Activity
3w
Update for existing app (6759172913) waiting for review – verifying submission
Hi everyone, We recently submitted an update for our existing iOS application and just wanted to verify that everything looks correct on our side in App Store Connect. The previous version of the app was approved and is currently live on the App Store. This new submission is a small update that improves some UI elements and adds minor usability improvements for our customers. At the moment the build is still waiting for review, and since we are coordinating this update with our client rollout schedule, we wanted to confirm that there are no issues with the submission metadata or the selected build. If anyone from the App Review team happens to see this and can confirm that the submission looks complete, we would really appreciate it. App ID: 6759172913 Thank you very much for your time and support. Kind regards, José Rodríguez
Topic: App Store Distribution & Marketing SubTopic: App Review
Replies
3
Boosts
0
Views
122
Activity
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
5
Boosts
0
Views
164
Activity
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
1
Boosts
0
Views
74
Activity
3w