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
Each should have dedicated page explaining how errors and performance can be captured in applications combining native (React Native, Flutter, iOS, Android) views and webviews.
Note that at the moment there is no special communication between the SDKs. Screens from inside of the webviews would not appear on the mobile insights. They would be reported as page load transactions by the JS SDK.
The text was updated successfully, but these errors were encountered:
@krystofwoldrich what's the goal of this exactly?
Is it just to document how to instrument webViews using JS SDK?
Or does it include a trace propagation, or any kind of sync between each SDKs?
This applies to all mobile SDKs.
Each should have dedicated page explaining how errors and performance can be captured in applications combining native (React Native, Flutter, iOS, Android) views and webviews.
Note that at the moment there is no special communication between the SDKs. Screens from inside of the webviews would not appear on the mobile insights. They would be reported as page load transactions by the JS SDK.
The text was updated successfully, but these errors were encountered: