Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
it was found that
EXIF_TAGS
includesIFD_TIFF_TAGS
twice
This duplication has always been present in the AndroidX version of ExifInterface
. It looks like it was inherited from the platform version, where it was added in 2016 in
ru...@gmail.com <ru...@gmail.com> #3
The duplication of IFD_TIFF_TAGS
is also discussed in internal
su...@google.com <su...@google.com>
ru...@gmail.com <ru...@gmail.com> #4
Project: platform/frameworks/support
Branch: androidx-main
commit 77ac31b4e0d83f5cee16dc6c50da6f26a1f5a4d3
Author: Ian Baker <ibaker@google.com>
Date: Thu Mar 28 16:49:00 2024
Ensure XMP data isn't duplicated into Exif segment when saving
Test: ExifInterfaceTest
Bug: 309843390
Change-Id: I56b6defea9b5e800d426cb050b19bea03f614b15
M exifinterface/exifinterface/src/androidTest/java/androidx/exifinterface/media/ExifInterfaceTest.java
M exifinterface/exifinterface/src/main/java/androidx/exifinterface/media/ExifInterface.java
https://android-review.googlesource.com/3017513
Branch: androidx-main
commit 77ac31b4e0d83f5cee16dc6c50da6f26a1f5a4d3
Author: Ian Baker <ibaker@google.com>
Date: Thu Mar 28 16:49:00 2024
Ensure XMP data isn't duplicated into Exif segment when saving
Test: ExifInterfaceTest
Bug: 309843390
Change-Id: I56b6defea9b5e800d426cb050b19bea03f614b15
M exifinterface/exifinterface/src/androidTest/java/androidx/exifinterface/media/ExifInterfaceTest.java
M exifinterface/exifinterface/src/main/java/androidx/exifinterface/media/ExifInterface.java
su...@google.com <su...@google.com> #5
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.exifinterface:exifinterface:1.4.0-alpha01
Description
Version used: 1.0.0-beta03
Devices/Android versions reproduced on: couldn't reproduce
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.os.PowerManager$WakeLock.isHeld()' on a null object reference
at androidx.work.impl.utils.WakeLocks.checkWakeLocks(WakeLocks.java:89)
at androidx.work.impl.background.systemalarm.SystemAlarmService.onAllCommandsCompleted(SystemAlarmService.java:69)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.dequeueAndCheckForCompletion(SystemAlarmDispatcher.java:217)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$DequeueAndCheckForCompletion.run(SystemAlarmDispatcher.java:317)
at android.os.Handler.handleCallback(Handler.java:810)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:189)
at android.app.ActivityThread.main(ActivityThread.java:5529)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:950)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:745)
Seems like the copy of wake locks can contain null keys. I couldn't reproduce this, but some devices on crashlytics are reporting this crash.