-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta tag parsing cause exception #314
Comments
The documentation for getString() claims that it will return null if no mapping of the desired type exists: http://developer.android.com/reference/android/os/BaseBundle.html#getString(java.lang.String) It's possible that may not be true on different versions of Android, do you have a stack trace? |
It occurs on 5.0.1
|
Can you add the metadata tag you're using? Does this cause a crash? |
It doesn't crash the app. but exception logs are printed. |
It occurs on 4.3, 4.4.4 and logs only. |
Ok, glad it doesn't crash. We could either prefix the key, which would avoid the log but require String parsing or we could probably use get() and instanceof. I guess I'd lean toward the latter since it doesn't involve changing the format. |
I am getting this error as well. In my Manifest:
The previous version did not have this bug. Is there a fix yet, or would reverting be best for the time being? |
I'm inclined to not fix it until the next major release. Doing so will require changing our metadata tag format and this doesn't cause a crash, just some log spam. If you feel strongly we could do a dot release with a new and legacy format, although that's rather ugly. |
If I can find a way to remove this warnings without changing the format of our tag, I'll push that in 3.5.1 since we need to do the dot release anyway for #320. |
Glide 3.5.0
com.bumptech.glide.module.ManifestParser
==> GLIDE_MODULE_VALUE.equals(appInfo.metaData.getString(key))
may cause ClassCastException if the manifest has meta-data for other libraries that is not a string value.
The text was updated successfully, but these errors were encountered: