iOS 8 not working at all. #23

Closed
JerryLumpkins opened this Issue Sep 22, 2014 · 8 comments

Comments

Projects
None yet
3 participants
@JerryLumpkins

Safari in iOS 8 is not recognizing the ydn plugin at all. Have you been able to identify the issues? And do you have any time frame in mind for releasing an update that will work with iOS 8?

@yathit

This comment has been minimized.

Show comment
Hide comment
@yathit

yathit Sep 23, 2014

Owner

iOS Safari 8 and OS X Safari 7.1 has serious bug on creating transaction with multiple stores. The bug is not something we can workaround.

So during the time please use WebSQL for iOS 8, as follow:

var db = new ydn.db.Storage('db name', schema, {mechanisms: ['websql']});
Owner

yathit commented Sep 23, 2014

iOS Safari 8 and OS X Safari 7.1 has serious bug on creating transaction with multiple stores. The bug is not something we can workaround.

So during the time please use WebSQL for iOS 8, as follow:

var db = new ydn.db.Storage('db name', schema, {mechanisms: ['websql']});
@JerryLumpkins

This comment has been minimized.

Show comment
Hide comment
@JerryLumpkins

JerryLumpkins Sep 23, 2014

Thank you for the response. Please keep me posted.

Thank you for the response. Please keep me posted.

@yathit

This comment has been minimized.

Show comment
Hide comment
@yathit

yathit Nov 16, 2014

Owner

Indexeddb in safari is not supported.

Owner

yathit commented Nov 16, 2014

Indexeddb in safari is not supported.

@yathit yathit closed this Nov 16, 2014

@JerryLumpkins

This comment has been minimized.

Show comment
Hide comment
@JerryLumpkins

JerryLumpkins Nov 16, 2014

Hi Kyaw,

I was wondering if you were closing these because of the bugs that exist in
iOS in indexeddb.

I just read through a couple links that are discussing this issue:

http://stackoverflow.com/questions/26019147/primary-key-issue-on-ios8-implementation-of-indexeddb

Do you plan on adding support if apple fixes their bug?
If everybody made their primary keys unique across all object stores, would
indexeddb work in iOS?

Thanks for your efforts,

Jerry Lumpkins
Lead Software Developer
Dakota Software

On Sun, Nov 16, 2014 at 10:00 AM, Kyaw Tun notifications@github.com wrote:

Indexeddb in safari is not supported.


Reply to this email directly or view it on GitHub
#23 (comment).

Life is not a dress rehearsal.

Hi Kyaw,

I was wondering if you were closing these because of the bugs that exist in
iOS in indexeddb.

I just read through a couple links that are discussing this issue:

http://stackoverflow.com/questions/26019147/primary-key-issue-on-ios8-implementation-of-indexeddb

Do you plan on adding support if apple fixes their bug?
If everybody made their primary keys unique across all object stores, would
indexeddb work in iOS?

Thanks for your efforts,

Jerry Lumpkins
Lead Software Developer
Dakota Software

On Sun, Nov 16, 2014 at 10:00 AM, Kyaw Tun notifications@github.com wrote:

Indexeddb in safari is not supported.


Reply to this email directly or view it on GitHub
#23 (comment).

Life is not a dress rehearsal.

@yathit

This comment has been minimized.

Show comment
Hide comment
@yathit

yathit Nov 17, 2014

Owner

Safari has bugs in multi-store transaction and key generations. Working around those bug will cause changes your application logic. It is not just worth it. Apple have to fix them, sooner or later. WebSQL is fine.

You can still use ydn-db for indexeddb in safari, if your application is already aware of those bugs. But default, ydn-db will select websql on safari.

Owner

yathit commented Nov 17, 2014

Safari has bugs in multi-store transaction and key generations. Working around those bug will cause changes your application logic. It is not just worth it. Apple have to fix them, sooner or later. WebSQL is fine.

You can still use ydn-db for indexeddb in safari, if your application is already aware of those bugs. But default, ydn-db will select websql on safari.

@JerryLumpkins

This comment has been minimized.

Show comment
Hide comment
@JerryLumpkins

JerryLumpkins Nov 17, 2014

Hi Kyaw,

I agree. I just wanted to make sure that your plan was to support indexeddb
in Safari after Apple fixes the issues.

Thank you!

j

On Sun, Nov 16, 2014 at 7:52 PM, Kyaw Tun notifications@github.com wrote:

Safari has bugs in multi-store transaction and key generations. Working
around those bug will cause changes your application logic. It is not just
worth it. Apple have to fix them, sooner or later. WebSQL is fine.

You can still use ydn-db for indexeddb in safari, if your application is
already aware of those bugs. But default, ydn-db will select websql on
safari.


Reply to this email directly or view it on GitHub
#23 (comment).

Life is not a dress rehearsal.

Hi Kyaw,

I agree. I just wanted to make sure that your plan was to support indexeddb
in Safari after Apple fixes the issues.

Thank you!

j

On Sun, Nov 16, 2014 at 7:52 PM, Kyaw Tun notifications@github.com wrote:

Safari has bugs in multi-store transaction and key generations. Working
around those bug will cause changes your application logic. It is not just
worth it. Apple have to fix them, sooner or later. WebSQL is fine.

You can still use ydn-db for indexeddb in safari, if your application is
already aware of those bugs. But default, ydn-db will select websql on
safari.


Reply to this email directly or view it on GitHub
#23 (comment).

Life is not a dress rehearsal.

@rosshadden

This comment has been minimized.

Show comment
Hide comment
@rosshadden

rosshadden May 20, 2015

@yathit You said: "You can still use ydn-db for indexeddb in safari, if your application is already aware of those bugs."

My app does not use multi-store transactions or key generations. How do I tell ydn to use the same default fallback array ['indexeddb', 'websql', 'localstorage', 'sessionstorage', 'userdata', 'memory'], but to let safari use indexedDB if present?

@yathit You said: "You can still use ydn-db for indexeddb in safari, if your application is already aware of those bugs."

My app does not use multi-store transactions or key generations. How do I tell ydn to use the same default fallback array ['indexeddb', 'websql', 'localstorage', 'sessionstorage', 'userdata', 'memory'], but to let safari use indexedDB if present?

@yathit

This comment has been minimized.

Show comment
Hide comment
@yathit

yathit May 22, 2015

Owner

Please use rel 1.1.4 (just updated) and provide your preference (as you wrote above) in instantiating ydn.db.Storage. The default don't include 'indexeddb' for Safari browser.

Owner

yathit commented May 22, 2015

Please use rel 1.1.4 (just updated) and provide your preference (as you wrote above) in instantiating ydn.db.Storage. The default don't include 'indexeddb' for Safari browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment