Xcode Archive fails with missing GoogleUtilities/GULHeartbeatDateStorage.h on Bitrise

TL;DR

Delete the Pods directory and reinstall. The Pods install on the build machine had a stale or conflicting state, likely from a cache restore mixing pod versions.

Steps

1. A React Native iOS build on Bitrise fails during the Xcode Archive and Export step with a compile error saying GoogleUtilities/GULHeartbeatDateStorage.h cannot be found, in the Firebase CoreDiagnostics source. The Pods install on the build machine had a stale or conflicting state, likely from a cache restore mixing pod versions. Local builds worked because the local Pods directory was clean.
2. Delete the Pods directory and reinstall. Running rm -rf Pods/ before the pod install cleared the cached conflict and the archive step passed. The reporter confirmed the build succeeded after doing this.

When to use

You are seeing this: A React Native iOS build on Bitrise fails during the Xcode Archive and Export step with a compile error saying GoogleUtilities/GULHeartbeatDateStorage.h cannot be found, in the Firebase CoreDiagnostics source. Use this skill when you run into "Xcode Archive fails with missing GoogleUtilities/GULHeartbeatDateStorage.h on Bitrise".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/bitrise-io/bitrise/issues/730

In the thread, the asker reported: A React Native iOS build on Bitrise fails during the Xcode Archive and Export step with a compile error saying GoogleUtilities/GULHeartbeatDateStorage.h cannot be found, in the Firebase CoreDiagnostics source. The Pods install on the build machine had a stale or conflicting state, likely from a cache restore mixing pod versions. Local builds worked because the local Pods directory was clean. The verified answer that resolved it: Delete the Pods directory and reinstall. Running rm -rf Pods/ before the pod install cleared the cached conflict and the archive step passed. The reporter confirmed the build succeeded after doing this.

Source: https://github.com/bitrise-io/bitrise/issues/730 Thread: https://vectle.com/threads/thr_V6ief7uCix0dJzE2aYfZEg