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

iOS get error Dependency for P1: Debug:SwiftDriver Compilation Requirements app normal arm64 com.apple.xcode.tools.swift.compiler is not absolute #1397

Open
sootood opened this issue Jul 19, 2023 · 0 comments

Comments

@sootood
Copy link

sootood commented Jul 19, 2023

we decided to update macOS and XCode to lunching our react-native app on new version softwares although it had some weird errors, ran and built success. we ignored them at that time but when we wanted to get an archive those error presented and made archiving failed.
there tow type of error

  1. some of theme belong to TensorFlowLiteSwift like below(23 errors like these error ):

Dependency for P1:target-app- 69a90293829c4577a609157fb85f5e0d7ceb6b36bcfc2fb90f69ac96de4975d6-:Debug:SwiftDriver Compilation Requirements app normal arm64 com.apple.xcode.tools.swift.compiler is not absolute (Pods/TensorFlowLiteC/Frameworks/TensorFlowLiteC.framework/Modules/module.modulemap).

  1. some of theme refer to heaers in pods(6 errors like these):

Dependency for P1:target-app- 69a90293829c4577a609157fb85f5e0d7ceb6b36bcfc2fb90f69ac96de4975d6-:Debug:SwiftDriver Compilation Requirements app normal arm64 com.apple.xcode.tools.swift.compiler is not absolute (Pods/TensorFlowLiteC/Frameworks/TensorFlowLiteC.framework/Modules/module.modulemap).

we faced with this error with :
XCode | 14.1
react-native | 69.3
TensorFlowLiteSwift | 2.3.0
TensorFlowLiteSwift | 2.3.0
cocoapods | 11.12.1
PromisesObjC | 1.2.12
macOs | 13.4
ruby | 2.63 (tested 2.7.4)
on apple macmini intel

**we try to solve it by solutions below: **

  1. add [system] after our framework module in modulemap files (it removes TensorFlowLiteSwift errors pot 6 of them that appear because promisses still exist )
  2. removing ${PROJECT_DIR} from User Header Search Path in build setting but it made other errors so it doesn't work

we stuck in it

please help us

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

1 participant