-
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
VRS: cannot find certificate #77
Comments
In order to fix this bug it is enough to change the Bundle.module to Bundle.main in VrsProvider.swift line 31. This will allow all Users that use VRS to be able to integrate the package directly from SPM. Currently a workaround is needed for VRS users. |
Hi @cseh17, sorry for the long delay. I am struggling to reproduce the issue on my side: VrsProvider(certAuthorization: ["certName": "vrs-client-certificate.pfx", "password": "..."]) Could you please try the same or send me a sample project? |
I have tried it again and it seems to work now. Question: when can we expect a new version with the changes? |
Sorry, I have somewhat neglected to update the version in the past months. It used to match the versions of ÖPNV Navigator, but I don't think this is a great way moving forward. |
I'd like to reopen this issue as I have new information to share. Upon doing some further testing, I have discovered the following: However, in my scenario, if your certificate is situated outside the framework and elsewhere within the project structure, Bundle.module will only search within the framework structure. Oppositely, Bundle.main appears to search throughout the entire project structure, including within the framework (although I'm not 100% about the framework part). |
Thank you, I will recheck this later. |
Any update on this issue? |
When importing TripKit using SPM, the certificate for the VRS provider (vrs-client-certificate.pfx) cannot be found.
The text was updated successfully, but these errors were encountered: