Hello,
I submitted an app update (submission ID: 3bbbd08f-6ca9-40a2-bdc1-a2f33061f647) that was rejected for Guideline 4.0 - Design (about ad frequency issues).
The rejection message included this option:
"The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know."
I replied on December 11 at 10:21 PM asking to approve the current version as a bug fix, and that I would address the ad frequency in my next update.
It's now been over 35 hours with no response.
Should I resubmit my binary for review? Typically, when I reply to the App Review message in such a scenario, my app gets approved in a few hours.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi everyone,
I’ve filed a Feedback report (FB20986470) for a serious issue affecting the Call Directory database when add phone numbers for call blocking.
When adding blocking numbers to a Call Directory extension, the system’s CallKit database (/private/var/mobile/Library/CallDirectory/CallDirectory.db) becomes corrupted.
The reload call (reloadExtensionWithIdentifier) fails with error code 11 when the system tries to insert blocking entries, and the Console app on macOS shows the following errors:
database corruption page 2265525 of /private/var/mobile/Library/CallDirectory/CallDirectory.db at line 81343 of [f0ca7bba1c]
database corruption at line 79387 of [f0ca7bba1c]
Error Domain=com.apple.callkit.database.sqlite Code=11 "sqlite3_step for query 'INSERT INTO PhoneNumberBlockingEntry (extension_id, phone_number_id) VALUES (?, (SELECT id FROM PhoneNumber WHERE (number = ?))), (?, (SELECT id FROM PhoneNumber WHERE (number = ?))),...)'"
After this happens, CallKit becomes fully corrupted on the device and no further numbers can be added, even after:
Disabling and re-enabling the extension
Restarting the device (either force or soft restart)
Reinstalling the app
Waiting for a couple of minutes after this issue happens (that CallKit could possibly self-recovered)
I also tested other call-blocking apps, and they all fail with the same error. The only thing that recovers the system is a full “Reset All Settings.”
This issue has been reported by many users of my app, across multiple iOS versions and devices.
Similar related issue reported by another developer:
https://developer.apple.com/forums/thread/806129
Steps to Reproduce:
Enable the Call Directory extension from a call-blocking app.
Add and reload blocking numbers (a few thousand entries).
Perform multiple reloads between additions.
Check the Console, the corruption errors appear.
From this point, all insert attempts fail system-wide.
Expected Result:
Entries should be inserted successfully, or the system should self-recover without persistent corruption.
Actual Result:
sqlite3_step fails with Code=11, and the Call Directory database remains corrupted until the user resets all settings.
Additional Notes:
All numbers are sorted and deduplicated before insertion.
Happens intermittently after multiple reloads.
The system log always shows internal database failure.
Environment:
Device: iPhone 16 Plus
iOS 18.2 Beta (23C5027f)
Xcode 16.1 (17B55)
Attachments (included in Feedback FB20986470):
sysdiagnose captured immediately after the failure (with Phone app General Profile)
It seems like a system-level corruption affecting all Call Directory extensions once it occurs.
Hello Apple Developer Community,
I'm experiencing an issue with file download functionality in the iOS Simulator after updating to Xcode 26 RC (Build 17A321).
Issue Description:
When attempting to download files in the iOS Simulator via Safari, the download prompt appears correctly, but after tapping the 'Download' button, files are not being saved to the Files app. The download appears to do nothing with no error message, no indication of failure, but the file simply doesn't appear in Downloads or anywhere in the Files app.
Environment:
Xcode Version: 26.0 RC (17A321)
iOS Simulator Version: 26.0 RC (23A339)
Device Simulated: iPhone Air
Steps to Reproduce:
Open Safari in the iOS Simulator
Navigate to a downloadable file (PDF, ZIP, etc.)
Tap to initiate download
Download prompt appears as expected
Tap the 'Download' button
Check the Files app → Downloads folder (empty)
Expected Behavior:
Files should download normally as they do on physical devices and as they did in previous Xcode versions.
Actual Behavior:
The download prompt dismisses after tapping 'Download', but no file appears in the Files app. No error message is shown, and there's no indication that the download failed, it simply appears as if nothing happened.
Additional Information:
Downloads work correctly on physical device (iOS 26 RC 23A340)
This functionality worked properly in previous Xcode versions
I have created a bug report to Feedback assistant: FB20190927
Thanks in advance for any assistance.
Hello, is it allowed to include the action=write-review URL parameter in customer support emails to direct users to the App Store review page?
Example: https://apps.apple.com/app/id[APP_ID]?action=write-review
I want to make it easy for customers to leave feedback after positive support interactions, but only if it's compliant.
Hello,
my call blocking app was incorrectly rejected under Guideline 2.5.12 for using "SMS Fraud Extension," but my app is a call blocker that only uses CallKit framework exclusively for blocking unwanted phone calls.
There's no SMS functionality or SMS/Message frameworks at all and no pre-made spam lists.
I've submitted an appeal, but this is a time-sensitive update that needs to be released as soon as possible (used an Expedited Review request already).
I had a previous appeal for another app that was delayed for 11 days, and it was only resolved after posting here. I cannot afford another 11-day delay for this time-sensitive update.
Any suggestions to make the process faster?
Thank you.
Hi Apple Dev community,
I want to ask if CallKit and CXCallDirectoryProvider (with addBlockingEntryWithNextSequentialPhoneNumber) doesn't work for 3rd party Phone apps.
Is this a known issue that CallKit doesn't work on 3rd party iOS Phone apps (like WhatsApp, etc)?
Thank you.
Hello,
I've submitted a detailed appeal for my app update rejection on September 11th and haven't received any response yet.
Is 11+ days normal for appeal responses or should I follow up somehow?
Any insights would be appreciated as this is blocking my app update.
Thank you.
Call blocking using a third-party CallKit app is not longer working with the latest iOS 26 Public Beta (23A5297m).
We've tried several different Call Blocking apps (that used to work fine on iOS 18.5) and their call blocking functionality is not working anymore.
All calls pass through and the phone rings on those "blocked" numbers. We got several user complaints about our app that is not working on iOS 26 Public Beta.
We've filed 2 bug reports with Feedback Assistant:
FB19140680
FB19140594
Please fix this issue in the next Beta versions of iOS 26 to have a stable iOS 26 release in the future.
Thank you in advance.
App Store Connect's privacy label system creates impossible review situations by checking live app versions instead of submitted builds.
Problem:
Developer has a live app with tracking on the App Store
Developer create a new app version with all tracking removed
Privacy labels from AppStore Connect cannot be updated because system references live version with tracking
App gets rejected for privacy label mismatch with submitted build
Cannot fix labels until approved, cannot get approved with wrong labels
Expected behavior:
Privacy label system should allow updates for pending app versions or check submitted build instead of live version.
Steps to reproduce:
Submit app update with tracking removed
Try to update privacy labels to "no tracking" from AppStore Connect
System shows error: "Your app contains NSUserTrackingUsageDescription, indicating that you will request permission to track users. You must indicate which data types are tracking users. If this is incorrect, update your app binary and upload a new build to App Store Connect."
App gets rejected despite submitted build having no tracking
This affects any developer trying to remove tracking functionality from AppStore Connect in such a scenario.
I have opened a bug in Feedback Assistant: FB19459680
Hello Apple Developer Community,
I'm developing a call-blocking app for iOS and have encountered an issue with iOS 18. Despite calls being successfully blocked by our app's Call Directory extension, they are still appearing as unanswered calls in the native Phone app.
Details:
iOS version: 18
App uses CallKit and Call Directory extension
Calls are blocked successfully (not ringing on device)
Blocked calls show up as "Unanswered" in Phone app's recent calls list
Expected behavior: Blocked calls should not appear in the Phone app's recent calls list.
Actual behavior: Blocked calls appear as "Unanswered" in the recent calls list.
Following up on a previous thread that was marked as resolved, we're observing that the behavior of blocked calls in iOS 18.2 hasn't changed as indicated.
Current behavior in iOS 18.2:
Calls blocked by Call Directory extensions still appear as "unanswered" in the Phone app's call history
The calls are successfully blocked (don't ring) though
There's no indication in the call history that these calls were blocked
Expected behavior (as previously indicated would be fixed in iOS 18.2 beta 3):
Blocked calls should be labeled as "Blocked"
Should show which app blocked them
This continues to cause confusion among users who expect blocked calls to either be clearly labeled or not appear in their history at all. We're still receiving regular user complaints about this behavior.
Has there been any change in the timeline for addressing this? Any information would be helpful for both developers and users.
Thank you in advance.