Sentry.configureScope not synchronize in native

[nEdAy]

sentry_flutter: ^4.0.0-alpha.2

Sentry.configureScope((Scope scope) async {
    scope.user = User(id: xxx);
});

The user information was set in the flutter and did not synchronize in native(Android).

Hope to add this feature, thanks

[marandaneto]

@nEdAy thanks for this.

True, we still don't synchronize the Scope to the native layer, but we'll definitely do it.

[bruno-garcia]

This is needed also in order to get the scope IP address to the session in native.

[rayliverified]

Is this related to a race condition that happens between the native and Flutter SDKs?
If await is used on SentryFlutter.init(), only the Flutter scope details are sent.
If await is not called on SentryFlutter.init(), only the native details are sent.
I'm currently getting both the native and Flutter details to send by calling Sentry.configureScope before every error report call.

[marandaneto]

@searchy2 not sure if I follow, this is a feature request, not a bug, at least related to this issue.
could you open an issue describing the problem? using the issue template would be very helpful too, thanks,

[rayliverified]

Will do, thanks!

[mafreud]

any update?

[marandaneto]

no, you could always call the Native SDKs yourself via Method channels, we'll eventually do it, just not a high priority right now, PRs are also welcome, happy to guide & review.

[ueman]

Do we want to implement it with ScopeObserver (like the Java implementation)?

[marandaneto]

@ueman it's not a unified behavior across SDK but usually helpful when you have multiple SDKs packaged together.
it sounds like a good idea for me, you can experiment and see how it goes, obviously, we can adapt if necessary.
when Dart is used with Flutter, it should propagate the changes (possible to turn on/off via options).
when Dart is used alone, it should not, so that's why the Interface exists.

[ueman]

A few thoughts on this:

Option 1a:

The Java interface has only synchronus methods, which we can't use because MethodChannels are async. That would require use to make every synchronized property of a Scope to be an async method. This would be a pretty huge breaking change.

Option 1b:

Just like 1a but we don't await the MethodChannels. This is kinda a best effort approach. No breaking changes.

Option 2:

We could do something like a Sentry.configureNativeScope():

await SentryFlutter.configureNativeScope((scope){
// everything which is done in this callback is synced to the native SDKs
});

// No callback syncs the current scope to native
await SentryFlutter.configureNativeScope();

This method would then be responsible to sync everything to the native side.

What do you think @marandaneto ? Or do you have another idea?