fix: Return success during Cocoa SDK init on macOS (#2104)

* return success state

* Updated CHANGELOG.md

Author: bitsandfoxes

CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## Unreleased
 
+### Fixes
+
+- When targeting macOS, the SDK no longer fails to sync the scope to native events ([#2104](https://github.com/getsentry/sentry-unity/pull/2104))
+
 ### Features
 
 - When running on Android, Windows or Linux, the SDK now links errors and events originating on different layers (managed, native errors) via `trace ID` ([#1997](https://github.com/getsentry/sentry-unity/pull/1997), [#2089](https://github.com/getsentry/sentry-unity/pull/2089))

package-dev/Plugins/macOS/SentryNativeBridge.m

@@ -72,14 +72,22 @@ void SentryNativeBridgeOptionsSetInt(const void *options, const char *name, int3
     dictOptions[[NSString stringWithUTF8String:name]] = [NSNumber numberWithInt:value];
 }
 
-void SentryNativeBridgeStartWithOptions(const void *options)
+int SentryNativeBridgeStartWithOptions(const void *options)
 {
     NSMutableDictionary *dictOptions = (__bridge_transfer NSMutableDictionary *)options;
+    NSError *error = nil;
+
     id sentryOptions = [[SentryOptions alloc]
         performSelector:@selector(initWithDict:didFailWithError:)
-        withObject:dictOptions withObject:nil];
+        withObject:dictOptions withObject:&error];
+
+    if (error != nil)
+    {
+        return 0;
+    }
 
     [SentrySDK performSelector:@selector(startWithOptions:) withObject:sentryOptions];
+    return 1;
 }
 
 void SentryConfigureScope(void (^callback)(id))