I am working on a socket.io implementation of room based chat system. The web app works perfectly in Firefox, however, in Chrome, only one way communication is achieved. That is, the client in Chrome mobile version, doesn't receive the updates emitted from other devices, but is able to emit messages to other devices. Also, please note that things work perfectly, when tried in Firefox Mobile, Firefox Desktop or Chrome Desktop.
Some other answers suggest that this may be a version issue but all the modules are upto date.
Is it a common issue? Please help.
For others facing similar issue :
Switching off "Data Saver" in chrome mobile solved the problem for me!
Related
I'm having an issue related to a PWA which was created using Blazor.
This app worked fine until yesterday which starting failing in Google Chrome in mobile devices only.
I'm using Chrome 91.0.4472.88 Android 8.0
The weird thing is that the app is working fine in mobile Opera and also in any browser in desktop computers.
The app is hosted using IIS 10.0
I debugged a bit and I found this error output
This error is only happening in Google Chrome mobile version.
I tried updating to target build net 5.0, maybe this has been solved, but it does not fix the error.
I found some related links to this issue, but no luck
https://github.com/dotnet/aspnetcore/issues/26698
https://github.com/dotnet/runtime/issues/42628
Anyone has an idea how to fix this problem? I'm out of ideas.
This appears to be something with Chrome 91, which has all kinds of significant performance optimizations that, for me, tanked Blazor apps (or at least mine). My app will work on Android Firefox, but I get errors like this, and/or memory errors, since the browser updated to 91. I find it hard to believe that we're the only ones, but I haven't seen any wider concern among Blazor devs.
Then goes on to say look in console. Problem is it works fine on desktop, no problems at all. It was also working fine on mobile 2 days ago and no changes. So on mobile there is no console. I have even tried Googles example # https://developers.google.com/maps/documentation/javascript/examples/marker-simple with obviously my API key and the same problem, works fine on desktop in all browser but not on mobile in either chrome and firefox. Thing is I am also getting the same problem with recapture (just spins forever), works fine on desktop but not on mobile chrome but works on mobile phone with firefox. This is driving me crazy. I have tried tow different phones.
OK ended up creating a new API key and it works, may have been something to do with a long list of credential addresses that I had on that api, no idea.
I have a website that uses (except for other things) AngularJS. This website works perfectly fine on (example):
Google Chrome
IE
Firefox
iOS
Android
However I am having problems with Windows 10 mobile as one of the features is not working correctly (to be more precise it is $interval).
When testing my app on one of the browsers I view website via Web Inspector and go to background code to inspect where exactly the app fails. However I have no idea how to fix the problems that occur on mobile devices - such as Windows 10 Mobile?
How can one debug websites on a mobile device?
Windows 10 Mobile has Edge Browser. Try debugging it in that.
This is might be helpful.
https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/f12-devtools-guide/
for the debugging tool you can use
https://msdn.microsoft.com/library/dn255001(v=vs.85).aspx
I've implemented bootstrap-wysihtml5 editor in one of my website. It works fine everywhere on desktop, iPad and on iphone, but doesn't display at all on Android device. I checked using Chrome browser.
Can anyone please let me know whats wrong there.
Update: On checking 'bootstrap-wysihtml5' from its default website http://www.w3masters.nl/bootstrap-wysihtml5/, found its also not working on Android device (checked on chrome and other android browsers).
The development of WysiHTML5 went on to another website. Maybe the newest version will fix your problem.
GitHub
Well, it's really that. I have a website, https://www.fagakademiet.no, developed with DotNetNuke and we recently upgraded to V7.
Everything works fine in my PC using Chrome, but some people complain that it does not work in their PC's using also Chrome. When they login, the admin toolbar does not work.
It also doesn't work in IE, Opera, Firefox, etc.
Any thoughts?
Often times issues like this are related to browser caching of the resources (JS,CSS,etc)
You might see if a Hard Refresh works for the users.
Also you might check the host settings to see if you have the client dependancy framework and resource minification enabled. Try disabling that if you do and see if that helps.