warning: The file reference for “OneSignalNotificationServiceExtension” is a member of multiple groups (“Pods” and “”);

[tomosdevans]

Environment Details

Expo SDK 44
EAS managed workflow build

Issue Detail

The following warning is emitted from Xcode (as part of the EAS build):

warning: The file reference for “OneSignalNotificationServiceExtension” is a member of multiple groups (“Pods” and “”); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path.

Note that this issue was observed as part of the diagnosis of #67, so it might be that the two issues are interdependent.

[rgomezp]

Thanks for your patience.
I found the following links to similar issues that might help in resolution. We'll take a look as soon as possible.

https://stackoverflow.com/questions/33395675/cocoapods-file-reference-is-a-member-of-multiple-groups
yonaskolb/XcodeGen#782

[tomosdevans]

Awesome @rgomezp, thank you. FYI - this isn't a priority for me, unless it somehow is the source of a solution to #67 :)

[solarisn]

Experiencing the same issue using Expo SDK 44 after a fresh install and setup following this documentation. Does anyone know if there is a prior version of the onesignal expo plugin that works with Expo 44?

This is a high priority for me as its blocking us from implementing OneSignal. Will try to find a workaround for now.

[rgomezp]

@solarisn ,
Is it not working at all for you? As far as I can tell, this is just a warning.

[solarisn]

@rgomezp Apologies. I mis-attributed the issue to this. I will point out that this Config Plugin heavily abstracts away the setup of the Notification Service Extension but makes the process so invisible that I was unaware that I needed to configure an App Group and regenerate new provisioning profiles. Could be worth mentioning this in the documentation (a short explanation of the NSE and the fact that new provisioning profiles are needed after adding this SDK)

EDIT: Just found the collapsed portion of this page and realized I could easily set up after updating my EAS version. The documentation on the OneSignal website should be updated with the documentation changes in this repo.

[rgomezp]

@solarisn ,
Thanks for your suggestion. This should be done for you automatically if you allow EAS to manage your credentials. It sounds like perhaps you're using local credentials?

[rgomezp]

Closing due to no response

[nmateo]

We're facing the same with expo sdk 49, we build android without eas and iOS with eas, android is working fine, but managed iOS build fails with the same error since transferring our app to another apple account.

[gkpo]

Ok after building the app a LOT of times on EAS, I managed to narrow down the problematic line in our case. It turns out that removing configuration line associatedDomains: ["applinks:your.domain"] fixes the issue and results in a successful build. I have NO IDEA why, as this seems completely unrelated. Still investigating though, as my app needs universal links...

EDIT: what worked for me

After a lot of hair pulling I found the cause of my issue: In the XCode logs there was a line about provisioning profile:

Provisioning profile "*[expo] xx.xx.xx AppStore 2024-02-07T08:50:07.256Z" doesn't support the Associated Domains capability.

After going to my apple developer's account, I found the provisioning profile section (which was overloaded with too many profiles) and delete many Expired and Invalid profiles.

Then I re-generated new provisioning profiles with the command eas credentials (then follow the instructions).
Then I rebuilt my app and it worked.

Hope this helps

[ansh]

@gkpo That was super helpful!