AbortError exceptions on iOS

[michaelrevans]

Expected Behavior

No AbortError is thrown when using the Session Replay.

Looks similar to #957, but I cannot reopen that issue.

Current Behavior

Receiving thousands of AbortError reports in monitoring platform (Sentry).

I've since reverted to turn off Session Replay, as it was becoming untenable with the volume of issues coming in.

Possible Solution

I don't know, unfortunately.

Steps to Reproduce

1. Introduce @amplitude/plugin-session-replay-browser npm dependency in package.json
2. Add it to existing amplitude tracking in a React hook.

import * as amplitude from "@amplitude/analytics-browser";
+ import { sessionReplayPlugin } from "@amplitude/plugin-session-replay-browser";
import { useEffect } from "react";

const useAmplitude = () => {
  useEffect(() => {
    try {
      if (<api_key>) {
+       const sessionReplayTracking = sessionReplayPlugin();
+       amplitude.add(sessionReplayTracking);
        amplitude.init(<api_key>, undefined, { /* options omitted for brevity */ })
      }
    } catch (error) {
      console.error("Error initialising Amplitude Analytics", error);
    }
  }, []);
};

export default useAmplitude;

Environment

• JS SDK Version:
  • "@amplitude/plugin-session-replay-browser": "^1.16.13"
  • "@amplitude/analytics-browser": "^2.11.11"
• Installation Method: NPM
• Browser and Version: Predominantly iOS with Mobile Safari, but also on macOS and in other browsers like Instagram, Facebook, Chrome

[daniel-graham-amplitude]

Hi. This likely means that a fetch request is being cancelled, and that request is being cancelled because it's timing out. Do you have any information on which endpoint it's attempting to call?

[michaelrevans]

@daniel-graham-amplitude it differs every time. There's no pattern to the URL that's being called. Sometimes it's an internal API call, other times it's external, like Google Analytics. As pointed out in the linked issue, it seems be raised asynchronously and there's no stack trace.

It's difficult to give concrete data since we're talking about over 23k issues and I don't have a good way to export and analyse them.

The timing is consistent with the introduction and reversion of the Session Replay, though.