'FIRHeartbeatsPayload' for instance message is a forward declaration

[Spatel91111]

Description

Updating latest pods getting this error 'FIRHeartbeatsPayload' for instance message is a forward declaration

Reproducing the issue

No response

Firebase SDK Version

10.25.0

Xcode Version

15.0

Installation Method

CocoaPods

Firebase Product(s)

Analytics, Crashlytics, Messaging, Performance, Remote Config

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[ncooke3]

@Spatel91111 , could you share your Podfile and/or a reproducible example?

[Spatel91111]

Hello @ncooke3

Before I have used as below pods installed

pod 'Firebase/Core', '8.12.1'
pod 'Firebase/Crashlytics', '8.12.1'
pod 'Firebase/Analytics', '10.24.0'
pod 'Firebase/Messaging', '8.12.1'
pod 'Firebase/Performance','8.12.1'
pod 'Firebase/RemoteConfig','8.12.1'

Now update my podfile with below code

pod 'Firebase/Core'
pod 'Firebase/Crashlytics'
pod 'Firebase/Analytics'
pod 'Firebase/Messaging'
pod 'Firebase/Performance'
pod 'Firebase/RemoteConfig'

and pod update command and build project getting above error.

[paulb777]

@Spatel91111 The mix of 8.x and 10.x versions in the first could be problematic. Please also share the resulting Podfile.lock

[google-oss-bot]

Hey @Spatel91111. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@Spatel91111 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.