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
Expect that any transactions started from native layer before .Net SDK initialized will work and all transactions appear on Sentry console.
Actual Result
Android
Transaction start operation said that Tracing is disabled but it is in build- and run-time configurators.
2024-04-08 12:23:16.020 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Custom activity started
2024-04-08 12:23:16.021 20985-20985 Sentry com.teachdraw.tk.sandbox I Tracing is disabled and this 'startTransaction' returns a no-op.
2024-04-08 12:23:16.021 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Transaction created
2024-04-08 12:23:16.021 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Span started
2024-04-08 12:23:16.021 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Super method invoked
2024-04-08 12:23:16.022 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Span finished
2024-04-08 12:23:16.022 20985-20985 SentryCustomActivity com.teachdraw.tk.sandbox D Custom activity finished
iOS
On iOS case transaction started as I see but it's not finishing because of internal_error
default 13:48:57.262723+0300 Template [Sentry] [debug] [SentryTransactionContext:147] Created transaction context with name Unity start
default 13:48:57.262789+0300 Template [Sentry] [debug] [SentrySpanContext:93] Created span context with trace ID 2af73caa97e647f6ba390b8b3a0add91; span ID 9b797e29c3ba4190; parent span ID (null); operation main
default 13:48:57.262845+0300 Template [Sentry] [debug] [SentryFramesTracker:79] Initialized frame tracker <SentryFramesTracker: 0x280db2450>
default 13:48:57.264883+0300 Template [Sentry] [debug] [SentryTracer:203] Started tracer with id: 2af73caa97e647f6ba390b8b3a0add91
default 13:48:57.265038+0300 Template [Sentry] [debug] [SentryLaunchProfiling:157] No launch tracer present to stop.
default 13:48:57.265075+0300 Template [Sentry] [debug] [SentryLaunchProfiling:45] Won't profile next launch due to specified options configuration: options.enableAppLaunchProfiling: 0; options.enableTracing: 0
default 13:48:57.265130+0300 Template [Sentry] [debug] [SentryFileManager:51] No file to delete at /var/mobile/Containers/Data/Application/EF35AB1F-318A-4BF7-AFFE-90B9951F0B0B/Library/Application Support/io.sentry/profileLaunch
default 13:48:57.498689+0300 Template [Sentry] [debug] [SentryReachability:138] SentryConnectivityCallback called with target: <SCNetworkReachability 0x102c07240 [0x1f5f00190]> {name = sentry.io (complete, 35.186.247.156), flags = 0x00000003, if_index = 9}; flags: 3
default 13:48:57.498735+0300 Template [Sentry] [debug] [SentryReachability:103] Entered synchronized region of SentryConnectivityCallback with flags: 3
default 13:48:57.498760+0300 Template [Sentry] [debug] [SentryReachability:119] Notifying observers...
default 13:48:57.498886+0300 Template [Sentry] [debug] [SentryReachability:121] Notifying <SentryBreadcrumbTracker: 0x2824a8920>
default 13:48:57.498907+0300 Template [Sentry] [debug] [SentryScope:122] Add breadcrumb: <SentryBreadcrumb: 0x2833a2ac0, {
category = "device.connectivity";
data = {
connectivity = wifi;
};
level = info;
timestamp = "2024-04-08T10:48:57.492Z";
type = connectivity;
}>
default 13:48:57.498928+0300 Template [Sentry] [debug] [SentryReachability:121] Notifying <SentryHttpTransport: 0x2802a4660>
default 13:48:57.498948+0300 Template [Sentry] [debug] [SentryHttpTransport:106] Internet connection is back.
default 13:48:57.498967+0300 Template [Sentry] [debug] [SentryHttpTransport:268] sendAllCachedEnvelopes start.
default 13:48:57.499013+0300 Template [Sentry] [debug] [SentryHttpTransport:280] No envelopes left to send.
default 13:48:57.499037+0300 Template [Sentry] [debug] [SentryHttpTransport:362] Finished sending.
default 13:48:57.499062+0300 Template [Sentry] [debug] [SentryReachability:125] Finished notifying observers.
default 13:48:57.764524+0300 Template [Sentry] [debug] [SentryTracer:452] Finished trace with traceID: (null) and status: internal_error
Thanks for the detailed issue!
One thing to be aware of and to manage expectations: Currently, there is no mechanism to sync transactions and spans between the native and the managed layer. So you'd be "stuck" with native transaction - for now (tm)
Currently, there is no mechanism to sync transactions and spans between the native and the managed layer. So you'd be "stuck" with native transaction - for now (tm)
But it should work if I start and finish some transactions only on native layer and some another only on managed ? Am I understand correctly (that means that problem I described is valid) ?
You can start and finish things on the same layer. But there is no passing of ID happening. So the spans and transactions will be disconnected from each other based on their layer.
Yes, that would be great, in my case I need to track some native work we do before Unity starts separately from something inside engine, without blending Sentry layers.
Environment
We are using:
The issue is presenting on iOS and Android devices and cant be checked in Editor because it's connected with native tracking before the engine start.
Steps to Reproduce
Android
iOS
Expected Result
Expect that any transactions started from native layer before .Net SDK initialized will work and all transactions appear on Sentry console.
Actual Result
Android
Transaction start operation said that
Tracing is disabled
but it is in build- and run-time configurators.iOS
On iOS case transaction started as I see but it's not finishing because of
internal_error
Logs or screenshots
Android
Full log from app start
sentry-android-activity-transaction-all.log
The same log but filtered with
Sentry
sentry-android-activity-transaction-filtered.log
iOS
sentry-ios-main-transaction-all.log
Project I used for test
unity-sentry-test.zip
The text was updated successfully, but these errors were encountered: