-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS 8.4 put only works the second time #76
Comments
Could you try using this raw file https://storage.cloud.google.com/ydn-db-d1/1.3.2/ydn.db-isw-core-e-cur-qry-dev-raw.js ? Thanks for the report. |
With that raw file the result is the same: on an iOS 8.4 UIWebView I have to run the app twice for the record to be added. |
Can you figure out why? |
I have faced the same issue when i ran my web app on ios10.0.2 . After second time ,it shows like that : unable to open database (14 unable to open database file) And i use the same js plugin mentioned above. Have you ever solved this issue? @yathit |
Hi, thanks for this awesome library. I was just playing around with it and found two very related issues:
With this simple code:
The
put
call only works the second time I run the app on an iPhone with iOS 8.4 (the code runs inside a UIWebView). This is the output:First run
Second run
Third run
The same code inside a UIWebView on iOS 7.1 works just fine:
First run
Second run
So that's the first issue I wanted to report.
I then went ahead and created a Plunker to be able to try the code in iOS Safari (instead of the UIWebView): http://embed.plnkr.co/ldYHBaXhkyrMw9ksSYqj/preview
Note that the code in that Plunker contains:
These are the different scenarios:
mechanisms
: works finemechanisms
:ydn.db.TimeoutError
when creating the databasemechanisms
: creates the database but needs two calls toput
to actually add the record (just like the first with UIWebView).mechanisms
doesn't make a difference in UIWebView: even with it we need two calls toput
.I'm using YDN-DB I got from this page, more specifically from here.
Thanks!
The text was updated successfully, but these errors were encountered: