[Android] Fatal Exception: java.lang.IllegalArgumentException #489
Comments
|
I'm facing the same issue on Android API 32. On Android API 30 it's running fine. jineshmistry1312 do you know if this problem occurs on Android or iOS for your users? |
|
The issues with BlurView appear to be Android specific. |
|
android 12 Galaxy S20+ (SM-G985F) runtimeVersions: |
|
The issue appears on Android 12 devices and emulators. |
|
+1 |
|
+2 |
|
+1 |
3 similar comments
|
+1 |
|
+1 |
|
+1 |
|
Android 12 (OPPO K9X) same issue. It appears on the first rendering of BlurView's parent view. If I use effects or cdm lifecycles to maintain a state field called But obviously, that is not a permanently effectual solution, and does not consist with the current document. |
|
Those who need a patch asap can try this (works for me, but use on your own risk) Some details after research:
|
|
@Titozzz Hi m8! Wondering if you can take a look at the issue. Seems this is something happening after the latest release, I'm not sure if I have enough context to address this one 🤔 |
|
@Kureev & everyone else here, I cannot reproduce this on real device / simulator running android 12. Please provide a a reproduction, I would like to address this. |
|
Thank you for looking into this, @Titozzz! Can someone provide a repro case for this one, please? |
|
Yeah, that's a fair point... @Titozzz I do not remember exact case, I think it was more about a matter of random. A month ago I've spent a few hours trying to catch the reason of the exception, but no luck. We have a couple of places in the app where Blur is used, and it doesn't throw in all of them I can make a video recording if that can be somehow helpful |
|
It will only throw in the case the canvas isn't hardware accelerated.. but when would this happen and how to detect it, I am unsure |
|
I just upgraded my libraries from react-native 0.66 -> 0.70, and upgraded react-native-blur to the latest version, and I'm getting this issue on android emulator API 31 |
|
Same problem on React native 0.68.2 and react-native-blur 4.3.0. |
|
My app crashes under a certain condition 100%. In my case, I navigated to a screen with react-navigation and the screen has a scrollview with a blur view in it. When I pop the screen while the blur view is displaying, it crashes, but if the blur view is not displaying on the screen because I scrolled down or up then it doesn't crash. I hope this helps you guys figure out what's going on. |
|
The android library author said he would try to release a new version with a fix, so we'll update when it's ready |
|
This is algo happening to me but only when I upgraded to react navigation 6: before upgrade (working without crashes): after upgrade (crashes every time I open a screen with |
|
Same here . In my case its crashing in both android phone and simulator |
i am also facing the same kind of issue. For example i am going from screen A to B , then from B to C. |
|
I think spotted the react-navigation related issue. So when you trying to navigate to a screen in a different navigation layer, Main = Stack Navigator ( with different type of NAVIGATORS in it eg. PostsNavigator, BlogsNavigator) => and you have also shared screens in this Main stack, to be able to access them from everywhere like Settings, like EditProfile.... Posts = Stack Navigator ( with post related screens in it) |
|
trying this right now... building... |
solved my issue. Thank you so much @Gregoirevda |
|
patch file |
I think then it will force most of the apps to use outdated/less performant renderer, so it doesn't differ much to what I have suggested with if statement removal. Did anyone tested which renderer is picked with adding |
|
Yes @artyorsh this should be a temporary fix. |
yes but what is the answer, sorry
|
How can i check that |
|
Log.d("use hardware", blurView.isHardwareAccelerated()); |
sorry for responding that late,... used it like this. got the build now where should i check ? i dont see anything on logcat or debugger |
|
You should see it in Logcat by filtering on the 1st parameter which is a tag ("use hardware") |
|
this is the setup... filtering use hardware, and dont see anything |
|
Changing the Java file in your node_modules and running npm run android should work |
|
D/use hardware: false @Gregoirevda |
|
confirming that the patch works https://github.com/Kureev/react-native-blur/pull/512/files |
Only use optimised if hardware acceleration isn't disabled fixes Kureev#489
|
Hey, do you guys have any idea of when will this patch be published on npm? |
|
This issue still persists with TouchableOpacity. |
|
Should be fixed on latest |
and others
I am using
@react-native-community/blur": "^4.2.0"Getting below crash issue in Firebase Crashlytics.
The text was updated successfully, but these errors were encountered: