- General
-
Preguntes
-1
Respost
BioWallet server down?
I'm receiving the message "Could not connect to server for communicating with BioWallet. Try again later..." on trying to use Chrome Extension. Am I doing something wrong?
Answer
0
Answer
Respost
Mobbeel fa 13 anys
Hi, after a lot of work we have been able to solve the issue.
Please ensure you have the latest Chome extension (1.0.8) that solves the problem. It should get updated automatically shortly, but you always can force the update with the "Update extensions now" option in the extension management page.
Please accept our apologies for this unacceptable disruption in the service. We are taking measures to make sure this won't happen again in the future.
Mobbeel Team.
Hello Gilmar,
Could you tell us what version of Chrome you're using? We've got a known issue with the latest beta and dev version of the browser.
Thanks.
Hello. This is an almost forgotten past 7 years old issue. But I noticed the biowalleet2broser chrome extension mentioned is not anymore available and I need to export my Mobbell signatures fromone phone to another and cannot find the way to export the data without the chrome browser extension.
-2
There is a known bug with the beta and dev channel. BioWallet2Browser won't work with those versions until we fix the bug. Sorry about that, we are currently working on it.
If you want to use it, you should install the stable version versión (13.X).
+1
I'm having this issue with Chrome 16.0.912.63, on Mac OSx Snow Lepoard. This post was 5 months ago, please tell me the issue has been fixed!? I can't add any new website details.. this is most frustrating to say the least.
-2
Definitly frustrating as you say. I continue to feel the outraging issue on Chrome version 16.0.912.63 m under Windows 7, pointing that its a mobeel or Chrome plugin issue. So I don't belieive the issue has really been fixed 5 months ago. I have the Biowallet Signature Version 1.6 and the Biowallet 2 Browser Version 1.1. installed and running, My Biowallet Signature is open bit I always get the bloody ![image.png]( "image.png")
pop out. each time I trigger the Chrome plugin button. I tried almost everything but the full erase and reinstall. It seems that mobbeel has got a real issue by now, but they do not seem to care about it. The security is really tight because Chrome is allegedely the only browser supported and it does not work at all !!!
I do not know how to complain further. If you succeed, please let us know.
Dario CIPRUT.
Glad to know I'm not the only one. Devs... please give us an update on this.. right now you have a product that no-longer works... this is unacceptable.. if it was a minor bug, fair enough.. but the product won't work at all!
Please provide an update on the issue you are facing and information as to a fix release date.
Thanks
Searching answer
Hi everybody and sorry for the lack of information. We have had a problem with the notification email and we didn't notice your questions until another user has notified us via Twitter.
We are actively working on the issue with BioWallet2Browser but unfortunately we don't have a fix yet. Our product uses a protocol called WebSocket to instantly send the username/password to your browser as soon as the mobile phone sends them. The specification of this protocol has changed and Chrome 16+ no longer works with the old specification. We are relying on a third party framework that implements this protocol and, unfortunately, this framework hasn't been updated and the developers are not responding to any of our requests. It already happened some months ago but in that occasion the developers responded and we were able to solve the issue. This time, after a few days without any response we are looking for alternatives, but selecting and replacing it is not an easy task.
Please accept our apologies for this unacceptable disruption in the service. We are trying our best to solve it ASAP and we promise to keep you up-to-date with the progress.
Mobbeel Team.
Mobbeel team has answered by now. They are working hard to get a solution, as shown in a recent post.
Thanks Mobbeel team, good luck with the fix with existing framework/alternative. Pls keep us posted!
Answer
Respost
Hi, after a lot of work we have been able to solve the issue.
Please ensure you have the latest Chome extension (1.0.8) that solves the problem. It should get updated automatically shortly, but you always can force the update with the "Update extensions now" option in the extension management page.
Please accept our apologies for this unacceptable disruption in the service. We are taking measures to make sure this won't happen again in the future.
Mobbeel Team.
Customer support service by UserEcho
