Overview

Post

Replies

Boosts

Views

Activity

App not showing on App Store Connect
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.
0
0
35
4w
Provide spoken voice search string
Hello, My goal is to enable users to perform a freeform search request for any product I sell using a spoken phrase, for example, "Hey Siri, search GAMING CONSOLES on MyCatalogApp". The result would launch MyCatalogApp and navigate to a search results page displaying gaming consoles. I have defined a SearchIntent (using the .system.search schema) and a Shortcut to accomplish this. However, Siri doesn't seem to be able to correctly parse the spoken phrase, extract the search string, and provide it as the critiria term within SearchIntent. What am I doing wrong? Here is the SearchIntent. Note the print() statement outputs the search string--which in the scenario above would be "GAMING CONSOLES"--but it doesn't work. import AppIntents @available(iOS 17.2, *) @AppIntent(schema: .system.search) struct SearchIntent: ShowInAppSearchResultsIntent { static var searchScopes: [StringSearchScope] = [.general] @Parameter(title: "Criteria") var criteria: StringSearchCriteria static var title: LocalizedStringResource = "Search with MyCatalogApp" @MainActor func perform() async throws -> some IntentResult { let searchString = criteria.term print("**** Search String: \(searchString) ****") // tmp debugging try await MyCatalogSearchHelper.search(for: searchString) // fetch results via my async fetch API return .result() } } Here's the Shortcuts definition: import AppIntents @available(iOS 17.2, *) struct Shortcuts: AppShortcutsProvider { @AppShortcutsBuilder static var appShortcuts: [AppShortcut] { AppShortcut( intent: SearchIntent(), phrases: ["Search for \(\.$criteria) on \(.applicationName)."], shortTitle: "Search", systemImageName: "magnifyingglass" ) } } Thanks for any help!
1
0
603
3w
I'am porting my App to Swift 6...
... and I managed to fix most issues coming out, but for a specific issue in an class adopting a protocol; basically it is a support class to be used by the view controller and so I wanted to keep it in background, so I created a new actor and I wanted to use it for this protocol and adopting classes. Yet I came out with a host of errors I have no idea about how to cope with: :
1
0
39
3w
Mac Assigning NSManagedObject to NSPersistentStore
Hello, I have a iOS app I was looking at porting to Mac. I'm having an issue with both the Mac (Designed for iPad) and Mac Catalyst Destinations. I can't test Mac due to too many build issues. I'm trying to assign a new NSManagedObject into a NSPersistentStore. let object = MyObject(context: context) context.assign(object, to: nsPersistentStore) This works fine for iOS/iOS Simulator/iPhone/iPad. But on the Mac it's crashing with FAULT: NSInvalidArgumentException: Can't assign an object to a store that does not contain the object's entity.; { Thread 1: "Can't assign an object to a store that does not contain the object's entity."
6
0
273
3w
Apple App Review + DSA Review taking over 2 months – anyone else experiencing this?
I'm an independent developer and one of my apps has been stuck in App Review / DSA review for more than 2 months now. I fully understand that reviews take time, especially with the new Digital Services Act (DSA) requirements in the EU, but two months with almost no feedback is honestly frustrating. I've already submitted everything required for compliance and responded to the few messages I received, but the app is still sitting in review without any clear timeline. For indie developers this kind of delay can be really difficult since launches, updates, and marketing plans depend on getting the app approved. Has anyone else experienced very long DSA-related reviews recently?
2
0
124
4w
Apple Developer Program Enrollment Stuck for Over 2 Weeks
Hello, I enrolled in the Apple Developer Program and placed the $99 order. Shortly after, I received the email saying: “Thank you for your order. Your order request will be processed within 2 business days.” However, it has now been over two weeks and my membership has still not been activated. I also contacted Apple Developer Support about a week ago through the contact form, but unfortunately I have not received any reply so far. When I visit aninterestingwebsite.com, I still see the page prompting me to complete or place the order, even though I already placed it and received the confirmation email. Could someone from Apple please check the status of my enrollment or advise what I should do next? Thank you.
0
0
24
3w
Crash while presenting a media picker for Music
This is the code I use: @MainActor func picker()->UIViewController{ let pickerController = MPMediaPickerController(mediaTypes: .music) print(pickerController) pickerController.showsCloudItems=true pickerController.prompt = NSLocalizedString("Add pieces to queue", comment:""); pickerController.allowsPickingMultipleItems=true; pickerController.delegate=MPMusicPlayerControllerSingleton.sharedController(); return pickerController } MainActor @IBAction func handleBrowserTapped(_ sender: AnyObject){ if let pickerController=contentProvider?.picker(){ self.present(pickerController, animated:true, completion:nil) } } And this his is the crash log: *** Assertion failure in -[MPMediaPickerController_Appex requestRemoteViewController], MPMediaPickerController.m:523 *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'remoteViewController cannot be nil -- process will crash inserting in hierarchy. We likely got a nil remoteViewController because Music is crashing.' *** First throw call stack: (0x1869cac70 0x183499224 0x1844f9f50 0x1a6c6a060 0x18d45518c 0x18d4cd410 0x103354544 0x10336dccc 0x10338f748 0x103364204 0x103364144 0x186957a64 0x1868e5288 0x1868e41d0 0x22bde7498 0x18c5a5ca0 0x18c510254 0x18c71ce90 0x103854340 0x1038542b0 0x103854430 0x1834f1c1c) libc++abi: terminating due to uncaught exception of type NSException *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'remoteViewController cannot be nil -- process will crash inserting in hierarchy. We likely got a nil remoteViewController because Music is crashing.'
12
0
245
3w
Guideline 1.2 Compliance Notice — Build Awaiting Review, 14-Day Deadline Approaching
Hello, I received a Guideline 1.2 compliance notice for my app OMG: Video Chat (Apple ID: 6756574665) on March 7, 2026, with a 14-day deadline to submit a compliant update. The issues raised in the notice — random matching and anonymous chat — were already resolved in the current live version of the app prior to receiving the notice. Specifically: Random matching has been completely removed. Users browse profiles and choose who to connect with. All calls require mutual consent via Accept/Decline. Sign in with Apple is mandatory — no anonymous or guest access exists. Selfie-based age verification is active. Full moderation system is in place: content filtering, user reporting, blocking, and 24/7 monitoring. I responded to the notice on March 7 with a detailed explanation, screen recording, and screenshots demonstrating the current app flow. I also submitted a compliant build and requested an expedited review. As of today (March 12), I have received no acknowledgment, no feedback, and the build has not entered review. The deadline is March 21. I have also contacted Developer Support, the App Review Board, and sent a direct email to the App Review team — all without a substantive response. I have done everything required on my end. The delay is entirely outside of my control. I am respectfully requesting assistance to ensure my build is reviewed before the deadline. Thank you for any help.
1
0
91
3w
SwiftUI Instruments tool error: "Time Profiler: Time Profiler does not support the iOS platform"
I am trying to run the SwiftUI instruments tool for an iOS app and every time I run it, it either switches from giving me the "Time Profiler: Time Profiler does not support the iOS platform" error, or I end up with no data at all; however, when I run just the Time Profiler by itself it works fine. I am running this on a physical device
1
0
65
3w
statusCode 7000 "Team is not yet configured for notarization" - no response from support for days
My Team (ID: 3TMU292P34) has been unable to notarize any macOS software. Every submission is immediately rejected with statusCode 7000: "Team is not yet configured for notarization." This is not a code-signing or technical issue: Developer ID Application certificate is valid (expires 2027-02-02) Code signing and hardened runtime are correctly configured Uploads succeed, but Apple's backend rejects them instantly Both Apple ID auth and App Store Connect API Key auth produce identical results A minimal "hello world" test app also fails — confirming this is account-level, not app-level Submission IDs: 71753924-276a-4b77-be77-4355ff21ab72, 53a990af-45e1-4164-bfa4-2b60e09a3a1d I have contacted Developer Programs Support multiple times with no resolution. Could someone help escalate this?
0
0
41
3w
Inquiry Regarding Differences in App Store Server Notifications (V2) Behavior for Monthly and Annual Plans
I am contacting you to clarify a technical issue regarding the behavior of App Store Server Notifications (V2), as we have observed differences depending on the subscription plan. Currently, we have noticed the following behavior when a refund occurs for an auto-renewable subscription: Observed Behavior: Monthly Plan:When a refund occurs, we receive a REFUND notification, followed by an EXPIRED notification indicating the subscription has ended. Annual Plan:When a refund occurs, we receive the REFUND notification, but the expected EXPIRED notification does not arrive. Questions: Are there any differences in the conditions for sending EXPIRED notifications after a REFUND, depending on the subscription plan (monthly vs. annual)? Is the absence of the EXPIRED notification for annual plans an intended behavior by Apple, or could it be a possible issue? I would appreciate your guidance on this matter.
1
0
189
4w
Enrollment Failure – Unable to Complete Apple Developer Program Registration
Dear Apple Developer Support Team, I am writing to request assistance regarding an issue I am experiencing while attempting to enroll in the Apple Developer Program. Below are the details of the problem: The enrollment process fails before reaching the payment page. The message displayed is: “Your enrollment could not be completed.” The error appears prior to any payment attempt. Two-factor authentication is enabled on the Apple ID. Email address and phone number are verified. The Apple ID being used for enrollment is different from our existing Enterprise account. We have attempted enrollment using: A U.S. address A Indian phone number A clean browser session (logged out of other Apple accounts) The existing Apple Enterprise account under our organization is active and functioning without issues. This new enrollment attempt is for a separate Developer Program account using a different email address. We have tried multiple browsers and networks, but the issue persists and prevents us from proceeding to payment. Could you please check whether: The Apple ID is restricted or flagged in your system? There are any verification issues preventing enrollment? Any additional steps are required from our side to complete registration? Kindly let us know how we can resolve this and proceed with successful enrollment. Thank you for your assistance.
2
0
384
3w
With iOS in German language, Safari inserts the wrong decimal separator in number inputs
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: <input type="number"> <input type="number" value="5.6"> 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 webviews, also since iOS 26.2. How to use the correct decimal separator in html number inputs for the user selected language in iOS/macOS on iOS 26.2 and newer versions? Is this maybe a bug? This was working correctly for iOS 26.1 and older:
2
0
335
4w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bug number to the thread, just for the record. When filing this sort of bug report it’s important to provide: Solid evidence that the problem is on the Apple side of the fence Enough information for Apple’s engineers to investigate it effectively Let’s start with that second point. If you can reproduce the problem reliably, install the Wi-Fi debug profile on your device, reproduce the problem, noting down a rough timestamp, and include the resulting logs and that timestamp in your bug report. Also, consider attaching a packet trace. There are three options here: Record a packet trace from the perspective of the Apple device. On iOS, use an RVI packet trace for this. Record a packet trace from the perspective of your accessory. Record a Wi-Fi level packet trace. You can do this from your Mac (see Recording a Wi-Fi Packet Trace) but it might be easier to do this with the infrastructure you used during the bring up of your accessory. It’s fine to include all three (-: Also include any relevant context about the issue. For example: If the issue is tied to a specific device model (In that case, it’d be good to include the above information for both the successful and failing cases.) If the problem shows up when joining from Settings > Wi-Fi, or whether it’s tied to a specific API, like NEHotspotConfigurationManager Finally, make sure to include an explanation of why you think this is an Apple bug, referencing specific items in the logs and packet traces that you attached. Of course, it’s only possible to do all of this if you can reproduce the problem. Investigating an intermittent issue based on reports coming in from users is much harder. It’s OK to file a bug about such issues, but your bug might not be actionable. At a minimum you should aim to include a sysdiagnose log with your bug. IMPORTANT This log has to be taken shortly after reproducing the problem. Don’t just attach any old log. One option is to request such a log from your users. I talk more about this in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. You can also ask your users to file their own bugs using the Feedback Assistant app. It should automatically capture and attach a sysdiagnose log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] Well, your organisation. It’s rare to find a team where the same engineer works on both the iOS app and the accessory firmware. But if that’s you, good job!
0
0
37
3w
Can a build be "In review" and "Waiting for Review" at the same time?
An does that happen usually? For example: We can see that the build 1.0.10 is showing as "In Review" and at the same time in the submission page we see it as "waiting for review"? Last time it was "In review" it was reviewed within 32 minutes precisely (2 issues were mentioned, then I addressed them, 6 days ago, then 8H ago it went to "In review again") and it stayed "In review" for 8H58 minutes now, actually not even.. it shows on that submissions section "waiting for review". I am a bit confused?
1
0
108
3w
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
I have the issues in this particular guideline: Issue Description We noticed that the app requires users to register with personal information to purchase In-App Purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Next Steps To resolve this issue, please revise the app to not require users to register before purchasing In-App Purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their supported devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Please note that although guideline 5.1.1 requires an app to make subscription content available to all the supported devices owned by a single user, it is not appropriate to force user registration to meet this requirement; such user registration must be optional. For this issue, I have revised my app accordingly many times, but it still get rejected even though I believe that I have revised my app accordingly. My app name is Wallpaperlogoart and my app ID is 6744837826. I would like Apple to look into this issue again in my app submission. I am looking forward to hearing from you soon.
1
0
88
3w
App not showing on App Store Connect
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.
Replies
0
Boosts
0
Views
35
Activity
4w
Provide spoken voice search string
Hello, My goal is to enable users to perform a freeform search request for any product I sell using a spoken phrase, for example, "Hey Siri, search GAMING CONSOLES on MyCatalogApp". The result would launch MyCatalogApp and navigate to a search results page displaying gaming consoles. I have defined a SearchIntent (using the .system.search schema) and a Shortcut to accomplish this. However, Siri doesn't seem to be able to correctly parse the spoken phrase, extract the search string, and provide it as the critiria term within SearchIntent. What am I doing wrong? Here is the SearchIntent. Note the print() statement outputs the search string--which in the scenario above would be "GAMING CONSOLES"--but it doesn't work. import AppIntents @available(iOS 17.2, *) @AppIntent(schema: .system.search) struct SearchIntent: ShowInAppSearchResultsIntent { static var searchScopes: [StringSearchScope] = [.general] @Parameter(title: "Criteria") var criteria: StringSearchCriteria static var title: LocalizedStringResource = "Search with MyCatalogApp" @MainActor func perform() async throws -> some IntentResult { let searchString = criteria.term print("**** Search String: \(searchString) ****") // tmp debugging try await MyCatalogSearchHelper.search(for: searchString) // fetch results via my async fetch API return .result() } } Here's the Shortcuts definition: import AppIntents @available(iOS 17.2, *) struct Shortcuts: AppShortcutsProvider { @AppShortcutsBuilder static var appShortcuts: [AppShortcut] { AppShortcut( intent: SearchIntent(), phrases: ["Search for \(\.$criteria) on \(.applicationName)."], shortTitle: "Search", systemImageName: "magnifyingglass" ) } } Thanks for any help!
Replies
1
Boosts
0
Views
603
Activity
3w
I'am porting my App to Swift 6...
... and I managed to fix most issues coming out, but for a specific issue in an class adopting a protocol; basically it is a support class to be used by the view controller and so I wanted to keep it in background, so I created a new actor and I wanted to use it for this protocol and adopting classes. Yet I came out with a host of errors I have no idea about how to cope with: :
Replies
1
Boosts
0
Views
39
Activity
3w
Register for Apple Developer while you are already registered for Enterprise.
I'm currently enrolled in Enterprise, and I want to continue my enrollment in the Apple Developer Program. How do I do that?
Replies
0
Boosts
0
Views
67
Activity
3w
Mac Assigning NSManagedObject to NSPersistentStore
Hello, I have a iOS app I was looking at porting to Mac. I'm having an issue with both the Mac (Designed for iPad) and Mac Catalyst Destinations. I can't test Mac due to too many build issues. I'm trying to assign a new NSManagedObject into a NSPersistentStore. let object = MyObject(context: context) context.assign(object, to: nsPersistentStore) This works fine for iOS/iOS Simulator/iPhone/iPad. But on the Mac it's crashing with FAULT: NSInvalidArgumentException: Can't assign an object to a store that does not contain the object's entity.; { Thread 1: "Can't assign an object to a store that does not contain the object's entity."
Replies
6
Boosts
0
Views
273
Activity
3w
Apple App Review + DSA Review taking over 2 months – anyone else experiencing this?
I'm an independent developer and one of my apps has been stuck in App Review / DSA review for more than 2 months now. I fully understand that reviews take time, especially with the new Digital Services Act (DSA) requirements in the EU, but two months with almost no feedback is honestly frustrating. I've already submitted everything required for compliance and responded to the few messages I received, but the app is still sitting in review without any clear timeline. For indie developers this kind of delay can be really difficult since launches, updates, and marketing plans depend on getting the app approved. Has anyone else experienced very long DSA-related reviews recently?
Replies
2
Boosts
0
Views
124
Activity
4w
Apple Developer Program Enrollment Stuck for Over 2 Weeks
Hello, I enrolled in the Apple Developer Program and placed the $99 order. Shortly after, I received the email saying: “Thank you for your order. Your order request will be processed within 2 business days.” However, it has now been over two weeks and my membership has still not been activated. I also contacted Apple Developer Support about a week ago through the contact form, but unfortunately I have not received any reply so far. When I visit aninterestingwebsite.com, I still see the page prompting me to complete or place the order, even though I already placed it and received the confirmation email. Could someone from Apple please check the status of my enrollment or advise what I should do next? Thank you.
Replies
0
Boosts
0
Views
24
Activity
3w
Crash while presenting a media picker for Music
This is the code I use: @MainActor func picker()->UIViewController{ let pickerController = MPMediaPickerController(mediaTypes: .music) print(pickerController) pickerController.showsCloudItems=true pickerController.prompt = NSLocalizedString("Add pieces to queue", comment:""); pickerController.allowsPickingMultipleItems=true; pickerController.delegate=MPMusicPlayerControllerSingleton.sharedController(); return pickerController } MainActor @IBAction func handleBrowserTapped(_ sender: AnyObject){ if let pickerController=contentProvider?.picker(){ self.present(pickerController, animated:true, completion:nil) } } And this his is the crash log: *** Assertion failure in -[MPMediaPickerController_Appex requestRemoteViewController], MPMediaPickerController.m:523 *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'remoteViewController cannot be nil -- process will crash inserting in hierarchy. We likely got a nil remoteViewController because Music is crashing.' *** First throw call stack: (0x1869cac70 0x183499224 0x1844f9f50 0x1a6c6a060 0x18d45518c 0x18d4cd410 0x103354544 0x10336dccc 0x10338f748 0x103364204 0x103364144 0x186957a64 0x1868e5288 0x1868e41d0 0x22bde7498 0x18c5a5ca0 0x18c510254 0x18c71ce90 0x103854340 0x1038542b0 0x103854430 0x1834f1c1c) libc++abi: terminating due to uncaught exception of type NSException *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'remoteViewController cannot be nil -- process will crash inserting in hierarchy. We likely got a nil remoteViewController because Music is crashing.'
Replies
12
Boosts
0
Views
245
Activity
3w
Guideline 1.2 Compliance Notice — Build Awaiting Review, 14-Day Deadline Approaching
Hello, I received a Guideline 1.2 compliance notice for my app OMG: Video Chat (Apple ID: 6756574665) on March 7, 2026, with a 14-day deadline to submit a compliant update. The issues raised in the notice — random matching and anonymous chat — were already resolved in the current live version of the app prior to receiving the notice. Specifically: Random matching has been completely removed. Users browse profiles and choose who to connect with. All calls require mutual consent via Accept/Decline. Sign in with Apple is mandatory — no anonymous or guest access exists. Selfie-based age verification is active. Full moderation system is in place: content filtering, user reporting, blocking, and 24/7 monitoring. I responded to the notice on March 7 with a detailed explanation, screen recording, and screenshots demonstrating the current app flow. I also submitted a compliant build and requested an expedited review. As of today (March 12), I have received no acknowledgment, no feedback, and the build has not entered review. The deadline is March 21. I have also contacted Developer Support, the App Review Board, and sent a direct email to the App Review team — all without a substantive response. I have done everything required on my end. The delay is entirely outside of my control. I am respectfully requesting assistance to ensure my build is reviewed before the deadline. Thank you for any help.
Replies
1
Boosts
0
Views
91
Activity
3w
StoreKit / react-native-iap: Payment deducted via UPI in India but no transaction or receipt returned (E_CONNECTION_CLOSED)
Thanks!
Replies
0
Boosts
0
Views
71
Activity
3w
SwiftUI Instruments tool error: "Time Profiler: Time Profiler does not support the iOS platform"
I am trying to run the SwiftUI instruments tool for an iOS app and every time I run it, it either switches from giving me the "Time Profiler: Time Profiler does not support the iOS platform" error, or I end up with no data at all; however, when I run just the Time Profiler by itself it works fine. I am running this on a physical device
Replies
1
Boosts
0
Views
65
Activity
3w
statusCode 7000 "Team is not yet configured for notarization" - no response from support for days
My Team (ID: 3TMU292P34) has been unable to notarize any macOS software. Every submission is immediately rejected with statusCode 7000: "Team is not yet configured for notarization." This is not a code-signing or technical issue: Developer ID Application certificate is valid (expires 2027-02-02) Code signing and hardened runtime are correctly configured Uploads succeed, but Apple's backend rejects them instantly Both Apple ID auth and App Store Connect API Key auth produce identical results A minimal "hello world" test app also fails — confirming this is account-level, not app-level Submission IDs: 71753924-276a-4b77-be77-4355ff21ab72, 53a990af-45e1-4164-bfa4-2b60e09a3a1d I have contacted Developer Programs Support multiple times with no resolution. Could someone help escalate this?
Replies
0
Boosts
0
Views
41
Activity
3w
Inquiry Regarding Differences in App Store Server Notifications (V2) Behavior for Monthly and Annual Plans
I am contacting you to clarify a technical issue regarding the behavior of App Store Server Notifications (V2), as we have observed differences depending on the subscription plan. Currently, we have noticed the following behavior when a refund occurs for an auto-renewable subscription: Observed Behavior: Monthly Plan:When a refund occurs, we receive a REFUND notification, followed by an EXPIRED notification indicating the subscription has ended. Annual Plan:When a refund occurs, we receive the REFUND notification, but the expected EXPIRED notification does not arrive. Questions: Are there any differences in the conditions for sending EXPIRED notifications after a REFUND, depending on the subscription plan (monthly vs. annual)? Is the absence of the EXPIRED notification for annual plans an intended behavior by Apple, or could it be a possible issue? I would appreciate your guidance on this matter.
Replies
1
Boosts
0
Views
189
Activity
4w
Enrollment Failure – Unable to Complete Apple Developer Program Registration
Dear Apple Developer Support Team, I am writing to request assistance regarding an issue I am experiencing while attempting to enroll in the Apple Developer Program. Below are the details of the problem: The enrollment process fails before reaching the payment page. The message displayed is: “Your enrollment could not be completed.” The error appears prior to any payment attempt. Two-factor authentication is enabled on the Apple ID. Email address and phone number are verified. The Apple ID being used for enrollment is different from our existing Enterprise account. We have attempted enrollment using: A U.S. address A Indian phone number A clean browser session (logged out of other Apple accounts) The existing Apple Enterprise account under our organization is active and functioning without issues. This new enrollment attempt is for a separate Developer Program account using a different email address. We have tried multiple browsers and networks, but the issue persists and prevents us from proceeding to payment. Could you please check whether: The Apple ID is restricted or flagged in your system? There are any verification issues preventing enrollment? Any additional steps are required from our side to complete registration? Kindly let us know how we can resolve this and proceed with successful enrollment. Thank you for your assistance.
Replies
2
Boosts
0
Views
384
Activity
3w
With iOS in German language, Safari inserts the wrong decimal separator in number inputs
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: <input type="number"> <input type="number" value="5.6"> 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 webviews, also since iOS 26.2. How to use the correct decimal separator in html number inputs for the user selected language in iOS/macOS on iOS 26.2 and newer versions? Is this maybe a bug? This was working correctly for iOS 26.1 and older:
Replies
2
Boosts
0
Views
335
Activity
4w
Filing a Wi-Fi Bug Report
Every now and again I end up helping a developer with a Wi-Fi issue. These fall into two groups: User-level Wi-Fi issues Development Wi-Fi issues A user-level Wi-Fi issue is one where the developer hasn’t created any of the products involved. An example of this is when you’re developing an app for an accessory and iOS is having problems connecting to that accessory but you don’t control the accessory’s firmware. In general, I recommend that you escalate such issues to the accessory vendor. They can then run their own investigation and, if necessary, file their own bug report. A development Wi-Fi issue is one that directly affects one of your products. For example, you’re developing a Wi-Fi accessory and iOS is having problems connecting to it. In that case, the onus is on you [1] to investigate why things are failing. If your conclusion is that iOS is behaving incorrectly, file a bug about that. IMPORTANT If you do file a bug in the context of some forums thread, please post your bug number to the thread, just for the record. When filing this sort of bug report it’s important to provide: Solid evidence that the problem is on the Apple side of the fence Enough information for Apple’s engineers to investigate it effectively Let’s start with that second point. If you can reproduce the problem reliably, install the Wi-Fi debug profile on your device, reproduce the problem, noting down a rough timestamp, and include the resulting logs and that timestamp in your bug report. Also, consider attaching a packet trace. There are three options here: Record a packet trace from the perspective of the Apple device. On iOS, use an RVI packet trace for this. Record a packet trace from the perspective of your accessory. Record a Wi-Fi level packet trace. You can do this from your Mac (see Recording a Wi-Fi Packet Trace) but it might be easier to do this with the infrastructure you used during the bring up of your accessory. It’s fine to include all three (-: Also include any relevant context about the issue. For example: If the issue is tied to a specific device model (In that case, it’d be good to include the above information for both the successful and failing cases.) If the problem shows up when joining from Settings > Wi-Fi, or whether it’s tied to a specific API, like NEHotspotConfigurationManager Finally, make sure to include an explanation of why you think this is an Apple bug, referencing specific items in the logs and packet traces that you attached. Of course, it’s only possible to do all of this if you can reproduce the problem. Investigating an intermittent issue based on reports coming in from users is much harder. It’s OK to file a bug about such issues, but your bug might not be actionable. At a minimum you should aim to include a sysdiagnose log with your bug. IMPORTANT This log has to be taken shortly after reproducing the problem. Don’t just attach any old log. One option is to request such a log from your users. I talk more about this in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. You can also ask your users to file their own bugs using the Feedback Assistant app. It should automatically capture and attach a sysdiagnose log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] Well, your organisation. It’s rare to find a team where the same engineer works on both the iOS app and the accessory firmware. But if that’s you, good job!
Replies
0
Boosts
0
Views
37
Activity
3w
Can a build be "In review" and "Waiting for Review" at the same time?
An does that happen usually? For example: We can see that the build 1.0.10 is showing as "In Review" and at the same time in the submission page we see it as "waiting for review"? Last time it was "In review" it was reviewed within 32 minutes precisely (2 issues were mentioned, then I addressed them, 6 days ago, then 8H ago it went to "In review again") and it stayed "In review" for 8H58 minutes now, actually not even.. it shows on that submissions section "waiting for review". I am a bit confused?
Replies
1
Boosts
0
Views
108
Activity
3w
Using iOS App on iPhone 5s with iOS 12.5.8
Objective: Downloading and running an old Swift iOS App on iPhone 5s with iOS 12.5.8. Development System and Tools: Apple macBook, M4 Pro, running macOS Tahoe 26.3.1 (25D2128). Xcode Version 26.3 (17C529)
Replies
1
Boosts
0
Views
66
Activity
4w
Waiting my app to be reviewed for 6 days
Hi, my app is stucked with the status "Waiting for review" for the last 4 days. It's crucial for me to get my app reviewed. Anything wrong ? Thanks for your answer.
Replies
1
Boosts
0
Views
47
Activity
3w
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
I have the issues in this particular guideline: Issue Description We noticed that the app requires users to register with personal information to purchase In-App Purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Next Steps To resolve this issue, please revise the app to not require users to register before purchasing In-App Purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their supported devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Please note that although guideline 5.1.1 requires an app to make subscription content available to all the supported devices owned by a single user, it is not appropriate to force user registration to meet this requirement; such user registration must be optional. For this issue, I have revised my app accordingly many times, but it still get rejected even though I believe that I have revised my app accordingly. My app name is Wallpaperlogoart and my app ID is 6744837826. I would like Apple to look into this issue again in my app submission. I am looking forward to hearing from you soon.
Replies
1
Boosts
0
Views
88
Activity
3w