I have an error build with firebasex plugin on iOS.
Please describe the issue:
My build IDs
a8ff6262-531f-4450-98bf-1b791c645b7b
52dbb743-b63d-479a-a77f-c4c4480c61d4
319b8fe4-8f40-48fa-9e95-4198ece605fe
I need help with firebasex plugin on IOS.
I tryed to define deployment-target 13, 14, ios engine 5, 6, 7, swift
But get same build error. Can you help me?
The following build commands failed:
ScanDependencies /Users/vagrant/Library/Developer/Xcode/DerivedData/АЗС_Expert-fbivuzmuhxjjjsflapgqchcoioey/Build/Intermediates.noindex/ArchiveIntermediates/АЗС\ Expert/IntermediateBuildFilesPath/АЗС\ Expert.build/Release-iphoneos/АЗС\ Expert.build/Objects-normal/arm64/FirebasePlugin.o /Users/vagrant/voltbuilder/agent/upload/47e75009-c079-40e5-895a-eb441e5370cf/platforms/ios/АЗС\ Expert/Plugins/cordova-plugin-firebasex/FirebasePlugin.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target ‘АЗС Expert’ from project ‘АЗС Expert’)
Archiving workspace АЗС Expert with scheme АЗС Expert
(2 failures)
Command failed with exit code 65: xcodebuild -workspace АЗС Expert.xcworkspace -scheme АЗС Expert -configuration Release -destination generic/platform=iOS -archivePath АЗС Expert.xcarchive archive ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = NO LD_RUNPATH_SEARCH_PATHS = “@executable_path/Frameworks”
OR
UserError: [!] CocoaPods could not find compatible versions for pod “FirebaseInAppMessaging”:
In Podfile:
FirebaseInAppMessaging (= 11.8.0-beta)
I found out the reason. The problem was in the cyrillic name of the application in “name” config.xml . For now, I’ve changed it to the latin and entered the name through the “short” property of the “name” tag. But there is still a need for Cyrillic. When building the application, will you be able to convert Cyrillic characters for the workflow so that the build works and i could set cyrrilyc “name”?
We’ve not seen a problem with this before. Could you share the build ID of the build that succeeded, then change the line in config.xml and try to build again and share that build ID? We’d like to look into this further.