-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sphereon ssi agent not working with docker compose #104
Comments
Hi @Soapfedan Yes, sorry for that. We are in the middle of adding new specification versions and it seems the demo has already seen merges into develop containing the new specifications, without the examples being updated. Since we have not released new versions of the wallet yet, we will be in limbo until roughly middle next week. Sorry for that |
Hi @nklomp, thanks for your reply. Now i solve the problem. I checkout to the previous develop commit (951d10c), where you upgraded the libraries. I already check that my phone reach the endpoint, that endpoint gives me this JWS What am i missing? P.S. My colleague doesn't have the problem with his iOS wallet application |
It has to do with the current Android wallet in the store not allowing http connections and only https. If you would run the app in development mode with a USB cable ot will work. We will probably revert this for next store release as we are getting more reports of people testing against http URLs |
Thanks for the clarification @nklomp |
Hi i'm trying to setup the 3 docker container, but i have a problem with the ssi agent.
I launch the .sh script (./install-configs.sh sphereon http://<my_local_ip>:5000) to setup the conf files, but when i launch the container it exits with the following error:
opt/oid4vc-demo/node_modules/.pnpm/@[email protected][email protected]/node_modules/@sphereon/oid4vci-issuer/dist/builder/VcIssuerBuilder.js:13
2024-06-10 15:47:09 throw new Error('IssuerMetadata should be from type v1_0_13 or higher.');
How can i fix this problem?
Thanks in advance
The text was updated successfully, but these errors were encountered: