4 ms·

I really, really need to get this fixed, we're in the middle of selling a web-based ipad app to a very large client, utilizing the local caching. This is a terr

by kilian 16y ago

I really, really need to get this fixed, we're in the middle of selling a web-based ipad app to a very large client, utilizing the local caching. This is a terrible bug for me :(

jarin 16y ago
One of the golden rules of iOS development is "work with what you've got". I'd get started on a workaround.
- jrockway 16y ago
  One of the golden rules of developing for a proprietary platform is "work with what you've got". I'd get started on a workaround. Fixed that for you. Windows developers have the same problems.
  - mooism2 16y ago
    I upvoted you because I didn't think your comment deserved a subzero karma. But the snark was unnecessary.
  - DerekL 16y ago
    Don't open source operating systems have the same problem? It's legally and technically possible to fix or improve the system, but you may not have the skill or time. You also have to convince the maintainers to accept your patch and wait for your users to upgrade. No matter what system you write for, you have to work with what you've got. All open source lets you do is fork it and distribute your own version of the OS.
  - joebadmo 16y ago
    That's true enough, but there's a bigger distinction, isn't there? Maybe the better golden rule for developing for iOS is "work with what Apple will let you"? My point being Windows developers do not have exactly the same problems.
deleted 16y ago
[deleted]
spoondan 16y ago
Why do you need this fixed? Your app, even running in full screen, probably runs faster on iOS 4.3 than it did on any previous version of iOS.
- jerome_bent 16y ago
  The OP said "local caching" not speed. I'm surprised the local caching hasn't gotten the media spotlight as that's been broken since 4.2.1. and is more important for web apps aiming to replace native apps.
lukifer 16y ago
It's sad that Apple has a disincentive against improving web-based dev tools. On my own project, I keep bumping up against unnecessary limitations on touch and focus events for form fields. For what it's worth, local caching should still work fine, either in Safari or UIWebView, so long as it doesn't involve natively executed ARM code.
deleted 16y ago
[deleted]
some1else 16y ago
Did you try and package fallback versions of files into a native app and load them with a UIWebView unless there's an internet connection? It's not perfect, but it could save your ass until they fix the bug. Afterwards, make sure you don't forget how much Apple cares about you if you're not in line with their objectives :-)
some1else 16y ago
Did you try and package fallback versions of files into a native app and load them with a UIWebView unless there's an internet connection? It's not perfect, but it could save your ass until they fix the bug. Afterwards, make sure you don't forget how much Apple cares about you if you're not in line with their objectives :-)

by kilian 16y ago

I really, really need to get this fixed, we're in the middle of selling a web-based ipad app to a very large client, utilizing the local caching. This is a terrible bug for me :(

jarin 16y ago

One of the golden rules of iOS development is "work with what you've got". I'd get started on a workaround.

jrockway 16y ago
One of the golden rules of developing for a proprietary platform is "work with what you've got". I'd get started on a workaround. Fixed that for you. Windows developers have the same problems.
- mooism2 16y ago
  I upvoted you because I didn't think your comment deserved a subzero karma. But the snark was unnecessary.
- DerekL 16y ago
  Don't open source operating systems have the same problem? It's legally and technically possible to fix or improve the system, but you may not have the skill or time. You also have to convince the maintainers to accept your patch and wait for your users to upgrade. No matter what system you write for, you have to work with what you've got. All open source lets you do is fork it and distribute your own version of the OS.
- joebadmo 16y ago
  That's true enough, but there's a bigger distinction, isn't there? Maybe the better golden rule for developing for iOS is "work with what Apple will let you"? My point being Windows developers do not have exactly the same problems.

deleted 16y ago

[deleted]

spoondan 16y ago

Why do you need this fixed? Your app, even running in full screen, probably runs faster on iOS 4.3 than it did on any previous version of iOS.

jerome_bent 16y ago
The OP said "local caching" not speed. I'm surprised the local caching hasn't gotten the media spotlight as that's been broken since 4.2.1. and is more important for web apps aiming to replace native apps.

lukifer 16y ago

It's sad that Apple has a disincentive against improving web-based dev tools. On my own project, I keep bumping up against unnecessary limitations on touch and focus events for form fields. For what it's worth, local caching should still work fine, either in Safari or UIWebView, so long as it doesn't involve natively executed ARM code.

deleted 16y ago

[deleted]

some1else 16y ago

Did you try and package fallback versions of files into a native app and load them with a UIWebView unless there's an internet connection? It's not perfect, but it could save your ass until they fix the bug. Afterwards, make sure you don't forget how much Apple cares about you if you're not in line with their objectives :-)

some1else 16y ago