4 ms·
Separately from the utter ridiculousness of this... ...can anyone guess what about their app might break in iOS 16? I was under the impression that iOS updates
by crazygringo 4y ago
Separately from the utter ridiculousness of this...
...can anyone guess what about their app might break in iOS 16? I was under the impression that iOS updates didn't generally break compatibility, unless it's locking down some kind of permission. But I'm having a hard time imagining what a banking app would rely on that would change underneath it?
- mathieulj 4y agoTouch ID/Face ID lockdown most likely.
- tcoff91 4y agoApple Pay is changing in subtle ways that can break payment flows.
- aeontech 4y agoCan you expand on this? From my understanding about Apple Pay, anything already working should continue to work, and any new features are optional… so I’m curious what you have in mind.
- tcoff91 4y agoIf you fail the payment request, the Apple Pay dialog remains on the screen and the user can change cards. Before, the payment flow would end and the app would then submit a new payment request to try again.
- deleted 4y ago[deleted]
- poink 4y agoThere is at least one expensive enterprise DRM/obfuscation/"code protection" tool that had a late breaking bug in the iOS 16 beta process, and any app that uses it works with with earlier iOS 16 beta builds while crashing on newer ones.
- dpkirchner 4y agoMaybe they're still using FTP (support removed in iOS 16).
- izacus 4y agoI worked on a iOS product and Apple breaks things across versions pretty constantly. A lot of them are undocumented (things like UI components just not rendering correctly or breaking) and it requires a pretty big sprint every year when betas arrive (which is a pain because you don't know which of the bugs will be fixed by release). Android isn't much different.
- Shorn 4y agoUpvoted for being the first comment with the content I come to HN for.