verify() function returns false for all proofs in example iOS app

[iammatthias]

Environment

• Platform: iOS 17+
• Device: iPhone (Apple A17 Pro GPU)
• Framework: IMP1
• Device Type: DeviceType.CpuMetal
• Language: Swift
• Application: IMP1FrameworkExample (provided example iOS app)

---

Issue

The verify() function returns VerifierFailure for all proofs in the example iOS app, including those successfully generated by prove() using the bundled example circuits.

---

Expected vs Actual

• Expected: verify() returns VerifierSuccess for valid proofs generated from example circuits
• Actual: verify() returns VerifierFailure for all proofs using example circuits

Logs

[INFO] Metal device 'Apple A17 Pro GPU' initialized successfully.
[WARNING] Metal backend doesn't support async calls when using host memory.

=== SINGLE PROOF TESTS ===

reclaim-aes-128-ctr:
Proof generation: 0.305s ✅
Verification: 0.012s ❌ FAILED
File sizes: proof=856B, public=9858B, vk=260394B
Protocol: groth16, Curve: bn128, nPublic: 1408
Public inputs: 1408/1408 ✅

reclaim-aes-256-ctr:
Proof generation: 0.260s ✅
Verification: 0.012s ❌ FAILED
File sizes: proof=855B, public=9858B, vk=260408B
Protocol: groth16, Curve: bn128, nPublic: 1408
Public inputs: 1408/1408 ✅

reclaim-chacha20:
Proof generation: 0.187s ✅
Verification: 0.014s ❌ FAILED
File sizes: proof=856B, public=15234B, vk=400902B
Protocol: groth16, Curve: bn128, nPublic: 2176
Public inputs: 2176/2176 ✅

sha256:
Proof generation: 0.170s ✅
Verification: 0.005s ❌ FAILED
File sizes: proof=852B, public=1794B, vk=49594B
Protocol: groth16, Curve: bn128, nPublic: 256
Public inputs: 256/256 ✅

=== PARALLEL PROOF TESTS ===

reclaim-aes-128-ctr (2x):
Proof generation: 0.265s ✅ (2/2 successful)
Verification: 0.022s ❌ (0/2 successful)

reclaim-aes-256-ctr (2x):
Proof generation: 0.417s ✅ (2/2 successful)
Verification: 0.026s ❌ (0/2 successful)

reclaim-chacha20 (2x):
Proof generation: 0.284s ✅ (2/2 successful)
Verification: 0.029s ❌ (0/2 successful)

sha256 (2x):
Proof generation: 0.277s ✅ (2/2 successful)
Verification: 0.011s ❌ (0/2 successful)

=== SUMMARY ===
Total verifications: 0/12 successful (100% failure rate)
All proofs generated successfully
All verifications failed in ~0.005-0.015 seconds

[jeremyfelder]

@iammatthias Thanks for opening the issue. What version of the framework and what commit for the example app are you using? We are trying to reproduce the issue

[iammatthias]

Hi Jeremy, I was using a fresh clone of the repo. Commit df5c750. No changes to the example iOS app, I just built it and ran it on my iPhone 15 Pro Max. After the initial verification failure I added some additional logs before reporting the issue.