I have an activity which handles any URL events within my application and it opens them within a web view. The issue which I currently have is that if i turn off the WiFi and turn it back on the URLs which were previously working before in the webview do not load and it eventually timeouts. The puzzling thing is that I have tried this within the same application across other phones (HTC, Samsung S5, LG Nexus 5, Samsung S4, One Plus One) and it works perfectly.
I am wondering if anyone has a solution for this or at least an explanation as to why this is happening.
The reason I'm asking this is on here is because although it seems to be a device specific issue, before to get another issue with my webview to work with samsungs i had to enable webView.getSettings().setCacheMode(WebSettings.LOAD_NO_CACHE);
I want to know if there would be something similar to help me with this S6 issue.
Related
I have a problem on galaxy s8 and galaxy s9 with dynamic links from firebase. On other android devices it works. A strange loading screen appears, then returns to the application from which there was an attempt to open the application. Anyone had a similar problem or potentially knows a solution? The application is not installed. Certificate SHA-1 is attached. https://drive.google.com/open?id=15BTDWjFgMtijZ7RVILN7DUq-fG0BzlE7
on the next day the links started to work correctly ... it looked like a problem with permissions on devices
I created a simple HTML page that displays the problem.
With Chrome desktop version is okay but trying on different mobile device and with different browsers it becomes obvious that there is a bug.
Scrolling down, in my example with Samsung S6 and Chrome, appear a white band on the bottom of the screen that disappears after less than one second.
I believe this problem is generated from the header of Chrome (or browser you use) that disappears when you scroll down.
I created an example JSFiddle and loaded the HTML page on my server.
On the web I did not find answers to my question, I hope someone is able to help me.
Thank you all in advance.
Tests performed (and failed) with:
Samsung S6 and Chrome
Samsung S6 and Samsung Browser
IPhone 6S and Safari
LG G4 and Chrome
LG G4 and LG Browser
We have a hybrid app running on Android and IOS with several hundred users so far. Out of that number we have come across 2 phones that will not render the webpages of our site properly, a Vodafone Prime 6 and a Samsung Galaxy Ace 3. Here's a screenshot from the Prime.
The webpages use IFrames and SmartMenus, otherwise nothing unusual I don't think. Does anyone have any suggestions on how to fix this issue please?
Using jSignature (https://github.com/willowsystems/jSignature) within a PhoneGap, JQuery Mobile application.
When trying to sign in the content div using the Samsung Galaxy S4 the drawn line is not displaying. The signature is there when I pull the data but is for some reason not displaying. Any ideas why this might be? It has been working on other devices such as Samsung Galaxy S3, iPhone, and iPad.
<script>
var signatureContentDiv = $("#signatureContentDiv");
signatureContentDiv.html("");
signatureContentDiv.jSignature();
</script>
<div id="signatureContentDiv"></div>
I have also just run into this. For me, the error appears on the Galaxy Note 2.0 while running Chrome. I tried changing to Firefox and it works properly. The same behavior is noted when trying the demo directly on jSignatures site. I would suggest checking against their site and seeing if your device works properly to eliminate your code being the issue.
Hopefully this will get fixed.
Additional Info: I have just determined that it seems to be based on the dimensions of the image. Anything over 66,000 pixels (such as 600x110) will cause the failure. This still seems to only happen on certain devices, all running the same version of Chrome.
Interesting that I wind up responding to the last thread I answered about this issue almost 2 years ago.
It seems the most recent update to Chrome on Android (V 43.0.2357.78) causes new failures to jSignature. If the page is in it's native size (no browser zooming), it works properly. If you zoom the screen, it fails. This is new behavior (on existing code). Other browsers seem to work properly.
We released a new app which has a widget. This works fine so far on all devices, however on Samsung Galaxy S3 we get reports that it stops working in certain situations.
Unfortunately I do not have such a device to check myself - therefore I would just like to know if anyone had some similar experience.
The widget stops working after the screen redraws itself (which seems to happen on the S3 regularly and randomly). Another user reported that the widget stops working after invoking the Task Manager and "clearing memory". There is no crash - in this case unfortunately.
The app has been tested on many devices with different Android versions - so far we have never seen such a random screen update which caused the widget to stop working.
I am thankfull for any hints.
...in fact it turned out to be a fault in Samsung's Android implemenation - they promised to fix it in the upcoming release. Thanks to Samsung amazing support we finally could confirm this issue !