2 ms·

I don't understand, why don't you "just" try to support ios 11?

jsnell 7y ago
You've totally misunderstood the OP's story. Their app does not have any kind of dependency on iOS 13 and should work on iOS 11. It's just that there's a correlation between an iOS 11 UA and the app not working. The hypothesis is that there is something wrong with some devices that both a) caused them to not be upgraded, b) causes their app to fail. This kind of misreading is a prime example of just how toxic any discussions about version number detection are. Rather than give the OP any benefit of the doubt and maybe re-read what they wrote, you've just decided they must be incompetent or lazy and castigate them over it.
- skrebbel 7y ago
  Oh come on. I even began my sentence stating that I didn't understand. What more do you want? I was genuinely interested, there's no need to snark. The only thing that's toxic in this thread is your comment. If we're going to begin by assuming that things like "I don't understand" are meaningless hollow phrases that trolls tack on comments just to snark more effectively, then the end is that we simply can't communicate online anymore. Please don't push in that direction, it's not the solution. > you've just decided they must be incompetent or lazy and castigate them over it. I did no such thing and I'm genuinely angry at you for suggesting it.
chrismmay 7y ago
We do support iOS 11. The client being on iOS 11 is an indication that the device has run our of storage space. Because it was out of storage, the files for our app were truncated because there was insufficient storage. A truncated file is there but it's corrupt. iOS doesn't detect this corruption, and the app is broken. Forever, and it can't be fixed without a factory reset, complete reinstall of the OS or somehow jailbreaking the device as far as I know. The customer reporting "stuck on a blank screen" and the User Agent being stuck on iOS 11, even when most people have automatic updates enabled are the primary indications that leads to this conclusion.
- skrebbel 7y ago
  Ah right! Thanks, now I get it. Wow that's nasty.

You've totally misunderstood the OP's story. Their app does not have any kind of dependency on iOS 13 and should work on iOS 11. It's just that there's a correlation between an iOS 11 UA and the app not working. The hypothesis is that there is something wrong with some devices that both a) caused them to not be upgraded, b) causes their app to fail. This kind of misreading is a prime example of just how toxic any discussions about version number detection are. Rather than give the OP any benefit of the doubt and maybe re-read what they wrote, you've just decided they must be incompetent or lazy and castigate them over it.

skrebbel 7y ago
Oh come on. I even began my sentence stating that I didn't understand. What more do you want? I was genuinely interested, there's no need to snark. The only thing that's toxic in this thread is your comment. If we're going to begin by assuming that things like "I don't understand" are meaningless hollow phrases that trolls tack on comments just to snark more effectively, then the end is that we simply can't communicate online anymore. Please don't push in that direction, it's not the solution. > you've just decided they must be incompetent or lazy and castigate them over it. I did no such thing and I'm genuinely angry at you for suggesting it.

chrismmay 7y ago

We do support iOS 11. The client being on iOS 11 is an indication that the device has run our of storage space. Because it was out of storage, the files for our app were truncated because there was insufficient storage. A truncated file is there but it's corrupt. iOS doesn't detect this corruption, and the app is broken. Forever, and it can't be fixed without a factory reset, complete reinstall of the OS or somehow jailbreaking the device as far as I know. The customer reporting "stuck on a blank screen" and the User Agent being stuck on iOS 11, even when most people have automatic updates enabled are the primary indications that leads to this conclusion.

skrebbel 7y ago
Ah right! Thanks, now I get it. Wow that's nasty.