This has been observed for Perfetto Profiling in our demo app, where a trace had a profiler.id set, but the actual profile was missing.
When linking traces and profiles, we link them unconditionally, e.g. here:
|
private @NotNull SentryId getProfilerId() { |
This stems from ProfilingManager, where requests can be rate-limited, and rejections are only reported via async profiling result. Or in other words PerfettoProfiler.start() will always return true, and only processResult at a later point will be able to detect rate limiting.
This has been observed for Perfetto Profiling in our demo app, where a trace had a
profiler.idset, but the actual profile was missing.When linking traces and profiles, we link them unconditionally, e.g. here:
sentry-java/sentry/src/main/java/io/sentry/SentryTracer.java
Line 552 in bcd3e76
This stems from
ProfilingManager, where requests can be rate-limited, and rejections are only reported via async profiling result. Or in other wordsPerfettoProfiler.start()will always return true, and onlyprocessResultat a later point will be able to detect rate limiting.