My indian passport is 1.1 year old it doesnt support nfc , only available for new passports , there is no back option its asking both to scan id and nfc . No way to exit, wtf is this always sucks to be a customer to use a web3 product. Web3 sucks in developing apps , better hire a andriod dev than giving a gig to vibe coder or useless devrel
I’m trying to scan for nfc chip but after scanning for more than 10-15 mins app is not fetching anything. I passed the MZ number thing step but scan chip is not happening.
I am a security researcher trying to submit a Critical Vulnerability, but I am currently blocked by the ZK Passport KYC process due to a hardware limitation. The Issue: The ZK Passport app requires an NFC scan of a passport or ID card. Passport: My valid passport is an older version that does not have an NFC chip. National ID: My Indian Aadhaar card does not support NFC scanning. Impact: I am physically unable to complete the verification flow on the mobile app because my valid government documents do not have the required chips. Request: Please allow me to verify using an alternative method (such as manual document upload or a standard video KYC provider like SumSub) that does not require NFC. I have my documents ready to upload immediately.
Hi I spent about 30 minutes trying to verify my identity in the app, and only after multiple attempts did I find out that Bolivia is not currently supported. Because of that, the app doesn’t accept my passport or national ID, so verification is impossible from my country. Please consider enabling Bolivia or at least making this limitation clearer in the verification flow. Appreciate the work you’re doing!
Issue type: Bug report Device model: Samsung Galaxy Note 10+ Operating system: Android 12 ID type: National ID card Country of ID: Pakistan App version: 0.9.40 Description of the issue: I am unable to complete identity verification in the zkPassport app because the application fails to properly scan my ID document. The camera scan either does not detect the ID card or remains stuck during the scanning step. Additionally, the verification process is extremely slow. After attempting to scan the ID, the app remains in a processing state for a long time without completing the step or providing a clear error message. I have attempted multiple retries and basic troubleshooting steps, including restarting the app and device and using a stable internet connection, but the issue persists. Expected behavior: The app should successfully scan the ID document and complete verification within a reasonable processing time. Actual behavior: The ID document is not scanned successfully, and the verification process becomes very slow or stuck during processing. Impact: This issue prevents completion of mandatory identity verification required by third-party platforms and blocks time-sensitive verification-dependent actions. Additional notes: I am available to provide additional non-sensitive technical details if required to help resolve this issue.
Hello, I am trying to complete my identity verification on Immunefi, but I am facing an issue with the ZKPassport app. My current mobile device (Realme) is not compatible with the app because it lacks NFC hardware support. Also, I want to mention that I have a bug with me (containing my documents/items), but without a compatible phone, I cannot scan the QR code or my ID. Could you please provide an alternative way for me to verify my identity? Device Info: Realme not60x (No NFC support) Location: Pakistan"
unable to scan African passport or ID. I’ve tried multiple times however it does read a Canadian ID.
The app says my passport is genuine, but how does it know that its genuine?
Hey everyone, greetings,. is the zk-passport mobile app is open sourced? if yes, can someone point me to the repo? i checked their repos and all i could find was circuits and few other sdks. Thanks
iOS version: 18.6.2 ZKPassport version: 0.9.29 I reach the chip scanning phase and I get this message "Error: last command of the chain expected..." Trying again multiple times doesn’t solve it. I get the error irrespective of whether I use the camera to scan the MRZ or I input it manually.
This is more of a question than a request. I am building a (experimental) voting platform and currently thinking through attack vectors. In this case, what if an individual is able to access your passport temporarily; long enough to scan it into their ZKPassport App, after which point they lose access to the physical passport. Would the passport owner have any recourse to invalidate the attacker’s scan (presumably by re-scanning it themselves?)? If not … do scanned passports expire in the app (requiring re-scanning) so that the attacker’s version becomes invalid after a certain period (hopefully less than expiration date of the passport)? If not, is there anything that can be done at the application level, such as detecting that proof A uses a passport more recently scanned than proof B? Thanks for the consideration!
MRZ scan failed, checksum validation failed. on IOS even when i enter it manually same error pls fix german id card
Getting this all the time on the iOS app. Can’t verify for a website because of this.
Hi team, I’m facing an issue after the latest ZKPassport mobile app update. I’m using the latest SDK, and everything was working fine until Saturday evening (last tested nov 1st ~9:30 PM IST). Today, when I opened the ZKPassport app for verification, it prompted a mandatory update, and after updating, the verification flow stopped working. It now throws an error with no debug logs. Nothing has changed on my side same code, same sdk version (0.11.0) so it looks like the issue is coming from the latest app release. I’ve attached screen recording below. Could you please check if there was a breaking change in the update? Thanks.
I’m trying to complete KYC with zkPassport but I don’t have a passport yet. I can provide Aadhaar / driving licence / other government ID. Could you please.
Everytime I try to verify my brazilian passport it shows this error. What should I do?
The app seems to get stuck on at the Ready to Scan screen. For a few moments it appears to register the chip in my passport but it never finalizes. I have tried this on two separate Android devices. Fails on both. Is it possible to do this stage manually?
The documentation states that “just ethereum_sepolia [is supported] for now”. I am interested in verifying proofs on Arbitrum One. Are there any plans to deploy the verifier contract to this L2 chain or others? Would it be possible and/or advisable for a developer to deploy the necessary contracts themselves? Thanks