Community

We are evaluating the EUDI Wallet Reference Implementation for a project that needs SD-JWT VC issuance and presentation on both iOS and Android. What is a reliable way to assess platform readiness before committing a delivery plan?\n\nI would like to compare the published feature status with a small end-to-end test: issue a credential, store it, request selected claims, and verify the presentation. Which version details and edge cases should we record?\n\nFor background, this question was prompted by an older [Reference Implementation roadmap discussion](https://github.com/eu-digital-identity-wallet/eudi-wallet-reference-implementation-roadmap/discussions/59); its release dates should not be treated as current.

I am putting together a safe troubleshooting checklist for cases where a wallet returns an SD-JWT VC presentation but the verifier cannot match or decode it. Which request details and redacted diagnostics make a report useful to the verifier or wallet maintainers?\n\nI plan to capture the wallet and verifier versions, credential format, requested claims, and the exact reproducible steps. What should be removed or replaced before sharing logs? This is a new, generalized prompt informed by an [older public interoperability thread](https://github.com/eu-digital-identity-wallet/eudi-wallet-reference-implementation-roadmap/discussions/61), not a reproduction of its payload or environment.

A wallet can hold more than one credential format, and a verifier request may accept only a particular format and set of claims. When a PID is not offered or cannot satisfy a request, what should an integration team compare first?\n\nI am looking for a repeatable diagnostic that covers the credential selected in the wallet, the requested format, and the verifier’s input descriptor—without sharing personal data or full presentation tokens. An older [EUDI Reference Implementation discussion](https://github.com/eu-digital-identity-wallet/eudi-wallet-reference-implementation-roadmap/discussions/61) raised a similar interoperability issue.