OneSignalNotificationServiceExtension provisioning profile?

[raunaqsingh2020]

Hi, I am getting the following Fastlane error when I try to build for iOS (eas build --profile development --platform ios):

❌ error: No profiles for 'bundle id.OneSignalNotificationServiceExtension' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'bundle id.OneSignalNotificationServiceExtension'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'OneSignalNotificationServiceExtension' from project '***')

Do I have to manually create an additional identifier (.OneSignalNotificationServiceExtension) and then a provisioning profile for this?

The plugin works perfectly when I comment all the OneSignal related code out before the build, and then uncomment it all after running expo start --dev-client.

Thanks so much!

[rgomezp]

Howdy,
To answer your question, you shouldn't need to create an additional identifier for the NSE. This is done for you automatically. The provisioning profile should be an XCode Managed Profile if automatic signing is on (which it should be). Try visually inspecting the Signing and Capabilities configuration in the Xcode workspace. You should have:

• Team: <your team>
• Bundle Identifier: <your bundle id> AND <your bundle id>.OneSignalNotificationServiceExtension

It sounds like something in your environment is preventing automatic signing as I'm not seeing that error on my end.

[raunaqsingh2020]

Hmm, how can I check the Xcode workspace for a managed workflow?

I don't see the <your bundle id>.OneSignalNotificationServiceExtension identifier on the Apple Developer Console.

[rgomezp]

[raunaqsingh2020]

When I try building the native project (expo run:ios), I get the following:

Failed to build iOS project. "xcodebuild" exited with error code 65.
To view more error logs, try building the app with Xcode directly, by opening /Users/raunaqsingh/Developer/canada-goose/ios/DP.xcodeproj.

Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project /Users/raunaqsingh/Developer/canada-goose/ios/DP.xcodeproj -configuration Debug -scheme DP -destination id=079A8E83-0A88-4223-8185-61FA54F6734A

User defaults from command line:
    IDEPackageSupportUseBuiltinSCM = YES

note: Using new build system
note: Planning
Analyze workspace

Create build description
Build description signature: 5c9947c631b8dc214ce840dc1724b44c
Build description path: /Users/raunaqsingh/Library/Developer/Xcode/DerivedData/DP-chreouiuptppyzbmrutwxoddflad/Build/Intermediates.noindex/XCBuildData/5c9947c631b8dc214ce840dc1724b44c-desc.xcbuild

note: Build preparation complete
note: Building targets in dependency order
/Users/raunaqsingh/Developer/canada-goose/ios/Pods/Target Support Files/Pods-DP/Pods-DP.debug.xcconfig:1:1: error: unable to open file (in target "DP" in project "DP")
/Users/raunaqsingh/Developer/canada-goose/ios/Pods/Target Support Files/Pods-DP/Pods-DP.debug.xcconfig:1:1: error: unable to open file (in target "DP" in project "DP")
/Users/raunaqsingh/Developer/canada-goose/ios/Pods/Target Support Files/Pods-DP/Pods-DP.debug.xcconfig:1:1: error: unable to open file (in target "DP" in project "DP")
/Users/raunaqsingh/Developer/canada-goose/ios/Pods/Target Support Files/Pods-DP/Pods-DP.debug.xcconfig:1:1: error: unable to open file (in target "DP" in project "DP")


objc[6180]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x20b75fb78) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10cfb02c8). One of the two will be used. Which one is undefined.
objc[6180]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x20b75fbc8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10cfb0318). One of the two will be used. Which one is undefined.
2021-12-30 16:43:05.279 xcodebuild[6180:3594115] 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.
** BUILD FAILED **

It does create an .xcodeproj and the <your bundle id>.OneSignalNotificationServiceExtension is there, but it does not create a .xcworkspace

Could the The file reference for "OneSignalNotificationServiceExtension" is a member of multiple groups ("Pods" and ""); this indicates a malformed project. warning be the problem? If you want to take a look at the project, it's here: https://github.com/dailypenn/canada-goose.

Thanks so much!

[jparksecurity]

@rgomezp we're having the same issue although I can see the right bundle identifier on Xcode UI.

We pass ios credential files when we run EAS build. Do you think if it is something to do with this?

Does anyone know if setting credentialsSource to local in eas.json turns off automatic signing?

If credentialsSource is not the issue, I think the problem is
The file reference for "OneSignalNotificationServiceExtension" is a member of multiple groups ("Pods" and ""); this indicates a malformed project.

because it's the first error I see on the console log after EAS build runs
xcodebuild -resolvePackageDependencies -workspace ./XXXX.xcworkspace -scheme XXXX -configuration Release

[raunaqsingh2020]

I didn't set credentialsSource and still have the issue.

[jparksecurity]

@ raunaqsingh2020 Thanks for sharing your config. Then I guess credentialsSource is less likely the problem.

FYI I think expo prebuild --platform ios --clean generates .xcworkspace file.

You can follow rgomezp's instruction to check the bundle identifier by opening Xcode with the file.

[raunaqsingh2020]

is there any update as to whether this is an issue with the plugin or our setups? thanks again!

[russriser]

I don't have Xcode (I work on PC), I rely on EAS Build to build my ios apps.

So, I have no idea how to verify if automatic signing is the issue. And if it were, I don't know how to fix it.

[lisaah]

Just adding another point of anecdata, also seeing this error. It seems like automatic signing is disabled when running our eas managed build based on the error message (no issues for android build). However, when I run expo prebuild --platform ios --clean, the workspace shows says automatically manage signing is enabled. Onesignal bundle identifier is not there.

[r1cs1]

I was running into the same issue. To resolve this issue first I had to create another bundle identifier and provisioning profile as stated here. I've missed this first.

Then I also had to setup credential source to local with multi target credentials.json as it is here because EAS didn't pull the extensions provisioning profile even if that was submitted from the credentials.json to EXPO (That wasn't straightforward either). Or if I don't want to use local credentials then I had to run expo prebuild --platform ios --clean

{
  "android": {
    ...
  },
  "ios": {
    "<<APPNAME>>": {
      "distributionCertificate": {
        "path": "***",
        "password": "***"
      },
      "provisioningProfilePath": "***"
    },
    "OneSignalNotificationServiceExtension": {
      "distributionCertificate": {
        "path": "***",
        "password": "***"
      },
      "provisioningProfilePath": "***"
    }
  }
}

Now it gave me a new error commented here

To resolve this I had to patch the onesignal-expo-plugin to use the same iOS target as the expo sdk. (12.0 for my case).

If anyone knows what I've missed in order to skip these patches to get it to work I'd appreciate it :)

[seyaobey-dev]

Hi. I'm facing same issue, same error. But I rely completely on (remote) eas build to build my ios app. I do not have Xcode locally to try to visually inspect the Signing and Capabilities configuration in the Xcode workspace. I cannot run expo prebuild --platform ios --clean

[raunaqsingh2020]

@r1cs1

Hey I tried to follow your comment. Here's what I have right now:

Identifiers:

• com.thedailypennsylvanian.mobileapp
• com.thedailypennsylvanian.mobileapp.OneSignalNotificationServiceExtension

Profiles:

• com.thedailypennsylvanian.mobileapp.profile
• com.thedailypennsylvanian.OneSignal.profile

My credentials.json is similar to what you did but I am now receiving the following errors:

❌  error: Provisioning profile "com.thedailypennsylvanian.OneSignal.profile" doesn't support the group.com.thedailypennsylvanian.mobileapp.onesignal App Group. (in target 'OneSignalNotificationServiceExtension' from project 'DP')

❌  error: Provisioning profile "com.thedailypennsylvanian.OneSignal.profile" doesn't match the entitlements file's value for the com.apple.security.application-groups entitlement. (in target 'OneSignalNotificationServiceExtension' from project 'DP')

Did you get any these errors as well? and if so, how did you resolve them?

thanks!