continueTrace with startInactiveSpan does not work correctly with Sentry v8

[mikan3rd]

In Sentry v7, continueTrace is used as follows, and checking the Sentry Issue confirms that the traceId used in the frontend is successfully passed on to the backend.

  const server = new ApolloServer({
    context: async ({ req }): Promise<Context> => {
      const sentryTraceHeaders = req.headers['sentry-trace'];
      const sentryTrace = Array.isArray(sentryTraceHeaders) ? sentryTraceHeaders.join(',') : sentryTraceHeaders;
      const baggage = req.headers['baggage'];
      const sentrySpan = Sentry.continueTrace({ sentryTrace, baggage }, (transactionContext) => {
        return Sentry.startInactiveSpan({
          ...transactionContext,
          op: 'gql',
          name: req.body.operationName,
        });
      });
      return { sentrySpan };
    },
  );

In Sentry v8, the transactionContext argument of the continueTrace callback has been removed, so I changed the code as follows.
However, when I did so, the traceId displayed in Sentry's Issue was different for frontend and backend.

  const server = new ApolloServer({
    context: async ({ req }): Promise<Context> => {
      const sentryTraceHeaders = req.headers['sentry-trace'];
      const sentryTrace = Array.isArray(sentryTraceHeaders) ? sentryTraceHeaders.join(',') : sentryTraceHeaders;
      const baggage = req.headers['baggage'];
      const sentrySpan = Sentry.continueTrace({ sentryTrace, baggage }, () => {
        return Sentry.startInactiveSpan({
          op: 'gql',
          name: req.body.operationName,
        });
      });
      return { sentrySpan };
    },
  );

I would like to know the cause and countermeasures.

[mikan3rd]

ref: #13126