The default bug view has changed. See this FAQ.

Deprecate support for iOS 8

RESOLVED FIXED

Status

()

Firefox for iOS
General
P1
normal
Rank:
2
RESOLVED FIXED
7 months ago
5 months ago

People

(Reporter: aaronmt, Assigned: bnicholson)

Tracking

unspecified
Other
iOS

Firefox Tracking Flags

(fxios6.0+, fxios-v6.0 fixed)

Details

(Whiteboard: [MobileAS])

Attachments

(1 attachment)

Comment hidden (empty)
(Assignee)

Comment 1

7 months ago
With iOS 10 around the corner, this is a good time to finally drop 8 support.
tracking-fxios: ? → 6.0+

Updated

6 months ago
Priority: -- → P3

Updated

6 months ago
Whiteboard: [MobileAS]
Rank: 2
(Assignee)

Comment 2

6 months ago
Not requiring these #available checks for iOS 9 will make life easier for bug 1304456, and we'll have to eventually do this anyway, so let's go ahead and knock this one out now.
Assignee: nobody → bnicholson
Status: NEW → ASSIGNED
Priority: P3 → P1
(Assignee)

Comment 3

6 months ago
Created attachment 8793503 [details] [review]
Link to Github pull-request: https://github.com/mozilla/firefox-ios/pull/2111
Attachment #8793503 - Flags: review?(sleroux)
Comment on attachment 8793503 [details] [review]
Link to Github pull-request: https://github.com/mozilla/firefox-ios/pull/2111

Awesome. Thanks for fixing the keychain stuff I missed in the test targets.
Attachment #8793503 - Flags: review?(sleroux) → review+
(Assignee)

Comment 5

6 months ago
https://github.com/mozilla/firefox-ios/commit/a2467d72e0ffd01688311ddceec1e919fea7e68a
Status: ASSIGNED → RESOLVED
Last Resolved: 6 months ago
status-fxios-v6.0: --- → fixed
Resolution: --- → FIXED

Comment 6

6 months ago
Hi Brian,

Was there any burden, code-wise, or any compromises we had to make, that we dropped support for iOS 8? I thought it was only the 'if #available' checks that were extra.

Just curious, since I'm on iPhone 4s/iOS 8 and don't want to move to iOS 9 as it might slow it down.
Flags: needinfo?(bnicholson)
(Assignee)

Comment 7

6 months ago
Hi Maurya,

There's a growing number of features and APIs with each iOS release, so maintaining support for older releases becomes a huge maintenance burden.

Examples from iOS 9:
* Private browsing
* Clearing private data
* New XCTest APIs

This list will grow longer with iOS 10.

Code-wise, we worked around many of these using 'if #available' checks as you said, but maintaining support for 8 means we also need to test and run iOS 8 builds often to make sure they're stable. We were already neglecting iOS 8 before; we just don't have the resources to maintain 8, 9, *and* 10 now.
Flags: needinfo?(bnicholson)

Comment 8

6 months ago
Hmm, yeah that sounds reasonable. Thanks for your reply!

Updated

5 months ago
Iteration: --- → 1.5
You need to log in before you can comment on or make changes to this bug.