[iOS 18] Depend on latest firebase_messaging to fix "include of non-modular header inside framework module 'firebase_messaging.FLTFirebaseMessagingPlugin'" error

[dJani97]

Description

I'm getting the following error in my iOS builds using the latest iOS 18 tooling:

Running Xcode build...                                                  
 └─Compiling, linking and signing...                         4.0s
Xcode archive done.                                         104.2s
Failed to build iOS app
Lexical or Preprocessor Issue (Xcode): Include of non-modular header inside framework module 'firebase_messaging.FLTFirebaseMessagingPlugin': '/Users/username/flutter/project-name/ios/Pods/Headers/Public/Firebase/Firebase.h'
/Users/username/.pub-cache/hosted/pub.dev/firebase_messaging-15.1.0/ios/Classes/FLTFirebaseMessagingPlugin.h:11:8

Encountered error while archiving for device.

This is caused by an outdated version of the Firebase Messaging plugin. The latest firebase_messaging: ^15.1.3 fixes this problem, as described in the release notes.

The problem can also be fixed by using the following dependency overrides, but I am yet to test if this introduces any runtime errors, and I do not recommend anyone using this code in a production app:

dependency_overrides:
  firebase_messaging: ^15.1.3
  web: ^1.0.0

Could we please get a new release of amplify_push_notifications_pinpoint that depends on firebase_messaging: ^15.1.3 or newer?

Categories

• Analytics
• API (REST)
• API (GraphQL)
• Auth
• Authenticator
• DataStore
• Notifications (Push)
• Storage

Platforms

• iOS
• Android
• Web
• macOS
• Windows
• Linux

Flutter Version

3.24.3

Amplify Flutter Version

2.4.1

Deployment Method

Amplify Gen 2

[dJani97]

I realized that Amplify does not directly depend on firebase_messaging and something else was the culprit. Closing this issue.

Updating Amplify's web dependency would still be nice though, but that's another issue.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.