I've created a BlackBerry webworks application that consists of multiple pages each loading data from a local SQLite database.
The application works fine until I've navigated between a certain number of pages, at which time the application shows a blank alert box and hangs on the loading screen that shows between pages.
This is using the Bold 9700 simulator but also occurs on the device itself. I've tried disabling caching, as well as increasing the size of the cache, both to no avail. The console shows nothing, neither does the event log on the simulator.
Has anyone come across this behaviour before? More importantly, how do I get any useful debug information out of the simulator so I can track down the culprit?
Many thanks!
Edit: I've tracked this down the the html5_init.js library that Blackberry recommend for translating HTML5 to Google Gears calls for OS5. Any ideas?
Further Edit: I've removed all traces of html5_init.js and instead I'm using the Google Gears API directly. This resolves the problem but requires that I double up all my database code. Google Gears requires that you call clear() on all ResultSets so that they don't cause a memory leak but html5_init doesn't offer that functionality. Maybe that could be the cause?
Related
My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.
When I open my Firebase hosted site (built with Polymer Starter Kit) using my computer that I deployed (i.e., using $ firebase deploy) the app from, it works great. It works on all browsers too.
However, when I try to open it on my mobile device (an Android tablet in this case) I get a Site Not Found Error. The full error text message reads as follows:
Site Not Found
Why am I seeing this?
There are a few potential reasons:
You haven't deployed an app yet.
You may have deployed an empty directory.
This is a custom domain but we haven't finished setting it up yet.
How can I deploy my first app?
Refer to our hosting documentation to get started.
Obviously, none of the possible causes listed are actually the case because, as mentioned, the site tests fine on my deploying device. And on all browsers on that device.
Question
What could be causing this?
TL;DR: User error. Problem fixed.
I just tested it again and it worked on the other devices. Since I was not clicking a link, but rather, typing it instead, I think that was what caused the problem.
I think what happened was the "en dash" character on some soft keypads looks like a different character (maybe em dash?) which causes the typed URL not to match the actual URL if the user is not used to typing out URLs and doesn't know how to tell the difference on a soft keypad between the different types of dashes.
I have a webapp that I created well over a year ago, and running on iOS 6, it's been rock solid. It's designed to work offline and online, from the same home screen icon. I've got a manifest file that loads up the bootstrap javascript, all the js includes, and the core files. The app is designed to store data while offline (using SQLite) then transfer anything in the offline queue to a MySQL database once online. And again, all this was working on iOS 6 with absolutely no changes whatsoever to any of the files, the manifest, etc. for months.
Then I upgraded to iOS 7.
Now I have a host of problems, but they all seem to revolve around database issues. I'm getting a lot of code 6 errors in Chrome (in Safari, I get nothing, just a blank screen). In my reading up on this I found that Apple did make some sort of change to how SQLite runs, but not being an xcode developer I don't have access to the materials on Apple's site, and since I'm not running xcode in any case I don't know if that even applies to my purely HTML app.
My question, then, is this: with whatever changes Apple made on the app side, is there anything that would have affected the functionality of a pure HTML5/JS/SQLite offline web app, bookmarked to the home page via Safari?
IOS 7 limit browser DB size from 50MB to 5MB , is that the reason ? Also I met a end user turn on Private Browsing in their IPAD , also could cause this trouble, hope that helps.
you can check this :http://www.mobilexweb.com/blog/safari-ios7-html5-problems-apis-review
I figgured it out.When you enter safari, a little button on the top left on the keyboard says "private", click it to disable it. The database will work fine. But! jquery mobile will not be able to use the back button. For this, you have to delete appcache from your code. jquerymobile 1.4 will fix this, but for now you will have to live without appcache!
I am working on a simple mobile web app and I am having trouble logging in...
I followed this little sample on making a custom login: http://blog.benmcmahen.com/post/41741539120/building-a-customized-accounts-ui-for-meteor
Nothing too tricky here.
So I run my meteor server locally. On my computer, through the browser, I can log in and create accounts -- no problem.
When I go to my local IP from my iPhone, the website successfully loads but for some reason I am not able to login or create accounts.
I have noticed that for Meteor.loginWithPassword and Meteor.createUser, the callback function NEVER gets called. I have {{loggingIn}} rendering a loading screen and the loading screen is only there for a fraction of a second before the form is reloaded. No errors are thrown (validation passes and the callback function doesnt fail).
Out of suspicion, I deployed the app and tried accessing the deployed website from my phone and the same issue persists...
Any ideas what I cannot log in or create accounts on my iPhone, but I can on my computer? Maybe its a cookies thing? Any ways of solving this?
Thanks a lot,
Chet
Edit:
This works on both my desktop browser and iPhone simulator. Just not my iPhone. Could it just be a local network issue? -- No, even if I deploy the website, I have the same issues...
Also, check out my github post about recreating the issue:
https://github.com/ccorcos/meteorPasswordMobileError
Check to make sure that you are running the same version of iOS on all the devices you are testing on. I have seen iOS 7 misbehave when using Meteor apps. iOS 6 works just fine.
I'm a C++ programmer, but I'm a newbie in Flex. I'm developing a Flex 3 application for a social network using the FlashDevelop. For debugging I'm using the stand-alone FlashPlayer (10.3 debug) downloaded from Adobe. The application is a simple audio player which shows artist/album images.
The application worked properly on both local computer and remote server until I made some layout changes in Main.mxml. I added some HBoxes and changed Image placement. After that the application still works on my local computer, but it doesn't work properly after I upload it to a server.
Application buttons are not highlighted on over/out/click events, images loaded from the Internet are not displayed, text changed dynamically is not displayed, but when I click buttons a sound file is loaded from the internet and starts playing. It looks like some events which are responsible for components displaying are not dispatched, because some part of functionality not related to displaying still works.
To make sure that this is not a server problem, I rolled back to the previous revision. All works fine.
I suppose that this is a known issue, but I have no idea what is the reason.
Could anyone please help me to resolve the issue?
Thanks.
UDP: I observed the issue in IE and FF, I didn't test Opera and Chrome.
Are you tying to access the pixel data of the images in the new version? If so, that might be the problem, as pixel data for loaded images is not (always) accessible so that might throw a security error, which in turns breaks the rest of the interface.
Also, did you try running the remote version in the debugger? If so, is there any exception being thrown?
And no, it's not a known issue, it's the kind of annoying and hard to debug error that you sometime get when using the Flex SDK.