TapVaultSupport & setup.
Read compatible tags on iPhone and manage your library on iPhone and iPad.
The app is under development. Physical NFC operations and synchronization across devices still require release validation.
Set up TapVault
- Use iOS/iPadOS 17 or later. Physical NFC operations require a compatible iPhone.
- Open the scanner, start a session and hold one compatible tag near the reader. Allow NFC access when prompted.
- Inspect the records, then save them to the library or create a link, text or vCard contact.
- To write, select saved content and confirm the overwrite. Keep the destination tag still until read-back verification finishes.
iCloud synchronization requires a correctly configured app build, an available iCloud account and network access. The app shows synchronization errors; changes may remain local until synchronization succeeds.
Troubleshooting
Why is scanning unavailable?
iPad and Simulator do not support physical NFC operations in TapVault. On iPhone, confirm device support and use one supported tag at a time.
Why can’t I write a tag?
The destination may be read-only, unsupported or too small for the NDEF message. A failed or interrupted write may partially change a tag. Inspect it before retrying; a failure is not reported as success.
Why is my library not syncing?
Check the iCloud account, connection and synchronization status in Settings. For development builds, the CloudKit container, signing entitlements and production schema must be configured. Preserve local data while investigating.
Can I add an access card to Apple Wallet?
Not in this version. Reading NFC content does not reproduce a protected credential or provision a Wallet key. Wallet requires support from the relevant issuer.
Remove saved data
Delete saved library entries in the app. See data removal for iCloud and physical-tag considerations.
Bugs, incidents & questions
Use the GitHub issue chooser for a bug, incident, feature request or support question. English and Polish reports are welcome. A GitHub account is required.
Include the app version/build, device model, iOS/iPadOS version, expected and actual behavior and minimal reproduction steps. For incidents, include impact, start time with timezone, current status and any workaround.
Use fictional data. Remove NFC payloads, tag identifiers, contact details, access credentials, iCloud identifiers and private screenshots or logs before posting.
Security reports
Use GitHub private vulnerability reporting for suspected vulnerabilities or data exposure. Do not publish exploit details or real credentials. No fixed support response time or bounty is promised.