I have an app built around Webview. It has three elements, one a direct link to a website the other two link to internal html files containing java script. The app has been downloaded over 1000 times over the last 2 years without a problem until recently a client reported the internal links threw up "File does not exist or cannot be opened" error.
He reported that the app worked previously on his lenovo device but after a failed upgrade and subsequent factory reset produced the error. Reinstall didn't work.
Is it program error or android issue? Is there a fix?
Yes I came to read that now webview got some authentication issue in loading https pages in latest releases especially when we use onReceivedError() method in it and handle some issue. But I am not 100% sure of it as I havent got this issue. So while using webview properly handle SSl certificate. This issue is occurring only in latest releases. This may fix your issues.
Related
I need to debug my Ionic React application on Android Emulator, but suddenly I cannot see the source file to debug it.
I cannot debug from bundled js, but the css files are fine tho.
It was not like this before, suddenly today it gives me this error, I cannot debug anything.
What can cause this errors? I cannot see the error message everywhere.
Please help.
I HAVE TRIED
I even try to revert to my last git commit when the error was not exist, apparently when I try to debug my last version, this error comes. I suppose there is something wrong with the chrome browser or maybe the Android Emulator.
UPDATE
I tried to remove my Android Emulator and re-created again, but the errors are still there.
I even tried to debug with Microsoft Edge in edge://inspect, there errors are still there.
I tried to open my other application coded in Ionic React, the application was deployed a long time ago without any of these errors, but now the errors are there.
I have no clue what is happening.
USING MOBILE PHONE WORKS
I tried to debug it in my mobile phone. It works there is no error. So I suppose there is a problem on Chrome to Android Emulator communication.
There really is a problem with my Android Emulator. I tried to create another emulator with different API Level. It works, I suppose removing the emulator from AVD Manager in Android Studio and re-create it, does not really reset the emulator.
My problematic emulator was in API 30 after I create API 29 and debug in it, it works fine.
I successfully run the react-native app and emulator also opended.
I'm also getting emulator loading message too
However After that it crashes and nothing display
And I'm getting an error when reload the bundle as below
I'm unable to figure out the issue since I'm a react-native beginner.
Appreciate your suggestions
It seems your emulator not connected to your react-native development server. Sometimes it happen, devices connected and somehow it lost connection with the development server. Try running adb devices command on your terminal to check is your emulator available and detected.
I know this is old but maybe this will help someone else.
This could be happening due to several reasons.
Check emulator is working or if its storage is full? wipe the data.
Syntax error could be because of this. please recheck latest changes files.
Personally, I was stuck due to a small comma error in my code.
often when I have the Chrome Dev Tools open while developing React Native Android on my device, I get the following Error:
Did not get valid calls back from JS: [[],[],[],[],[]]
callFunction
ReactBridge.java:-2
run
CatalystInstanceImpl.java:203
...
Any idea whats wrong?
I'm using react-native v0.19 with a Nexus 5
This error should no longer be appearing as of React Native 0.23 when debugging with Chrome Dev Tools. The issue was the debugger returning "bogus values" to the app when it fails to handle a request. See this commit for the fix.
However, this error still sometimes occurs when debugging with Nuclide. Here is the issue I opened regarding that problem.
Either way, the app showing this error is just a symptom, where the real problem is that a request from the app to the debugger (in its role as the JS engine) couldn't be handled.
One specific reason I ran into was the Batched Bridge not being set, due to the debugger failing to load the JS app bundle (in my case this was caused by issues with the port at which it tried to fetch the bundle). However, there are probably many other reasons this might happen.
When I open a angularjs app in iframe on a page everything works fine on all browsers. But then in firefox if I refresh using ctrl+f5 I get this very nasty error starting with nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame" ...
Please see image: (not sure if you can acutally read it)
You can test it your self, open link https://www.ipushpull.com/embed/SCAR/Alpine in firefox, you should see login form, press ctrl+f5 and you should see the error.
Other browsers are fine.
I seen few other discussions, some mention this could be because of CORS requests (I am using) which I dont see probable because other requests are working fine in firefox on the same page (when you open taht page it makes request to the api that returns what it should)
Other mention it has something to do with window history, which might be because once you arrive to that link and API returns 403, it redirects you to angular uri #/user/login , but I didnt find any solution I could try out with the history.
Any ideas? thanks a lot
Update
I see you cannot open up the image, here is "full-res": http://i.stack.imgur.com/7SYQ8.jpg
Update 2
This is not due to CORS issue. I am using CORS throughout the site without an issue, even there are other CORS requests on that very same page and they work.
It is not caused by any adblock/popupblock addin, I tried in completely wiped out browser.
Using non-minified angular for debugging - Actually I didn't think this would matter for debugging (as I have confidence in angular), but quess what. If I change to un-minified angular the error does not happen.. Any ideas?
I have run into a similar issue trying to open an Ember app using history.pushState (Ember Router location: 'history' method of routing) inside an iframe. It appears the issue only occurs when doing a hard refresh (cmd + shift + r on Mac or ctrl + f5 on Windows) in Firefox. The issue only occurs for me in FireFox, works fine in Chrome and Safari with similar hard refresh. I also verified that the issue occurs for me as well opening an Angular JS app using $locationProvider html5mode(which also uses history.pushState under the hood) in an iframe in FireFox.
The issue does not occur for me when navigating to the page for the first time or when normally refreshing the page (cmd + r Mac, f5 Windows). I have found many seemingly related on Bugzilla for Mozilla but many are close. This one seems to represent the same issue I am having and is still open as of current versions of Firefox (v37.0.1 at time of writing).
https://bugzilla.mozilla.org/show_bug.cgi?id=1003100
Opening either an Ember or Angular app(or whatever technology...) in an iframe which uses hash based routing appears to be a viable work around for now. I could not reproduce the issue using hash based routing methods for either framework.
Minification in AngularJS causes problem if you don't declare the service dependencies list (in an array) followed by the function itself. However, I looked through your code and looks like you got it covered. I could be missing something here, so it's a good idea to go over one more time just in case.
On another hand, it could be false negative. I also got some errors in Chrome when I refresh the page before all the dependency js files are fully loaded. Since you have Firebug Persist mode, some requests are not canceled and causes an overflow exception like the 3rd one in your attached image.
So for this error, if you turn off the watches, they should go away.
I'm wondering if anyone has run into new problems with using the HTML5 application cache in Mobile Safari on iOS 5 devices? I had previously written an offline web app that worked well in iOS 4, but as devices that use this app are being moved over to iOS 5, I am discovering problems when devices are offline and attempting to access what should be cached resources.
I can confirm that the application caching procedure is working as expected, as I can track the hits to my webserver as resources are downloaded while the device is online.
The problem manifests itself in the form of the "Cannot Open Page: Safari cannot open the page because it is not connected to the Internet" dialog box when I attempt to follow a link to a page that should be cached while I am offline.
Interestingly, around the same time this error pops up, in the Debug Console one also gets the "JavaScript execution exceeded timeout" error, similar to what is mentioned in this thread. I'm not doing any computation nearly as complicated as what was posted there, but the suggestion to kill and restart Safari seems to fix both problems, at least for now.
So maybe this question is less a request for help and more of a landing place for future searchers to share their experiences.
Please check if you have added the cached page itself into the manifest file, in below example they are HTMLPage1.htm & HTMLPage2.htm. I have the same problem but it works after adding the cached page link.
CACHE MANIFEST
CACHE:
images/cover.png
HTMLPage1.htm
HTMLPage2.htm
NETWORK:
*