A third-party public library and a personal blacklist need not have the same controls. Understanding which source a switch changes helps explain why one number remains restricted after another option is disabled. Read the scope instead of assuming every list is being cleared.
Start with one number whose result surprised you
You turn off a public database yet a personal nuisance entry remains in place. That can be consistent with a design that keeps personal choices separate. Check the individual entry and any custom rule before concluding that the public switch failed.
Installation, lookup and call handling are three different stages
An app can show information about a number without that number already being in the system's applied protection list. With classic Call Directory, the app prepares entries and hands them to iOS after you enable its extension. iOS then uses that prepared information. It does not ask the classic extension to make a fresh web query each time the phone rings.
This explains a common source of confusion: a lookup result tells you what information you found, while a downloaded record and a successfully applied entry tell you about different stages of preparation. None is a blocked-call counter. Start with one surprising number so that you can compare the same thing at each stage instead of guessing from the size of the whole library.
Check the system extension before granting another permission
Open Phone settings: Settings, Phone on iOS 17, or Settings, Apps, Phone from iOS 18. Find the available call-identification and blocking extension controls and check the relevant app. Labels and the number of extensions can vary, so follow the app's current setup guidance for the components it actually provides. Contacts access is a separate permission, not a substitute for enabling call handling.
Then return to the app and read the current update or application status. If a step is pending or failed, work on that result before changing several other settings. In SpamVeto, manual public-library updates are free. A membership's background update is scheduled by iOS, so waiting for a promised fixed update time is not a useful troubleshooting step; no such schedule is guaranteed.
Check whether the intended source includes this exact number
Compare the complete number, including country calling code, with the entry you expected to apply. If you rely on public data, check that the public source is enabled and that the locally chosen region and category include it. In SpamVeto, switching that source off does not remove personal lists and membership rules, and changing the local filters does not fetch a new collection of numbers.
For a personal entry or custom rule, check its own application result and any capacity warning. A saved rule is a definition, not proof that every number it could describe has been applied. A changed, hidden or spoofed displayed number can also make the incoming call different from the one you checked. Look for that concrete mismatch before deciding the whole extension is ineffective.
Check the opposite problem when a wanted call stays quiet
An app's allow list deals with the app's own number decisions. If an important call is still quiet, review system blocks, unknown-caller handling, Focus and any relevant carrier filtering separately. Removing an app block cannot force those independent controls to ring. Change one layer and recheck the result so that you know which change actually mattered.
Finally, keep the distinction between classic lists and Apple's newer Live Caller ID Lookup. They are different mechanisms, and the presence of an iOS API does not mean every app supplies it. SpamVeto should be assessed against its enabled extensions and applied lists, not an assumed live-query capability. That gives you a clear, repeatable check rather than a search for permissions unrelated to the problem.
Use the status to choose the next action
In a layered setup, record whether you changed a public source, personal entry or system setting. This makes later corrections precise rather than a cycle of unrelated toggles.
Check the exact number, enabled extension and applied-list result before changing unrelated permissions. A successful lookup is useful information, but it is not a record of a call that the system actually blocked.
About the app · SpamVeto
SpamVeto offers personal block and allow lists, reviewed community number information, and on-device screenshot checks. Call protection requires enabled extensions and applied lists; it cannot stop every unwanted call.
About the app · iPhone · iOS 17+Sources and version notes
System behavior follows the linked Apple guides, reviewed on the date above. Menus and feature availability vary by iOS version, language, region and carrier. Examples are illustrative, not measurements or identity checks.