If you need help with SpamSniper, the best place to reach the project is the GitHub issue tracker.
Before You Open an Issue
Check the basics first:
- confirm that
Settings > Phone > Call Blocking & Identificationhas SpamSniper enabled - refresh the selected blocklists in the app
- reopen the app after changing repository or blocklist selections
- if you use Contacts filtering, verify that Contacts access is still allowed
Report an Issue
Open a GitHub issue in this repository with:
- a short summary of the problem
- what you expected to happen
- the steps needed to reproduce it
- your device model and iOS version
- screenshots, logs, or error messages if you have them
Request Help
For setup questions or feature requests, describe what you are trying to do and where the workflow breaks down.
Troubleshooting
- If call blocking is not working, make sure the Call Directory extension is enabled and the latest local blocklist has been loaded.
- If a repository sync fails, try again later and include the repository URL or repository name in your issue report.
- If a number should not have been blocked, mention whether it came from a synced blocklist or from your personal list.
Privacy & Data
SpamSniper keeps personal blocklist entries on-device. Repository blocklists are downloaded from the selected source, verified, and merged locally before being handed off to iOS for blocking.
The optional Spam Sniper Triage Terminal is separate from the iOS app and stores community report data as described in the privacy policy.
Contact
Open an issue here:
- https://github.com/ffimnsr/spam-sniper/issues