I am using the Facebook API to post messages to Facebook from my Android app. I have tested it out on various different phones, yet on one particular phone the Facebook API just pops up a blank white dialogue window that doesn't load the FB log in page.
I have tested it on the Samsung Galaxy S, the HTC Desire, HTC Sensation and it works fine - but when I try it on the HTC Wildfire S it does not work.
There are no messages popping up in LogCat and stepping through it with the debugger does not reveal any problems.
Looking through the code provided by Facebook I can see it is just a WebView which is being created. There is a function called onPageFinished(..) which gets called but there is nothing in the WebView.
I'm not really sure what to try to fix this. I've tried clearing some settings on the phone but that did not work. Does anybody have any ideas?
Related
I recently detected an issue what I can only reproduce with a Samsung Galaxy S5 and Android 5.x (not with a HTC One, Android 5.x).
When opening a link in a WebView (target=_blank), then nothing happens. I can see an exception in the Logcat output, but the WebView WebViewClient Method shouldOverrideUrlLoading is never called (There I create an intent what opens the url).
My current workaround is to remove the target=_blank from all links - but does anyone knows if this is a Bug or a normal behaviour and I've set something wrong?
Thanks
So I have an app wherein ads appear at the bottom of the screen. When the ad is clicked, landing page should open in the device browser. However in some cases, it opens in the bottom area on the app itself (where the ad is shown). Has someone else also faced this issue? How to drill down to the reason? How to fix it?
I tried testing the app on a number of devices and saw the same happening for Micromax as well. The issue was seen on Samsung Galaxy : Android 4.4.2, Kernel version 3.4.0, Chrome 37.0.2062.117; and on Micromax: Android 4.4.2, Kernel version 3.4.67, Chrome 35.0.1916.141
I also tested the landing page url on mobi.ready and it reported some XHTML markup issues. Is that the reason?
We have a Javascript bug that only appears in the stock browser of the Galaxy S4 (GT-I9505) running KitKat (4.4.2) and we're unable to debug it or view the Javascript console. I've tried running about:debug and it does enable the debug menu, but it also redirects me to a 'page not found' and going back/forwards removes the debug menu.
We've also tried using logcat, but no messages are shown (this command works perfectly on a Nexus 4 JellyBean and in an emulated Gingerbread).
adb logcat browser:V WebCore:V Console:V *:S
We've also tried JSConsole and Firebug Lite but nothing useful is shown on their console. We also implemented the 'DIY Console' as suggested by EclipseSource and while it did show an error, it doesn't tell us which file the error comes from or any specific details.
Does anybody have any other suggestions for things to try, or a solution as to why about:debug isn't behaving properly?
I don't know if this will work for you, but I have a Galaxy S4 and I was able to see console messages this way:
Plug in your phone, make sure you're getting all the logcat messages
Add this filter: INFO:CONSOLE
Javascript errors are printed under the chromium tag and the "Info" log level
I'm developing for android (API 14) deploying for Nexus One on Genymotion simulator and to a Galaxy Note N8000 tablet, but my app it's having a strange behaviour: in one of the activities, when I press the back button, the app shows the right activity but my debugger disconnects.
Using the simulated Nexus One I have a log message related to OpenGL out of memory and I've found out that OpenGL support for simulators it's usually bad, but using physical note n8000 I have nothing in my logs that can help me. The app behaves like it should but I loose debugging.
Does anyone had a problem similar to that? How did you fix it?
I face the same issue sometimes, my guess is that the Exception actually forces application closing (disconnecting it from debugger), but somehow it gets automatically restarted restoring the previous 'state'.
In your case, maybe is just a simulator issue, but you should consider testing in a real Nexus One device, just to make sure.
Major head scratcher happening today. I developed a Cake app, hosted on Pagoda Box, that runs fine on all browsers except Android native browser on the Galaxy S3. It displays a white screen:
http://broomage.pagodabox.com/sweepstakes/MetsMoments2013
However, I uploaded this app to a standard LAMP server so I could debug it more quickly, and it showed up just fine! See here:
http://epi.qa/broomage/sweepstakes/MetsMoments2013
I'm really mystified at this point, since it now seems specific to Pagoda Box. I've checked the apache/php/cake logs and nothing weird is showing up. I can also "view source" and see that everything seems to be loading properly--only the browser just shows a white screen. This problem also happens on certain sites that use the Bootstrap library, but will sometimes show up if you go to another URL then hit the back button. But this particular site just shows a white screen on the S3 no matter what I do. Any ideas???
Grrr, I think I narrowed it down to a gzip issue: If you are serving certain assets thru a php script, the size may be reported as a mismatch w/ the compressed size, which screws up rendering on lackluster browsers like that of android.