Fatal Exception: parameter must be a descendant of this view - ReactScrollView.java line 218

[RodolfoGS]

Description

I'm having a lot of crashes on Crashlytics related to ReactScrollView.java line 218 on Android.
The crashes appears first time on Nov 15, but I didn't changes on my app.

Happen on Android: 8, 9, 10, 11 and 12. Samsung, Motorola, Google, LGE, OnePlus, etc.

Fatal Exception: java.lang.IllegalArgumentException: parameter must be a descendant of this view
       at android.view.ViewGroup.offsetRectBetweenParentAndChild(ViewGroup.java:6272)
       at android.view.ViewGroup.offsetDescendantRectToMyCoords(ViewGroup.java:6201)
       at android.widget.ScrollView.isWithinDeltaOfScreen(ScrollView.java:1289)
       at android.widget.ScrollView.onSizeChanged(ScrollView.java:1704)
       at com.facebook.react.views.scroll.ReactScrollView.onSizeChanged(ReactScrollView.java:218)
       at android.view.View.sizeChange(View.java:23088)
       at android.view.View.setFrame(View.java:23040)
       at android.view.View.layout(View.java:22897)
       at android.view.ViewGroup.layout(ViewGroup.java:6389)
       at com.facebook.react.uimanager.NativeViewHierarchyManager.updateLayout(NativeViewHierarchyManager.java:243)
       at com.facebook.react.uimanager.NativeViewHierarchyManager.updateLayout(NativeViewHierarchyManager.java:211)
       at com.facebook.react.uimanager.UIViewOperationQueue$UpdateLayoutOperation.execute(UIViewOperationQueue.java:161)
       at com.facebook.react.uimanager.UIViewOperationQueue$1.run(UIViewOperationQueue.java:917)
       at com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches(UIViewOperationQueue.java:1028)
       at com.facebook.react.uimanager.UIViewOperationQueue.access$2600(UIViewOperationQueue.java:48)
       at com.facebook.react.uimanager.UIViewOperationQueue$2.runGuarded(UIViewOperationQueue.java:986)
       at com.facebook.react.bridge.GuardedRunnable.run(GuardedRunnable.java:31)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:250)
       at android.app.ActivityThread.main(ActivityThread.java:7803)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)

Version

0.63.4

Output of react-native info

System:
    OS: macOS 12.0.1
    CPU: (8) x64 Apple M1
    Memory: 20.08 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.1 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.15 - /usr/local/bin/npm
    Watchman: 4.9.0 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.3
      System Images: android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_282 - /usr/bin/javac
    Python: 2.7.18 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ~0.63.4 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

I don't know, I'm seeing them on Crashlytics.

Snack, code example, screenshot, or link to a repository

No response

[julianD77]

We are also experiencing this same issue. Have you made any more headway when investigating it?

We are currently investigating whether it might be related to UI issues where some of our components are rendered off the screen in a scrollable view. Or whether it could be due to some improper handling of the device safe area boundaries.

  npmPackages:
    react: 17.0.1 => 17.0.1 
    react-native: 0.64.2 => 0.64.2 

[RodolfoGS]

@julianD77 I don't know how to reproduce it. The major concern is that I didn't made changes on my app and I didn't have anyone of these crashes before November 15th, but since nov 15 I've a lot of them

Last 30 days chart:

[julianD77]

Hmm that's very interesting - our graph is very similar.

Do you use Google Ads? We do and Im wondering if that could be related to this due to it being something potentially outside of our control that could have resulted in changed behaviour/appearance.

We also haven't yet identified a change in our code or dependencies that could have triggered this.

[RodolfoGS]

Mmm yes, I'm using Google Ads too and your chart is sooo similar

[julianD77]

What version of the Ads dependencies are you using? These are the relevant versions we have:

com.google.ads.mediation:facebook:6.5.1.0@aar
com.google.android.gms:play-services-ads:20.2.0@aar
com.google.android.gms:play-services-ads-lite:20.2.0@aar
com.google.android.gms:play-services-base:17.5.0@aar
com.google.android.gms:play-services-ads-base:20.2.0@aar
com.google.android.gms:play-services-ads-identifier:17.0.0@aar
com.google.android.gms:play-services-basement:17.6.0@aar
androidx.appcompat:appcompat:1.3.1@aar
com.facebook.react:react-native:0.64.2@aar

We are checking now if disabling Ads through Ad Manager does help affect this crash. Hopefully we will know within a couple of hours. Will also:

• try and push out a release with all the Ads related dependencies updated
• try updating the App to a newer RN version, likely 0.65.1 initially

Have you had any further insights/plans to address this/thoughts on where else we might get more information to help with this issue?

[RodolfoGS]

My dependencies are little older than yours:

com.google.android.gms:play-services-ads:19.8.0
com.google.android.gms:play-services-ads-base:19.8.0
com.google.android.gms:play-services-ads-identifier:17.0.0
com.google.android.gms:play-services-ads-lite:19.8.0
com.google.android.ads.consent:consent-library:1.0.6

I can't upgrade to latest version of RN since I'm using expo, and the latest version supported is 0.64. So, I didn't do anything for now, I don't know what can I do :/

[julianD77]

Id definitely suggest trying a release with updated -ads dependencies. I'll update here if we determine that disabling Android Ads / updating the SDKs has affected the frequency of this crash for us.

[Pingou]

Same issue here. Cannot update Admob for now as I'm waiting for react native firebase to support the new version of Admob.

[mqueiroz1995]

Hey @julianD77 , we are facing the same issue in our production app. Was updating Google Ads effective?

[mqueiroz1995]

Curiosly, despite using RN in our app, the stacktraces have no mention to React Native classes and the logs are indicating the problem occurs in a fully native feature. The ocurrencies also started on November 15th and also seems to be unrelated to any of our releases. We have Google Ads in our app.

[julianD77]

We are still trying to verify this and aiming to get a new release out with just an update to use v20.5.0 the Ads SDK today. Will update as soon as I can.

@mqueiroz1995 See facebook.react.uimanager.NativeViewHierarchyManager.updateLayout in the call stack above. This just ends up triggering method calls on the ViewGroup class which is as you say native Android code. The issue I think is how the view hierarchy is getting modified to lead to the case where parameter must be a descendant of this view is no longer true.

[julianD77]

We dont yet have the data for App usage with the updated Google Ads SDK but do now have data for a period when Ads have been fully disabled (from around 1am) and not served to the App, and can see from this chart that it does have an effect on the frequency of this crash:

[julianD77]

Reported on the Google Ads SDK forum here: https://groups.google.com/g/google-admob-ads-sdk/c/EsLEaoRjyNM