You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may be confused that some classes( For example, WebpResourceDecoder) are not in your project.
In fact, our project integrates your project and GlideWebpSupport (https://github.com/roths/GlideWebpSupport) in a sourcecode-dependent way. We replaced the WebpDecoder and WebpFrameLoader classes in your project with the same-named classes in the GlideWebpSupport project (because we found some problems with the GlideWebpSupport project).
My question is what would be the risk of this error if not handled, because we have not found any abnormality in the loading of dynamic webp.
Due to the lack of familiarity with fresco and c++ mechanisms, I would like to ask if it is necessary to deal with this error, because we only use fresco to load dynamic webp.
Many thanks.
The text was updated successfully, but these errors were encountered:
at com.facebook.soloader.SoLoader.init(SoLoader.java:104)
at com.xxx.xxx.impl.webp.WebpResourceDecoder.<init>(WebpResourceDecoder.java:54)
GlideWebpDecoder do not use WebpResourceDecoder and Soloader library, It seems like Soloader call an API that has been removed in Android P.
see facebook/SoLoader@4995a4b#diff-af2278b3b6db94229f8e96a1f3862dbd, comment: the third argument of nativeLoad method was removed in Android P API.
You should update the soloader library version to avoid the risk, thanks.
Hello developers:
On Android 9.0 I found some exception information when app started, the stack is as follows:
You may be confused that some classes( For example, WebpResourceDecoder) are not in your project.
In fact, our project integrates your project and GlideWebpSupport (https://github.com/roths/GlideWebpSupport) in a sourcecode-dependent way. We replaced the WebpDecoder and WebpFrameLoader classes in your project with the same-named classes in the GlideWebpSupport project (because we found some problems with the GlideWebpSupport project).
My question is what would be the risk of this error if not handled, because we have not found any abnormality in the loading of dynamic webp.
Due to the lack of familiarity with fresco and c++ mechanisms, I would like to ask if it is necessary to deal with this error, because we only use fresco to load dynamic webp.
Many thanks.
The text was updated successfully, but these errors were encountered: