[Bug]: Importing `OneSignalFramework.h` in bridging header results in error `No type or protocol named 'OSUser'` / `'OSLiveActivities'`

[ndemie]

What happened?

I upgraded our OneSignal SDK from 5.0.2 to 5.2.6 using CocoaPods.

After upgrading, I'm unable to compile our project due to errors in OneSignalFrame due to error No type or protocol named 'OSUser' / 'OSLiveActivities'

It seems to be related to using a Bridging Header, as the error seems to originate there. I've tried adding OneSignalLiveActivities and OneSignalOSCore to the Bridging Header as these files seem to live there; but to no avail.

Steps to reproduce?

1. Use version 5.2.6
2. Add `#import <OneSignalFramework/OneSignalFramework.h>` to your `SWIFT_OBJC_BRIDGING_HEADER`
3. Try to run project
3. Get errors

What did you expect to happen?

I do not expect these errors to happen, as they did with the 5.0.2

OneSignal iOS SDK version

5.2.6

iOS version

15

Specific iOS version

Our project targets iOS 15

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[ndemie]

Similar, unsolved, issue in the react-native-onesignal repo; OneSignal/react-native-onesignal#1717

[ManjunathaReddyNS]

Any update on this issue?

[ManjunathaReddyNS]

This issue only occurs for cross-platform projects, such as those containing .mm
For OneSignal team @nan-li
Could guys please consider addressing this issue in the next release? Currently, we’re unable to integrate the latest version of OneSignal in cross-platform projects, except for iOS native projects

[ManjunathaReddyNS]

Able to resolve this issue by adding OneSignal code in Swift file instead of Objective C.

[MrSco]

Able to resolve this issue by adding OneSignal code in Swift file instead of Objective C.

i'm using the 5.1.3/5.1.6 workaround since 5.2.6/5.2.7 still has the No type or protocol named 'OSUser' / 'OSLiveActivities' error.

my appdelegate.mm didn't play nice when I tried to convert it to swift. is there any eta on when this will be fixed for objective c without having to downgrade?

[ndemie]

I haven't been able to resolve this issue myself. I've resorted to downgrading to 5.1.6 - which is the latest version which works without this issue.

This issue will become a big problem for us soon as our app is a whitelabel app and is launched continuously as new apps. From February 12th 2025 (postponed from November 12th 2024) ITMS-91061 (privacy manifest) will be enforced which means we cannot release new apps with this version of the OneSignal SDK. From the plethora of third party libraries we use, OneSignal is the only one causing issues.

[nan-li]

Hi everyone, thank you for reporting, I apologize for the delay in investigating this issue.

I will be taking a look into this issue and follow up as soon as I can.

[ndemie]

Hi everyone, thank you for reporting, I apologize for the delay in investigating this issue.

I will be taking a look into this issue and follow up as soon as I can.

Hi nan-li. Any update on this?

[chenhongchen]

Put the header file reference into the AppDelegate.m file, there won't be any errors

[nejato]

Put the header file reference into the AppDelegate.m file, there won't be any errors

What header file did you place into the appdelegate.m file? Can you give me more example

[lfalcao]

#import <OneSignal/OneSignal.h> ?

Replace AppDelegate.mm with AppDelegate.swift and it works.

[nejato]

#import <OneSignal/OneSignal.h> ?

Replace AppDelegate.mm with AppDelegate.swift and it works.

my project is object-C, with many relate library, it is problem if change *.mm to *.swift, do you have any solution if we dont change the file extension.