Closed
Bug 720471
Opened 13 years ago
Closed 13 years ago
Missing Arrays and Editor methods in Android SDK <= 8
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P2)
Tracking
(firefox11 verified)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox11 | --- | verified |
People
(Reporter: rnewman, Assigned: liuche)
References
Details
Follow-on from Bug 717691.
Fatal exception during manual account creation, on SDK 8.
Android Sync crashes on 2.2.2 device, log attached. (See https://bugzilla.mozilla.org/attachment.cgi?id=588115)
SDK apparently does not contain some Arrays methods, or Editor.apply method.
Changing Android project build target to SDK 8 shows errors in project.
Reporter | ||
Comment 1•13 years ago
|
||
I think this is next in line for 2.2 compat…
Assignee: nobody → liuche
Priority: -- → P2
Comment 2•13 years ago
|
||
Raising importance.
This fails attempting to pair a 2,2 device to desktop
similar log to attached:
01-25 14:59:24.500: W/dalvikvm(666): threadid=9: thread exiting with uncaught exception (group=0x4001d7f0)
01-25 14:59:24.500: E/AndroidRuntime(666): FATAL EXCEPTION: Timer-0
01-25 14:59:24.500: E/AndroidRuntime(666): java.lang.NoSuchMethodError: java.util.Arrays.copyOf
01-25 14:59:24.500: E/AndroidRuntime(666): at org.mozilla.gecko.sync.Utils.concatAll(Utils.java:131)
Severity: normal → blocker
Reporter | ||
Comment 3•13 years ago
|
||
Reporter | ||
Comment 4•13 years ago
|
||
Pushed to inbound with next code drop.
(Note to inbound sheriff: we resolve our bugs when they land in android-sync, not when they merge to m-c. See the code drop bug in Bug 720933.)
Whiteboard: [inbound]
Comment 5•13 years ago
|
||
Richard please request aurora approval
Reporter | ||
Updated•13 years ago
|
status-firefox11:
--- → fixed
Whiteboard: [inbound]
Updated•12 years ago
|
Product: Mozilla Services → Android Background Services
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•