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
When initializing Amplitude-Swift, pass true for tracking screenViews (e.g. DefaultTrackingOptions(screenViews: true))
Attempt to start your application.
Observe the error thrown
Thread 1: "New Relic detected an unrecognized selector, 'amp_viewDidAppear:', sent to 'UIViewController'. It's possible _cmd was renamed by an unsafe method_exchangeImplementations()."
Expected Behavior
Tracking should begin seamlessly at app launch.
Current Behavior
When launching with
screenViews
set totrue
, the call toamp_viewDidAppear
triggers an exception in New Relic profiler.Possible Solution
Potentially use an alternative to swizzling that doesn't trigger other SDKs? (Not sure if this is possible)
Steps to Reproduce
true
for trackingscreenViews
(e.g.DefaultTrackingOptions(screenViews: true)
)Thread 1: "New Relic detected an unrecognized selector, 'amp_viewDidAppear:', sent to 'UIViewController'. It's possible _cmd was renamed by an unsafe method_exchangeImplementations()."
Environment
The text was updated successfully, but these errors were encountered: