[REQUIRED] Please fill in the following fields:
- Unity editor version: 2020.3.26f1
- Firebase Unity SDK version: 9.0.0
- Source you installed the SDK: packages from official site
- Problematic Firebase Component: Building overall
- Other Firebase Components in use: Analytics, Auth, Crashlytics, DynamicLinks, Messaging, RemoteConfig
- Additional SDKs you are using: Facebook, AdMob
- Platform you are using the Unity editor on: Mac
- Platform you are targeting: iOS
- Scripting Runtime: IL2CPP
- Pre-built SDK from the website
[REQUIRED] Please describe the issue here:
Everything started with AdMob update and its Mediators, which usually involves Firebase update too. Right after AdMob update - iOS build still produced file (although app was crashing right on start) so attempted to update Firebase to 9.0.0 or later, but now can’t get iOS to build… Had some issues with Android too, but updating gradle (was used custom one before as project drags from unity 2019, just replaced with unity included now) and bumping minSDK version to 31 everything builds and plays with no issues there. Still iOS just won’t build - updated xCode to 13.3.1 now can’t get the build to work, and as android build works, it seems I’m missing some build configuration or smth - what are recommended options for IOSResolver? these are settings that are in use now… and failing
Google.IOSResolver.PodfileGenerationEnabled = true;
Google.IOSResolver.CocoapodsIntegrationMethodPref = Google.IOSResolver.CocoapodsIntegrationMethod.Project;
Google.IOSResolver.PodToolExecutionViaShellEnabled = true;
Google.IOSResolver.AutoPodToolInstallInEditorEnabled = true;
Google.IOSResolver.VerboseLoggingEnabled = false;
Google.IOSResolver.UseProjectSettings = true;
Google.IOSResolver.PodfileAddUseFrameworks = true;
Google.IOSResolver.PodfileAllowPodsInMultipleTargets = true;
Google.IOSResolver.PodfileAlwaysAddMainTarget = true;
Google.IOSResolver.PodfileStaticLinkFrameworks = true;
Google.IOSResolver.SwiftFrameworkSupportWorkaroundEnabled = true;
Google.IOSResolver.SwiftLanguageVersion = "5.0";
Google.IOSResolver.PodToolShellExecutionSetLang = true;
and before update was used
Google.IOSResolver.PodfileGenerationEnabled = true;
Google.IOSResolver.CocoapodsIntegrationMethodPref = Google.IOSResolver.CocoapodsIntegrationMethod.Project;
Google.IOSResolver.PodToolExecutionViaShellEnabled = true;
Google.IOSResolver.AutoPodToolInstallInEditorEnabled = true;
Google.IOSResolver.VerboseLoggingEnabled = false;
Google.IOSResolver.UseProjectSettings = true;
Google.IOSResolver.PodfileAddUseFrameworks = false;
Google.IOSResolver.PodfileAllowPodsInMultipleTargets = true;
Google.IOSResolver.PodfileAlwaysAddMainTarget = false;
Google.IOSResolver.PodfileStaticLinkFrameworks = false;
right after update was having these on buildmachine logs:
The Swift pod
FirebaseCoreInternaldepends upon
GoogleUtilities, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set
use_modular_headers!globally in your Podfile, or specify
:modular_headers => true for particular dependencies.
so tried to add manually
<iosPod name="GoogleUtilities" version="7.7.0" modular_headers="true">
but although pods were installed, that was causing more issues down the line (on every imported firebase package)
FirebaseCore/Extension/FirebaseCoreInternal.h:15:9: fatal error: module 'FirebaseCore' not found
@import FirebaseCore;
so after xCode update, adding static links and swift framework pods do install, now having these errors on build for every referenced pod:
Build_iOS/Pods/___.entitlements" could not be opened. Verify the value of the CODE_SIGN_ENTITLEMENTS build setting for target "___" is correct and that the file exists on disk. (in target '___' from project 'Pods')
whole thing is that entitlements are correct and placed on root Build_iOS folder, not within Pods - I’m not familiar with such referencing and even tried to manually copy file there, but it didn’t helped
Feels like I’m missing something obvious, but can’t figure it out yet
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top GitHub Comments
Hi @paulinon Having an update: all my issues were because of the
use_framwworks!
key By default it wasn’t used (was stripped in postbuild) and after the update showed thatGoogleUtilities
dependency issue. After enabling it started to show that issue with the build command parameters mentioned in previous message. And on initial report I was really close to solution, which is to include both pods with modular headers in addition topod 'Firebase/Core', '9.3.0'
alsonow it builds again
Glad to hear that you’re able to build your app again, @vwormsbecherJC.
I’ll be closing this for now. Let me know if an issue arises.