"ITMS-90426: Invalid Swift Support"
Closed this issue · 8 comments
Description
as use only c++ and cmake, including firebase ios sdk requires to also include Swift language support into cmake.
which I did, and I can build and deploy the app just fine.
However when uploading generaed app to TestFlight / AppStore it gives me following error:
when I open generated *.app to check, it realy does not contain SwiftSupport folder.
So I guess I need to tell Cmake to require generating this folder upon build?
cmakes generate xproject which I open in xcode to build...
In the documentations neither examples I found anything how can I influence this from Cmake, neither directly set in xcode.
same/similar question unaswered here firebase/firebase-ios-sdk#10006
Reproducing the issue
No response
Firebase SDK Version
11.3
Xcode Version
16.0.1
Installation Method
N/A
Firebase Product(s)
Analytics, Messaging
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
No response
If using CocoaPods, the project's Podfile.lock
No response
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
I found a few problems with this issue:
- I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
- This issue does not seem to follow the issue template. Make sure you provide all the required information.
Transferred to the firebase-cpp-sdk repo to investigate how to apply the guidance from firebase/firebase-ios-sdk#10006 to C++ and cmake.
thank you, however i still think its pure ios sdk issue, as this happens only when to c++ project load swift stuff... which happens only in firebase ios sdk :)
The solution for the pure iOS issue is described in firebase/firebase-ios-sdk#10006. it sounds like you need additional help for a C++ context.
I dont see any solution there... theoretical solution was to include swift file which I already did with no success, and this was also mentioned by @ndahlquist that he did and didnt help. "contains embedded Swift" also can say didnt help me neither for that topic. No other solution was proposed there yet