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

Getting Multiple commands produce error when building using XCode 14.3 #1009

Open
NiharR27 opened this issue Jun 20, 2023 · 7 comments
Open
Assignees

Comments

@NiharR27
Copy link

NiharR27 commented Jun 20, 2023

Describe the bug
trying to implement Themis on my react native app with below environment is causing the build to fail immediately as soon as I press Build on XCode

To Reproduce
Steps to reproduce the behavior:

  1. Use 'react-native-themis: 0.14.11' with the environment specified below (and the xcode version)
  2. Click Build
  3. See the following error:
error:
Multiple commands produce '/Users/nihar/Library/Developer/Xcode/DerivedData/ConpagoResponsive-bteuwcmkzpfhhjfkpiwawcanldzt/Build/Products/Debug-iphonesimulator/react-native-themis/react_native_themis.framework/Headers/scell.h'

Expected behavior
It fails straight away with the above error (rather than building successfully)

Environment (please complete the following information):

  • iOS Simulator iPhone 14 (iOS 16.4)
  • Apple M1 Pro
  • Themis version: 0.14.11
  • React native version: 0.70.8
  • Installation way:
    • yarn add react-native-themis
    • cd ios
    • pod install
    • open xcode
    • clean build and press build
    • see the error

Additional context
Add any other relevant context for the problem here. Share an example project, if you can.

Screenshot 2023-06-20 at 11 14 50 am

@NiharR27 NiharR27 changed the title Getting Multiple commands produce when building using XCode 14.3 Getting Multiple commands produce error when building using XCode 14.3 Jun 20, 2023
@vixentael
Copy link
Contributor

@NiharR27 could you please share an empty test project that reproduces this error?

Because we have a react native example that was working fine:
https://github.com/cossacklabs/themis/tree/master/docs/examples/react-native

Another option would be to try our react native example to see if it's working?

@NiharR27
Copy link
Author

@NiharR27 could you please share an empty test project that reproduces this error?

Because we have a react native example that was working fine:

https://github.com/cossacklabs/themis/tree/master/docs/examples/react-native

Another option would be to try our react native example to see if it's working?

Thanks will do once I get to work tomorrow

@jonjamz
Copy link

jonjamz commented Aug 26, 2023

I'm experiencing the same issue, using Expo SDK 49 with the managed workflow.

@jonjamz
Copy link

jonjamz commented Aug 29, 2023

I'm still not able to build my app with react-native-themis. I tried creating a build plugin to remove duplicate files, but it didn't fully solve the problem. I ended up following the documentation closely and building a similar API manually using react-native-quick-crypto, with the intention of swapping out the insides when I can one day use this package.

I wanted to contribute to the solution here by providing a repro, but it seemed that I did not have the problem with a fresh Expo project with react-native-themis installed. My actual app is quite large, so to start from scratch and progress through until I track down the problem is not an option at this time.

This is the only package I've experienced this kind of error with, so I hope you can identify the issue and fix it soon. I would love to use this.

@radetsky radetsky self-assigned this Aug 29, 2023
@jonjamz
Copy link

jonjamz commented Aug 29, 2023

I'm experiencing the same issue, using Expo SDK 49 with the managed workflow.

Just to note that although I'm using the managed workflow, I'm using custom development clients.

@johnny-mcfadden-dailypay

Also getting this issue on a managed expo project when changing useFrameworks to static.

@johnny-mcfadden-dailypay

For anyone else, for me this was in a managed expo app and was the result of adding static frameworks for firebase packages. To resolve this, instead of globally using static frameworks for all ios pods, I created an expo plugin to only use static frameworks for any firebase packages.

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

5 participants