Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple commands produce '/Users/expo/Library/Developer/Xcode/DerivedData/[REDACTED]/Build/Intermediates.noindex/ArchiveIntermediates/[REDACTED]/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/customerio_reactnative.framework' #205

Open
Joaguirrem opened this issue Jan 16, 2025 · 2 comments

Comments

@Joaguirrem
Copy link

SDK version:
customerio-expo-plugin: 2.0.0-beta.1
customerio-reactnative: 4.2.1
expo-share-extension: 2.0.2

Environment:

  • Development
  • Production

Are logs available?

error: Multiple commands produce '/Users/expo/Library/Developer/Xcode/DerivedData/[REDACTED]/Build/Intermediates.noindex/ArchiveIntermediates/[REDACTED]/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/customerio_reactnative.framework'
    note: Target 'customerio-reactnative' (project 'Pods') has create directory command with output '/Users/expo/Library/Developer/Xcode/DerivedData/[REDACTED]/Build/Intermediates.noindex/ArchiveIntermediates/[REDACTED]/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/customerio_reactnative.framework'
    note: Target 'customerio-reactnative.default-apn' (project 'Pods') has create directory command with output '/Users/expo/Library/Developer/Xcode/DerivedData/[REDACTED]/Build/Intermediates.noindex/ArchiveIntermediates/[REDACTED]/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/customerio_reactnative.framework'

Describe the bug
When attempting to archive the iOS app with a share extension included, the build fails due to a conflict with customerio-reactnative. The error indicates multiple commands are producing the same output directory for the framework. However, this issue does not occur during regular builds.

To Reproduce

  1. Include customerio-expo-plugin and customerio-reactnative in the project dependencies.
  2. Add a share extension to the project (expo-share-extension).
  3. Attempt to archive the iOS app. I'm using Xcode 16.1 (16B40).

Expected behavior
Archive successful.

Additional context

[
      'customerio-expo-plugin',
      {
        android: {
          googleServicesFile: './google-services.json',
        },
        ios: {
          iosDeploymentTarget: '15.1',
          pushNotification: {
            env: {
              cdpApiKey: CUSTOMER_IO_API_KEY,
              region: 'us',
              siteId: CUSTOMER_IO_SITE_ID,
            },
            useFrameworks: 'static',
            useRichPush: true,
          },
          useFrameworks: 'static',
        },
      },
    ],

By making the following changes the archive finished successfully.

  • Removing from Podfile:
# --- CustomerIO Host App START ---
  pod 'customerio-reactnative/apn', :path => '../node_modules/customerio-reactnative'
# --- CustomerIO Host App END ---
  • Modifying customerio-reactnative.podspec
   s.dependency "CustomerIO/DataPipelines", package["cioNativeiOSSdkVersion"]
   s.dependency "CustomerIO/MessagingInApp", package["cioNativeiOSSdkVersion"]
+  s.dependency "CustomerIO/MessagingPushAPN", package["cioNativeiOSSdkVersion"]

...

     ss.dependency "CustomerIO/MessagingPush", package["cioNativeiOSSdkVersion"]
   end

-  # Note: Subspecs inherit all dependencies specified the parent spec (this file). 
-  s.subspec 'apn' do |ss|
-    ss.dependency "CustomerIO/MessagingPushAPN", package["cioNativeiOSSdkVersion"]
-  end
@mrehan27
Copy link
Contributor

Thanks for reaching out and sharing the details. Apologies for any inconvenience this may have caused. Can you please try following steps to help resolve the issue?

  • Remove DerivedData folder and clear any other cached or build files and check if the issue still exists
  • If the issue persists, try reproducing it after temporarily removing useFrameworks: 'static'
    • If this resolves the issue and removing it is feasible, you can proceed without it
    • If the issue persists or you can't remove it, please let us know so we can explore other solutions to help resolve the problem

Appreciate the details you've provided and your patience as we work together to debug and address the root cause. Have a great day!

@Joaguirrem
Copy link
Author

@mrehan27 by removing useFrameworks: 'static' the archive finished successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants