[Question]: Allow Overriding of App Group Name in OneSignal Expo Plugin (Prevents Unwanted App Group Inference)

[ribeiroevandro]

How can we help?

Description

I'm experiencing an issue with the onesignal-expo-plugin regarding the configuration of the App Group for iOS. My app uses a custom app group name (e.g., group.com.vegacheckout.mobile.onesignal), which I have correctly defined in the entitlements section of my app.config.ts file.

However, after running expo prebuild or an EAS build, the plugin automatically adds an additional app group (e.g., group.com.vegacheckout.app.onesignal) inferred from the bundle identifier. This inferred group does not exist in my Apple Developer account and causes build errors in Xcode.

Currently, there is no way to prevent the plugin from adding this extra, unwanted app group, nor is there a supported way to explicitly override the app group name via the plugin configuration. Attempts to use an appGroupName property in the plugin config result in an error, as this property is not supported.

Expected Behavior

• The plugin should respect the app group(s) defined in the entitlements section of the Expo config and not add any additional inferred app groups.
• Alternatively, the plugin should provide a supported configuration option (such as appGroupName) to explicitly set the app group name, and only use that value.

Current Workaround

After every prebuild, I have to manually remove the unwanted app group from the Xcode project settings before building, which is error-prone and not scalable for CI/CD workflows.

Request

Please add support for overriding the app group name in the plugin configuration, or ensure that only the app group(s) defined in the Expo config are used, without inferring or adding extra groups automatically.

Thank you!

OneSignal Expo SDK version

2.0.3

Platform

iOS

Relevant log output

Code of Conduct

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

[bruno-carneiro-da-silva]

Yep I’m facing the same issue for the last 3 days trying to solve the problem. I saw that in the past someone ask them to create this feature where the plug-in sets the app group by default, although most of the developers create custom groups to avoid unique issue that Apple connect has. So the best way is to behave like my friend above said. I appreciate a lot your jobs folks!

[muhammadarsal]

Facing the same issue. It would be really nice if we can get control over specifying custom app group identifier really soon. In my case, Apple is not even allowing me to create the app group identifier matching the pattern this SDK is expecting.

[vargajacint]

Hey guys,
Does anyone were able to overcome this issue?