From d2eca16240d97704be798bfffa70b11975a80f17 Mon Sep 17 00:00:00 2001 From: Nan Date: Tue, 6 Aug 2024 11:40:11 -0700 Subject: [PATCH] Remove `setLaunchOptions` from OneSignal header * This was added to the OneSignalFramework header file to expose to wrappers. * However, wrappers do not actually use this because they must initialize the SDK (not sufficient to only set launch options) so cold start click listeners can be triggered. * Remove from header so it is not misleading, which suggests it is used. --- iOS_SDK/OneSignalSDK/Source/OneSignalFramework.h | 1 - 1 file changed, 1 deletion(-) diff --git a/iOS_SDK/OneSignalSDK/Source/OneSignalFramework.h b/iOS_SDK/OneSignalSDK/Source/OneSignalFramework.h index a1a2d557b..fd5f70c55 100755 --- a/iOS_SDK/OneSignalSDK/Source/OneSignalFramework.h +++ b/iOS_SDK/OneSignalSDK/Source/OneSignalFramework.h @@ -76,7 +76,6 @@ NS_SWIFT_NAME(login(externalId:token:)); + (Class)Notifications NS_REFINED_FOR_SWIFT; #pragma mark Initialization -+ (void)setLaunchOptions:(nullable NSDictionary*)newLaunchOptions; // meant for use by wrappers + (void)initialize:(nonnull NSString*)newAppId withLaunchOptions:(nullable NSDictionary*)launchOptions; + (void)setProvidesNotificationSettingsView:(BOOL)providesView;