Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Information redacted by Android Beta Feedback.
[Deleted User] <[Deleted User]> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Screen record of the issue, for clarity Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4
Note: Please upload the files to google drive and share the folder to
al...@gmail.com <al...@gmail.com> #4
- Build Number: google/cheetah_beta/cheetah:UpsideDownCake/UPB2.230407.014/10064957:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This issue occurred when I plugged in my phone to charge it and it had fully charged. I plugged in my phone when it was at roughly 13% battery life and it said on the desk next to me charging. When battery percentage got you 100%, an error appeared in my notifications that said that the phone was either not charging or charging very slowly, it seemed to indicate a possible issue with the charger or the battery. This only started when I updated my phone recently. It seems to be that the error notification May not be ignoring the slow charge and or lack of charge when the battery has hit 100%..
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This issue occurred when I plugged in my phone to charge it and it had fully charged. I plugged in my phone when it was at roughly 13% battery life and it said on the desk next to me charging. When battery percentage got you 100%, an error appeared in my notifications that said that the phone was either not charging or charging very slowly, it seemed to indicate a possible issue with the charger or the battery. This only started when I updated my phone recently. It seems to be that the error notification May not be ignoring the slow charge and or lack of charge when the battery has hit 100%..
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
jh...@themeetgroup.com <jh...@themeetgroup.com> #5
- Build Number: google/cheetah_beta/cheetah:UpsideDownCake/UPB2.230407.014/10064957:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
I let my phone charge to 100% again and it's doing it every time now. Here is the screenshot of the notification which popped up as soon as it hit 100%.
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
I let my phone charge to 100% again and it's doing it every time now. Here is the screenshot of the notification which popped up as soon as it hit 100%.
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
ag...@gmail.com <ag...@gmail.com> #6
Information redacted by Android Beta Feedback.
[Deleted User] <[Deleted User]> #7
only some libraries are obfuscated for method reduction, currently only way to solve this is to reduce our methods to less than 65k+
[Deleted User] <[Deleted User]> #8
There is something wrong in art runtime when the device is samsung g900f.
almost all custom view crashed by ClassCastException exception when I use findviewbyid method.
almost all custom view crashed by ClassCastException exception when I use findviewbyid method.
[Deleted User] <[Deleted User]> #9
[Comment deleted]
bo...@gmail.com <bo...@gmail.com> #10
I am having the same issue with crashes on S5 5.0 devices in Europe. We tested a single dex build and it does not crash. Any multidex build crashes with multiple ClassCastExceptions.
ad...@gmail.com <ad...@gmail.com> #11
It appears the latest OS updates to the GS5 has a bug in it's multidex handling. They have stopped the roll out of the update. So it looks like we are waiting for Samsung to roll out a new OS update with it fixed.
Or find a way to not use multi-dex in your app.
Or find a way to not use multi-dex in your app.
gu...@gmail.com <gu...@gmail.com> #12
It seems u1boc7 firmware version solved the problem
[Deleted User] <[Deleted User]> #13
Any way to solve it???
[Deleted User] <[Deleted User]> #14
create a jar out of your libraries, create an interface project that will glue the main project with the libraries, load the jar as a dex in runtime
[Deleted User] <[Deleted User]> #15
@a.jaskev, can you give more details. What is your work around doing ?
sp...@gmail.com <sp...@gmail.com> #16
this turned out to be the only working solution that i've found. I'm also doing dynamic classloading across APKs and ran into the same issue when casting or fetching a annotation that wasn't from the parent classloader. The above solution works for annotations that have their own fields.
[Deleted User] <[Deleted User]> #17
@spyhunter, this code needs an annotation instance, but the bug appears when creating an annotation instance... This work around can't solve the current issue.
jo...@google.com <jo...@google.com> #18
Thanks for the feedback and sorry for the delay. We believe this has been fixed in later versions. Please reopen if you see this behavior again. Thanks.
Description
Problem running multidex apk with annotations, the app crashes with the following exception:
java.lang.AssertionError: annotation value type != return type
at libcore.reflect.AnnotationAccess.toAnnotationInstance(AnnotationAccess.java:649)
at libcore.reflect.AnnotationAccess.toAnnotationInstance(AnnotationAccess.java:641)
at libcore.reflect.AnnotationAccess.getDeclaredAnnotation(AnnotationAccess.java:170)
at libcore.reflect.AnnotationAccess.getAnnotation(AnnotationAccess.java:72)
at java.lang.Class.getAnnotation(Class.java:343)
at org.codehaus.jackson.map.introspect.JacksonAnnotationIntrospector.isHandled(JacksonAnnotationIntrospector.java:45)
at org.codehaus.jackson.map.introspect.AnnotatedClass._collectRelevantAnnotations(AnnotatedClass.java:857)
at org.codehaus.jackson.map.introspect.AnnotatedClass._constructMethod(AnnotatedClass.java:773)
at org.codehaus.jackson.map.introspect.AnnotatedClass._addMemberMethods(AnnotatedClass.java:626)
at org.codehaus.jackson.map.introspect.AnnotatedClass.resolveMemberMethods(AnnotatedClass.java:408)
at org.codehaus.jackson.map.introspect.BasicClassIntrospector.classWithCreators(BasicClassIntrospector.java:185)
at org.codehaus.jackson.map.introspect.BasicClassIntrospector.collectProperties(BasicClassIntrospector.java:157)
at org.codehaus.jackson.map.introspect.BasicClassIntrospector.forDeserialization(BasicClassIntrospector.java:108)
at org.codehaus.jackson.map.introspect.BasicClassIntrospector.forDeserialization(BasicClassIntrospector.java:16)
at org.codehaus.jackson.map.DeserializationConfig.introspect(DeserializationConfig.java:868)
at org.codehaus.jackson.map.deser.BeanDeserializerFactory.createBeanDeserializer(BeanDeserializerFactory.java:587)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:401)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
at org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
at org.codehaus.jackson.map.deser.std.StdDeserializer.findDeserializer(StdDeserializer.java:620)
at org.codehaus.jackson.map.deser.BeanDeserializer.resolve(BeanDeserializer.java:379)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._resolveDeserializer(StdDeserializerProvider.java:407)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:352)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
at org.codehaus.jackson.map.deser.BasicDeserializerFactory.createCollectionDeserializer(BasicDeserializerFactory.java:284)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createDeserializer(StdDeserializerProvider.java:389)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:310)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
at org.codehaus.jackson.map.deser.std.StdDeserializer.findDeserializer(StdDeserializer.java:620)
at org.codehaus.jackson.map.deser.BeanDeserializer.resolve(BeanDeserializer.java:379)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._resolveDeserializer(StdDeserializerProvider.java:407)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCache2(StdDeserializerProvider.java:352)
at org.codehaus.jackson.map.deser.StdDeserializerProvider._createAndCacheValueDeserializer(StdDeserializerProvider.java:290)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findValueDeserializer(StdDeserializerProvider.java:159)
at org.codehaus.jackson.map.deser.StdDeserializerProvider.findTypedValueDeserializer(StdDeserializerProvider.java:180)
at org.codehaus.jackson.map.ObjectMapper._findRootDeserializer(ObjectMapper.java:2829)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2728)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)
The following commit is the problem :
Neil Fuller 2014-03-26 16:59:44 +0000 08da684 [diff] [blame] 352. if (reader.getAnnotationType() != annotationClass.getDexTypeIndex()) {
Tested on Samsung s5 with the latest lollipop installed, this is a remote users device.
I am not an expert, but seems that multidex support breaks the annotation type and dex type index checking logic.
the following features are enabled in gradle:
multiDexEnabled true
dexOptions {
javaMaxHeapSize "4g"
jumboMode true
preDexLibraries true
incremental true
}
No code obfuscation is used.