Fixed
Status Update
No update yet.
Comments
dn...@google.com
dn...@google.com
Thank you for reporting this issue. Can you provide the below requested information to better understand the issue:
Steps to reproduce
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Steps to reproduce
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
to...@gmail.com
Thanks for the automated answer but as I said I can't reproduce this issue.
Issue that touch 0,1% of the sessions of Android 4.x users.
So well I can't provide anything asked as the crash logs does not explains why in 0,1% of the cases it does not take the correct path inside your code.
The crash logs provided does show that it happens whatever way is chosen to set the image.
1) Inflate a layout XML that contains an AppCompatButton with app:srcCompat= a vector drawable.
2) Setting an AppcompatImageView drawable with setImageDrawable(AppCompatResources.getDrawable(itemHolder.thumbnail.getContext(), R.drawable.ic_insert_drive_file_white_transparent_24dp))
3) Setting an AppcompatImageView resource with setImageResource(R.drawable.ic_repeat_white_24dp);
AppCompatDelegate.setCompatVectorFromResourcesEnabled(true); is activated as static in Application + in on application Create + in OnCreate of all activities in case it was some race condition that did not set the flag early enough.
vectorDrawables.useSupportLibrary = true is set in gradle too.
The issue is tied to
at android.support.v7.widget.VectorEnabledTintResources.superGetDrawable(VectorEnabledTintResources.java:2074)
at android.support.v4.content.ContextCompat.getDrawable(ContextCompat.java:360)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
It should not call superGetDrawable. So something happens before, either the flag is wrongly read, or you have previously cached an error that was not an error or there was another error during first caching of that drawable but we have no way to know.
Since I suppose this will get closed as some others case I've seen about that, maybe next support libraries versions could at least try to have a better crash message
Changing : "Fatal Exception: android.content.res.Resources$NotFoundException: File res/drawable/ic_insert_drive_file_white_transparent_24dp.xml from drawable resource ID #0x7f020147. If the resource you are trying to use is a vector resource, you may be referencing it in an unsupported way. See AppCompatDelegate.setCompatVectorFromResourcesEnabled() for more info."
So that it includes the seen value of isCompatVectorFromResourcesEnabled() + If that drawable was in your error cache so we can try to narrow the issue down further.
Or if you suspect it was an error during delegate load, maybe crash at that step if the drawable is a vector drawable and API < 21 as in all cases it will crash later.
Issue that touch 0,1% of the sessions of Android 4.x users.
So well I can't provide anything asked as the crash logs does not explains why in 0,1% of the cases it does not take the correct path inside your code.
The crash logs provided does show that it happens whatever way is chosen to set the image.
1) Inflate a layout XML that contains an AppCompatButton with app:srcCompat= a vector drawable.
2) Setting an AppcompatImageView drawable with setImageDrawable(AppCompatResources.getDrawable(itemHolder.thumbnail.getContext(), R.drawable.ic_insert_drive_file_white_transparent_24dp))
3) Setting an AppcompatImageView resource with setImageResource(R.drawable.ic_repeat_white_24dp);
AppCompatDelegate.setCompatVectorFromResourcesEnabled(true); is activated as static in Application + in on application Create + in OnCreate of all activities in case it was some race condition that did not set the flag early enough.
vectorDrawables.useSupportLibrary = true is set in gradle too.
The issue is tied to
at android.support.v7.widget.VectorEnabledTintResources.superGetDrawable(VectorEnabledTintResources.java:2074)
at android.support.v4.content.ContextCompat.getDrawable(ContextCompat.java:360)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
It should not call superGetDrawable. So something happens before, either the flag is wrongly read, or you have previously cached an error that was not an error or there was another error during first caching of that drawable but we have no way to know.
Since I suppose this will get closed as some others case I've seen about that, maybe next support libraries versions could at least try to have a better crash message
Changing : "Fatal Exception: android.content.res.Resources$NotFoundException: File res/drawable/ic_insert_drive_file_white_transparent_24dp.xml from drawable resource ID #0x7f020147. If the resource you are trying to use is a vector resource, you may be referencing it in an unsupported way. See AppCompatDelegate.setCompatVectorFromResourcesEnabled() for more info."
So that it includes the seen value of isCompatVectorFromResourcesEnabled() + If that drawable was in your error cache so we can try to narrow the issue down further.
Or if you suspect it was an error during delegate load, maybe crash at that step if the drawable is a vector drawable and API < 21 as in all cases it will crash later.
dn...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
to...@gmail.com
Any news about this? This is the main crash source and totally out of my control :(
to...@gmail.com
Time for monthly enquiry about the source of 75% of my crashes :)
sg...@google.com
Did these crashes start started happening with changing from dx to D8, or have they been there for longer?
Also, do you have information on which versions/vendors of 4.x this happens on? The stack traces indicate different version of the Android Platform.
Also, do you have information on which versions/vendors of 4.x this happens on? The stack traces indicate different version of the Android Platform.
to...@gmail.com
They started before :( I was hoping D8/AAPT2 would fix it but no. It's a long lasting bug, but I know that non reproductible issues are quite hard to advance :(
Seems unrelated to Device and OS version. I'm API 16+ and Crashlytics says for one of the issues :
OS:
4.4.2 48%
4.2.2 19%
4.4.4 19%
4.1.2 8%
4.3 5%
4.2.1 1%
Devices:
samsung 47%
asus 9%
LENOVO 9%
Xiaomi 4%
other 31%
other ->
Xiaomi 72%
Acer 1%
HTC 1%
Lenovo 1%
LGE 1%
motorola 1%
Asus 1%
Motorola 1%
WonderMedia 1%
Sony 1%
Foxconn International Holdings Limited 1%
NavRoad 1%
TCL 1%
MODECOM 1%
BullittGroupLimited 1%
intel 1%
Hewlett-Packard 1%
WIKO 1%
Cynus 1%
THL 1%
bq 1%
JTY 1%
Cyrus CS19 1%
HUAWEI 1%
amzn 1%
Orange 1%
Enspert 1%
alps 1%
Dell 1%
Those crashes have touched like 200/300 users and according to Play Console dashboard I still have about 80 000 active Android 4 users so it's rare but annoying as prevent perfect crash free sessions report :)
But from watching the crashs again it seems one of the D8 bug I thought was fixed with the last patch fromhttps://issuetracker.google.com/issues/73787793 is still present will open another issue for it. (Along with https://issuetracker.google.com/issues/77672662 that I'll ping again after IO :))
Seems unrelated to Device and OS version. I'm API 16+ and Crashlytics says for one of the issues :
OS:
4.4.2 48%
4.2.2 19%
4.4.4 19%
4.1.2 8%
4.3 5%
4.2.1 1%
Devices:
samsung 47%
asus 9%
LENOVO 9%
Xiaomi 4%
other 31%
other ->
Xiaomi 72%
Acer 1%
HTC 1%
Lenovo 1%
LGE 1%
motorola 1%
Asus 1%
Motorola 1%
WonderMedia 1%
Sony 1%
Foxconn International Holdings Limited 1%
NavRoad 1%
TCL 1%
MODECOM 1%
BullittGroupLimited 1%
intel 1%
Hewlett-Packard 1%
WIKO 1%
Cynus 1%
THL 1%
bq 1%
JTY 1%
Cyrus CS19 1%
HUAWEI 1%
amzn 1%
Orange 1%
Enspert 1%
alps 1%
Dell 1%
Those crashes have touched like 200/300 users and according to Play Console dashboard I still have about 80 000 active Android 4 users so it's rare but annoying as prevent perfect crash free sessions report :)
But from watching the crashs again it seems one of the D8 bug I thought was fixed with the last patch from
he...@worldiety.de
May be this is related to https://issuetracker.google.com/issues/79172317
This is just a vague guess so I opened a separate ticket.
This is just a vague guess so I opened a separate ticket.
to...@gmail.com
You too face ku...@google.com automated answers ;)
https://issuetracker.google.com/issues/78678417
BTW I've added another side effect of the race condition that can happens on your ticket.
BTW I've added another side effect of the race condition that can happens on your ticket.
ti...@google.com
This is likely related to race condition due to https://b.corp.google.com/issues/79172317 , especially given how difficult it is to reproduce.
Tolriq, until the thread safety with AppCompatDrawableManager is resolved, could you check in your code base and restrict access to AppCompatDrawableManager from the background thread?
Tolriq, until the thread safety with AppCompatDrawableManager is resolved, could you check in your code base and restrict access to AppCompatDrawableManager from the background thread?
to...@gmail.com
Well I've tripled checked my code and the non main thread access to those are Android Auto loader that can't be on main thread for performance reasons, RemoteViewsService.RemoteViewsFactory for stacked widget that will also be quite hard to move to main thread without performance hits, and generation of other widgets that could be moved to main thread but without moving the 2 other would slow things without addressing all cases :(
The other image manipulations are notifications builder addAction but I do use PNGs for those and I don't really know at what time / which thread notification does inflate the images.
The other image manipulations are notifications builder addAction but I do use PNGs for those and I don't really know at what time / which thread notification does inflate the images.
to...@gmail.com
Related to the race condition https://issuetracker.google.com/issues/79172317 but posting here since it happens after your asked to remove all background access.
Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=29; index=29
at android.support.v4.util.SparseArrayCompat.append(SparseArrayCompat.java:325)
at android.support.v7.widget.AppCompatDrawableManager.loadDrawableFromDelegates(AppCompatDrawableManager.java:381)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:193)
at android.support.v7.content.res.AppCompatResources.android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatResources.java:1186)
at android.support.v7.view.menu.MenuItemImpl.getIcon(MenuItemImpl.java:491)
at android.support.v7.view.menu.ActionMenuItemView.initialize$667f453d(ActionMenuItemView.java:125)
at android.support.v7.widget.ActionMenuPresenter.bindItemView(ActionMenuPresenter.java:210)
at android.support.v7.view.menu.BaseMenuPresenter.getItemView(BaseMenuPresenter.java:187)
at android.support.v7.widget.ActionMenuPresenter.getItemView(ActionMenuPresenter.java:196)
at android.support.v7.widget.ActionMenuPresenter.flagActionItems(ActionMenuPresenter.java:476)
at android.support.v7.view.menu.MenuBuilder.flagActionItems(MenuBuilder.java:1164)
at android.support.v7.view.menu.BaseMenuPresenter.updateMenuView(BaseMenuPresenter.java:95)
at android.support.v7.widget.ActionMenuPresenter.updateMenuView(ActionMenuPresenter.java:229)
at android.support.v7.view.menu.MenuBuilder.dispatchPresenterUpdate(MenuBuilder.java:8291)
at android.support.v7.view.menu.MenuBuilder.startDispatchingItemsChanged(MenuBuilder.java:1078)
at android.support.v7.app.ToolbarActionBar$1.android.support.v7.app.ToolbarActionBar.populateOptionsMenu(ToolbarActionBar.java:1460)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5525)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:730)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:620)
This one is from a special beta build that did not include from my code background access to AppCompatDrawableManager (missing functions but was serving as a test).
This crash is much more rare than the Android 4 bug and occurs on Android 5/6 and limited devices likes Huawey and oppo.
Posting is case it helps about the thread safety issue.
Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=29; index=29
at android.support.v4.util.SparseArrayCompat.append(SparseArrayCompat.java:325)
at android.support.v7.widget.AppCompatDrawableManager.loadDrawableFromDelegates(AppCompatDrawableManager.java:381)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:193)
at android.support.v7.content.res.AppCompatResources.android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatResources.java:1186)
at android.support.v7.view.menu.MenuItemImpl.getIcon(MenuItemImpl.java:491)
at android.support.v7.view.menu.ActionMenuItemView.initialize$667f453d(ActionMenuItemView.java:125)
at android.support.v7.widget.ActionMenuPresenter.bindItemView(ActionMenuPresenter.java:210)
at android.support.v7.view.menu.BaseMenuPresenter.getItemView(BaseMenuPresenter.java:187)
at android.support.v7.widget.ActionMenuPresenter.getItemView(ActionMenuPresenter.java:196)
at android.support.v7.widget.ActionMenuPresenter.flagActionItems(ActionMenuPresenter.java:476)
at android.support.v7.view.menu.MenuBuilder.flagActionItems(MenuBuilder.java:1164)
at android.support.v7.view.menu.BaseMenuPresenter.updateMenuView(BaseMenuPresenter.java:95)
at android.support.v7.widget.ActionMenuPresenter.updateMenuView(ActionMenuPresenter.java:229)
at android.support.v7.view.menu.MenuBuilder.dispatchPresenterUpdate(MenuBuilder.java:8291)
at android.support.v7.view.menu.MenuBuilder.startDispatchingItemsChanged(MenuBuilder.java:1078)
at android.support.v7.app.ToolbarActionBar$1.android.support.v7.app.ToolbarActionBar.populateOptionsMenu(ToolbarActionBar.java:1460)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5525)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:730)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:620)
This one is from a special beta build that did not include from my code background access to AppCompatDrawableManager (missing functions but was serving as a test).
This crash is much more rare than the Android 4 bug and occurs on Android 5/6 and limited devices likes Huawey and oppo.
Posting is case it helps about the thread safety issue.
to...@gmail.com
Ok so I've released a new build with Widgets moved to main thread only for Android 4.x and can confirm that those crashes have vastly reduced and suppose the remains are due to the stacked widgets / Android Auto that I can't move to main thread without way too big refactoring to address such rare issue.
The crash reported in #13 is obviously still present since I did not change the threads for Android 5+ if it's related to that.
But I've taken time to check all the reports so far about #13 and what is strange is that the index are always the same 29 or 61. Since the list of devices for this one is smaller maybe it's some Vector Drawable that is incompatible with those devices.
Do you have any idea how I can try to figure out more ?
The crash reported in #13 is obviously still present since I did not change the threads for Android 5+ if it's related to that.
But I've taken time to check all the reports so far about #13 and what is strange is that the index are always the same 29 or 61. Since the list of devices for this one is smaller maybe it's some Vector Drawable that is incompatible with those devices.
Do you have any idea how I can try to figure out more ?
he...@worldiety.de
Why don't you just synchronize that 2 or 3 critical lines in AppCompatDrawableManager? I know that multithreaded usage is not officially supported, but this drawable-stuff is not directly related to the UI. There are cases where one has to prepare bitmaps by drawing to a canvas in a background thread which definately should not be done on the main-thread. My feeling was, that, as long as you do not access live views that are attached to the window there should be no problem about it.
Why should resource-access be limited to the main-thread?
Why should resource-access be limited to the main-thread?
to...@gmail.com
I hope they'll fix that soon :)
Because moving widgets to main thread now creates rare ANRs ;)
at android.content.res.AssetManager.openXmlAssetNative (Native Method)
at android.content.res.AssetManager.openXmlBlockAsset (AssetManager.java:521)
at android.content.res.Resources.loadXmlResourceParser (Resources.java:2195)
at android.content.res.Resources.loadXmlResourceParser (Resources.java:2168)
at android.content.res.Resources.getXml (Resources.java:902)
at android.support.v7.widget.k.a (AppCompatDrawableManager.java:345)
at android.support.v7.widget.k.a (AppCompatDrawableManager.java:193)
at android.support.v7.c.a.b.b (AppCompatResources.java:1186)
at org.leetzone.android.yatsewidget.helpers.g.a (DisplayHelper.java:444)
at org.leetzone.android.yatsewidget.i.b.a (YatseWidgetHelper.kt:169)
Not sure what's better, crash or ANRs :)
Because moving widgets to main thread now creates rare ANRs ;)
at android.content.res.AssetManager.openXmlAssetNative (Native Method)
at android.content.res.AssetManager.openXmlBlockAsset (AssetManager.java:521)
at android.content.res.Resources.loadXmlResourceParser (Resources.java:2195)
at android.content.res.Resources.loadXmlResourceParser (Resources.java:2168)
at android.content.res.Resources.getXml (Resources.java:902)
at android.support.v7.widget.k.a (AppCompatDrawableManager.java:345)
at android.support.v7.widget.k.a (AppCompatDrawableManager.java:193)
at android.support.v7.c.a.b.b (AppCompatResources.java:1186)
at org.leetzone.android.yatsewidget.helpers.g.a (DisplayHelper.java:444)
at org.leetzone.android.yatsewidget.i.b.a (YatseWidgetHelper.kt:169)
Not sure what's better, crash or ANRs :)
dn...@google.com
The development team has fixed the issue that you have reported and it will be available in a future build.
Description
Version used: Latest 27.0.2 (and previous versions as well)
Theme used: All app compat
Devices/Android versions reproduced on: API 16 -> 20
I have an application in production with everything configured correctly for vector drawables. Everything works perfectly for Android 4.x at 99,9% of the time.
But sometimes there's crashes with some examples provided bellow.
I have not found a way to reproduce but would like to solve them if possible.
Stack trace correctly shows that all goes via support and vector drawable enable code. And that it correctly load the xml since it see the vector tag.
------
Caused by org.xmlpull.v1.XmlPullParserException: Binary XML file line #2: invalid drawable tag vector
at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:986)
at android.graphics.drawable.Drawable.createFromXml(Drawable.java:930)
at android.content.res.Resources.loadDrawable(Resources.java:3436)
at android.content.res.Resources.getDrawable(Resources.java:1917)
at android.support.v7.widget.VectorEnabledTintResources.superGetDrawable(VectorEnabledTintResources.java:2074)
at android.support.v4.content.ContextCompat.getDrawable(ContextCompat.java:360)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
at android.support.v7.content.res.AppCompatResources.android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatResources.java:1186)
at android.support.v7.widget.AppCompatImageHelper.loadFromAttributes(AppCompatImageHelper.java:58)
at android.support.v7.widget.AppCompatImageButton.(AppCompatImageButton.java:78)
at android.support.v7.widget.AppCompatImageButton.(AppCompatImageButton.java:68)
at org.leetzone.android.yatsewidget.ui.view.OverlayImageButton.(OverlayImageButton.kt:16)
at org.leetzone.android.yatsewidget.ui.view.AutoRepeatButton.(AutoRepeatButton.kt:28)
at java.lang.reflect.Constructor.constructNative(Constructor.java)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at android.view.LayoutInflater.createView(LayoutInflater.java:600)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:702)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:761)
at android.view.LayoutInflater.inflate(LayoutInflater.java:498)
at android.view.LayoutInflater.inflate(LayoutInflater.java:398)
at org.leetzone.android.yatsewidget.ui.fragment.DrawerRemoteFragment.onViewCreated(DrawerRemoteFragment.kt:169)
at android.support.v4.app.Fragment.performCreateView(Fragment.java:2261)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1419)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1750)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1819)
at android.support.v4.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3227)
at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:3191)
at android.support.v4.app.FragmentActivity.android.support.v4.app.FragmentController.dispatchResume(FragmentActivity.java:11214)
at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:471)
at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:171)
at android.app.Activity.performResume(Activity.java:5543)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3066)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3105)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
at android.app.ActivityThread.access$900(ActivityThread.java:175)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1308)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:146)
at android.app.ActivityThread.main(ActivityThread.java:5602)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1283)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
at dalvik.system.NativeStart.main(NativeStart.java)
------
-----
Caused by org.xmlpull.v1.XmlPullParserException: Binary XML file line #2: invalid drawable tag vector
at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:969)
at android.graphics.drawable.Drawable.createFromXml(Drawable.java:913)
at android.content.res.Resources.loadDrawable(Resources.java:3006)
at android.content.res.Resources.getDrawable(Resources.java:1586)
at android.support.v7.widget.VectorEnabledTintResources.superGetDrawable(VectorEnabledTintResources.java:2074)
at android.support.v4.content.ContextCompat.getDrawable(ContextCompat.java:360)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
at android.support.v7.content.res.AppCompatResources.android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatResources.java:1186)
at org.leetzone.android.yatsewidget.array.adapter.PlaylistRecyclerAdapter.onBindViewHolder(PlaylistRecyclerAdapter.java:96)
at android.support.v7.widget.RecyclerView$Adapter.onCreateViewHolder(RecyclerView.java:6508)
at com.h6ah4i.android.widget.advrecyclerview.adapter.SimpleWrapperAdapter.onBindViewHolder(SimpleWrapperAdapter.java:229)
at com.h6ah4i.android.widget.advrecyclerview.draggable.DraggableItemWrapperAdapter.onBindViewHolder(DraggableItemWrapperAdapter.java:116)
at android.support.v7.widget.RecyclerView$Recycler.android.support.v7.widget.RecyclerView$Adapter.bindViewHolder(RecyclerView.java:24541)
at android.support.v7.widget.RecyclerView$Recycler.getViewForPosition(RecyclerView.java:13589)
at android.support.v7.widget.LinearLayoutManager$LayoutState.next(LinearLayoutManager.java:2231)
at android.support.v7.widget.LinearLayoutManager.layoutChunk(LinearLayoutManager.java:1558)
at android.support.v7.widget.LinearLayoutManager.fill(LinearLayoutManager.java:1518)
at android.support.v7.widget.LinearLayoutManager.scrollBy(LinearLayoutManager.java:1332)
at android.support.v7.widget.LinearLayoutManager.scrollVerticallyBy(LinearLayoutManager.java:1076)
at android.support.v7.widget.RecyclerView$ViewFlinger.run(RecyclerView.java:4864)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:803)
at android.view.Choreographer.doCallbacks(Choreographer.java:603)
at android.view.Choreographer.doFrame(Choreographer.java:572)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:789)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:157)
at android.app.ActivityThread.main(ActivityThread.java:5356)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)
at dalvik.system.NativeStart.main(NativeStart.java)
----
----
Caused by org.xmlpull.v1.XmlPullParserException: Binary XML file line #2: invalid drawable tag vector
at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:881)
at android.graphics.drawable.Drawable.createFromXml(Drawable.java:822)
at android.content.res.Resources.loadDrawable(Resources.java:1990)
at android.content.res.Resources.getDrawable(Resources.java:673)
at android.support.v7.widget.VectorEnabledTintResources.superGetDrawable(VectorEnabledTintResources.java:2074)
at android.support.v4.content.ContextCompat.getDrawable(ContextCompat.java:360)
at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
at android.support.v7.content.res.AppCompatResources.android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatResources.java:1186)
at android.support.v7.widget.AppCompatImageHelper.setImageResource(AppCompatImageHelper.java:85)
at android.support.v7.widget.AppCompatImageView.setImageResource(AppCompatImageView.java:93)
at org.leetzone.android.yatsewidget.ui.fragment.SlidingNowPlayingFragment.onClientDataEvent(SlidingNowPlayingFragment.java:1030)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.squareup.otto.Bus.com.squareup.otto.EventHandler.handleEvent(Bus.java:5089)
at com.squareup.otto.Bus.dispatchQueuedEvents(Bus.java:368)
at
at
at org.leetzone.android.yatsewidget.bus.MainThreadBus$post$1.run(MainThreadBus.kt:17)
at android.os.Handler.handleCallback(Handler.java:800)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:194)
at android.app.ActivityThread.main(ActivityThread.java:5391)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:833)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
at dalvik.system.NativeStart.main(NativeStart.java)
----