-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cobra Issue: running alongside Porcupine Angular creates IO_ERROR
#109
Comments
thanks for the report. can you please share a repo that allows us to reproduce the issue and then we can work on it? it is ok if the repo is private. |
cobra bug.zip |
@sandeepsn1997 Thank you for sharing the project, but I couldn't reproduce the issue described above as it only has Cobra and not Porcupine. Can you send me either another project with the problem you mentioned or a step-by-step guide on reproducing it with the one you already sent? P.S: I deleted the link to the attached project since it has your |
IOError
IOError
IO_ERROR
@sandeepsn1997 I was able to reproduce what you got by creating a dummy angular project, and released a hotfix for our Cobra web binding, could you please try version |
Hello @mrrostam, I deleted the link to the attached project Thanks, I realised it after uploading🙂. |
@sandeepsn1997 We are looking forward to seeing your projects. keep us posted! |
Cobra stops working when porcupine service in installed and used in angular
getting this error
core.mjs:6494 ERROR Error: Uncaught (in promise): Error: 'pv_cobra_init' failed with status IO_ERROR
at resolvePromise (zone.js:1211:1)
at zone.js:1118:1
at asyncGeneratorStep (asyncToGenerator.js:6:1)
at _throw (asyncToGenerator.js:29:1)
at _ZoneDelegate.invoke (zone.js:372:1)
at Object.onInvoke (core.mjs:25608:1)
at _ZoneDelegate.invoke (zone.js:371:1)
at Zone.run (zone.js:134:1)
at zone.js:1275:1
at _ZoneDelegate.invokeTask (zone.js:406:1)
when working with only cobra VAD it works fine, but once i installed porcupine service it stops working
The text was updated successfully, but these errors were encountered: