GeckoView: Target Android API 33 (Android 13)
Categories
(GeckoView :: General, task, P1)
Tracking
(firefox100 wontfix, firefox101 wontfix, firefox102 wontfix, firefox103 wontfix, firefox104 wontfix, firefox105 wontfix, firefox106 wontfix, firefox107 wontfix, firefox108 fixed)
People
(Reporter: agi, Assigned: olivia)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Whiteboard: [geckoview:2022h2] [geckoview:m107] [geckoview:m108], [wptsync upstream])
Attachments
(1 file)
When released we should switch to targeting Android 13.
Comment 1•2 years ago
|
||
Consider for Q4. The Android 13 release date is expected to be September or October 2022.
Comment 2•2 years ago
|
||
Kevin says we can wait until 2023 Q1 to target the new API.
- Fenix SDK issue: https://mozilla-hub.atlassian.net/browse/FNXV2-20845
- AC SDK issue: https://mozilla-hub.atlassian.net/browse/FNXV2-20790
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Decision: let's skip API 32 and jump to API 33.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
This bug covers updating GV, A-C, Fenix, Focus, and R-B to target API 33.
We need to fix AD_ID bug 1771343 before we target Android 13. We won't be able to ship app updates that target Android 13 without this manifest change!
107
Comment 6•2 years ago
|
||
Assigning to Olivia for 108. We need to fix all the other Android 13 bugs before we fix this bug!
Fixing this bug includes fixing A-C https://mozilla-hub.atlassian.net/browse/FNXV2-20790 and Fenix https://mozilla-hub.atlassian.net/browse/FNXV2-20845.
Comment 7•2 years ago
|
||
Dropping this bug's priority to P2 because we want to fix the other Android 13 bugs first.
Assignee | ||
Comment 8•2 years ago
|
||
Updating from Android API level 31 to API 33 for target and compile.
Assignee | ||
Comment 9•2 years ago
|
||
Need to coordinate with other Android 13 bugs before ready to land, but patch is ready for review.
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 10•2 years ago
|
||
When testing the patch to move GecoView to SDK 33, I saw issues related to bug 1797617 on a SDK 33 device. I'm treating bug 1797617 as non-blocking because it exists presently at SDK 31 (without the SDK 33 changes). Resolving bug 1797617 will become important for adding a higher device SDK emulator to CI.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Comment 13•2 years ago
|
||
bugherder |
Description
•