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

How to embed custom Platform framework (ex: MATTER ,,,) in Pod Project #11874

Open
1 task done
HururuekChapChap opened this issue Apr 21, 2023 · 3 comments
Open
1 task done

Comments

@HururuekChapChap
Copy link

HururuekChapChap commented Apr 21, 2023

Report

What did you do?

When adding a custom Platform Framework with the same name to a Pod Project and building it locally, there are no issues. However, the following error occurred in Test Flight:

ITMS-90565: Invalid Bundle Structure - - The framework at '/Payload/XXX.app/Frameworks/Matter.framework' is not permitted. Do not include platform frameworks in your app.

This problem was resolved by adding Matter.xcframework to Link Binary With Libraries in the Main Project. However, if Matter.xcframework is not added to vendered_framework in the Pod Project, a No Such Module build error occurs in the Pod Project. If both the Main Project and Pod Project add Matter.framework, the following error occurs:

Multiple commands produce '/Users/XXX/Library/Developer/Xcode/DerivedData/XXXX-ftezoitulfteksaezryqlfozlpvh/Build/Products/TEST-iphoneos/XXX.app/Frameworks/Matter.framework'

this is my podSpec and podfile

- PodSpec 
Pod::Spec.new do |spec| 
spec.name = "XXXX"
spec.version = "0.0.1"
spec.summary = "A short description of XXXX."
spec.description = "A detail description of XXX."
spec.homepage = "http://example/XXX"
spec.license = "MIT"
spec.author = { "XXX.XXX" => "[XXXX.XXX@XXX.com](mailto:XXX.XXX@XXX.com)" }
spec.platform = :ios, "13.0"
spec.source = { :git => "http://mod.XXX.com/conv/IoTService_iOS", :tag => "#{spec.version}" }
spec.source_files  = ["XXX/**/*.{h,m,swift}"]
spec.exclude_files = "Classes/Exclude"
spec.vendored_frameworks  = "Frameworks/IotManagerLib.framework" , "Frameworks/Matter.xcframework"
spec.dependency 'RxSwift'
spec.dependency 'Moya'
end

What did you expect to happen?

What I want is for the ITMS-90565: Invalid Bundle Structure error not to occur on TestFlight when I submit it by adding the Platform Framework, Matter.xcframework.

Is it possible to reference the Embed Framework in the Main Project from the Pod Project?

Can I add the modified Matter.xcframework to Link Binary with Libraries in the Pod Project?

CocoaPods Environment

ℹ Please replace these two lines with the output of pod env.

Stack

   CocoaPods : 1.12.0
        Ruby : ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-darwin22]
    RubyGems : 3.4.10
        Host : macOS 13.0 (22A380)
       Xcode : 14.3 (14E222b)
         Git : git version 2.39.2 (Apple Git-143)
Ruby lib dir : /usr/local/Cellar/ruby/3.2.2/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/

Installation Source

Executable Path: /usr/local/Cellar/cocoapods/1.12.0/libexec/bin/pod

Plugins

cocoapods-deintegrate : 1.0.5
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.1
cocoapods-trunk       : 1.6.0
cocoapods-try         : 1.2.0

Podfile

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

workspace 'IotServiceTestApp'

target 'IotServiceTestApp' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for IotServiceTestApp
  pod 'RxSwift'
  pod 'Moya' 
  pod 'XXXX', :path => './../XXXX'

end
@DanijelBojcic
Copy link

I have the same issue.
Did you find a solution?

@falconeta
Copy link

same issue :(

@DanijelBojcic
Copy link

I have spoken with someone from Apple Developer Support, and they said that 'Matter.xcframework' is a reserved name. I have not tried it yet, but I hope I only need to rename the framework, and not its header files.

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

3 participants