BitShares Forum
Main => Technical Support => Topic started by: merivercap on February 27, 2016, 06:38:37 am
-
I have issues accessing the webwallet from the mobile browser. I get a blank screen on my iPhone5.
Does anyone know what the reason may be? I heard others are able to access it fine with an iPhone 6 or android.
Does anyone else have the same problem or know what the reason can be? Thanks!
-
Me too
-
What phone do you have @ebit?
Also do you know a lot of people in China using 2G? Just curious. I know there are less and less people using 2G, but just wondering how long it will take before everyone is on 3G/4G there. Thanks.
-
The web wallet doesn't not work well with Safari ..
As far as I know this has to do either with the websocket implementation or the local database store ..
We had a warning for those browsers earlier .. not sure what it has been removed.
Could you try Safrai on a Mac and open the development console to see if there are javascript errors?
-
What phone do you have @ebit?
Also do you know a lot of people in China using 2G? Just curious. I know there are less and less people using 2G, but just wondering how long it will take before everyone is on 3G/4G there. Thanks.
I use wifi
-
The web wallet doesn't not work well with Safari ..
As far as I know this has to do either with the websocket implementation or the local database store ..
We had a warning for those browsers earlier .. not sure what it has been removed.
Could you try Safrai on a Mac and open the development console to see if there are javascript errors?
Thanks @xeroc. I wish I had a Mac to test on.
I don't think it's entirely a Safari issue because from what I understand the iPhone6/Safari works fine.
As you mention it may have something to do with websockets and particularly on ios7 devices. It doesn't initialize correctly. The url always goes to: https://bitshares.openledger.info/#/init-error
Here are some links to resolving similar Safari/iOS websocket issues. Hope it can help:
http://stackoverflow.com/questions/5574385/websockets-on-ios?answertab=votes#tab-top
Matthew Levine's fix:
me = this // strange javascript convention
this.socket = new WebSocket(url);
// put onmessage function in setTimeout to get around ios websocket crash
this.socket.onmessage = function(evt) { setTimeout(function() {me.onMessageHandler(evt);}, 0); };
Mobile Safari crash when returning to WebSocket page
https://gist.github.com/mloughran/2052006
Safari (IOS and osx) crashes when connected to websockets
https://github.com/SignalR/SignalR/issues/2650