Undefined symbol: filament::uberz::ArchiveCache::* when building iOS project with CocoaPods on 1.23.2 release

[azhong-git]

Describe the bug
I came across the following link error when I use gltfio::createUbershaderLoader() in an iOS CocoaPod Project. This issue seems to only happen on v1.23.2.

To Reproduce
Steps to reproduce the behavior:

1. git checkout v1.23.2
2. cd ios/samples/HelloCocoaPods and create Podfile with the following 3.

platform :ios, '11.0'

target 'HelloCocoaPods' do
    pod 'Filament'
end

3. pod install and open HelloCocoaPods.xcworkspace with xcode
4. Use gltfio::createUbershaderLoader in code, for example like below

diff --git a/ios/samples/HelloCocoaPods/HelloCocoaPods/ViewController.mm b/ios/samples/HelloCocoaPods/HelloCocoaPods/ViewController.mm
index 42796f6e1..b85109eb0 100644
--- a/ios/samples/HelloCocoaPods/HelloCocoaPods/ViewController.mm
+++ b/ios/samples/HelloCocoaPods/HelloCocoaPods/ViewController.mm
@@ -39,6 +39,8 @@
 
 #include <filamat/MaterialBuilder.h>
 
+#include <gltfio/AssetLoader.h>
+
 #include <utils/Entity.h>
 #include <utils/EntityManager.h>
 
@@ -77,6 +79,10 @@ - (void)viewDidLoad {
     // Create an Engine, the main entry point into Filament.
     _engine = Engine::create(Engine::Backend::METAL);
 
+    gltfio::MaterialProvider* materialProvider = gltfio::createUbershaderLoader(_engine);
+    // gltfio::AssetLoader* assetLoader = gltfio::AssetLoader::create({
+        _engine, materialProvider, nullptr});

5. Build the project

Expected behavior
Should link and build with no error.

Logs

Undefined symbol: filament::uberz::ArchiveCache::getMaterial(filament::uberz::ArchiveRequirements const&)
Undefined symbol: filament::uberz::ArchiveCache::destroyMaterials()
Undefined symbol: filament::uberz::ArchiveCache::getDefaultMaterial()
Undefined symbol: filament::uberz::ArchiveCache::~ArchiveCache()
Undefined symbol: filament::uberz::ArchiveCache::load(void const*, unsigned long long)

Desktop (please complete the following information):
MacOS, XCode 13.4.1

[bejado]

Sorry for the trouble, this will be fixed with the v1.23.3 release.