FF keeps overriding with it's own code during local run - OneSignal Flutter SDK Integration

Troubleshooting

I installed the Flutter SDK for OneSignal (thought this would be easy...) adding ImageNotification as a target has been a nightmare. I've removed every trace of both OneSignal and ImageNotification from Xcode and FF, but every time I do a local run, it is pulling from something and completely rebuilds all the old ImageNotification code and files.

The project had multiple compounding issues:

1. Signing Issues โ€“ ImageNotification target is missing a development team.

2. Dependency Conflicts โ€“ flutter_test and collection version mismatch.

3. CocoaPods Issues โ€“ Duplicate post_install hooks, overridden settings, missing xcconfig files.

4. Missing Entitlements โ€“ App crashes due to missing permissions for notifications/authentication.

Link: https://documentation.onesignal.com/docs/flutter-sdk-setup?_gl=1*12xhk7v*_gcl_au*MTExODczNDA2Mi4xNzQwOTc1Mzcw*_ga*MTM0Mjc1Mjc1LjE3NDA5NzUzNjg.*_ga_Z6LSTXWLPN*MTc0MDk3NTM2OC4xLjEuMTc0MDk3NzE1NC42MC4wLjY5OTY2NjA0Nw..



Anyone have this error and know a solution?

What have you tried so far?

-Removed all trace of dependencies

Re-install cocoapods

-Checked for OneSignal in pubspec.yaml โ€“ Confirmed it was not present.

-Ran flutter pub get โ€“ Faced dependency resolution issues with collection version.

-Checked iOS Podfile โ€“ Found duplicate post_install hooks and fixed it.

-Ran pod install --repo-update โ€“ Encountered CocoaPods warnings about overridden settings.

-Checked Xcode Build Settings โ€“ Verified framework search paths and header search paths.

-Checked Signing & Capabilities in Xcode โ€“ Found missing development team selection.

-Attempted to run the app in Xcode โ€“ Encountered SIGKILL crash, likely due to entitlements or missing frameworks.

-Examined Xcode logs & debugger output โ€“ Identified readClass crash, possibly related to missing authentication entitlements.

-Verified Provisioning Profile & Push Notification Settings โ€“ Found issues with signing for ImageNotification.

Error:

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target Runner to Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig or include the Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig in your build configuration (`Flutter/Release.xcconfig`).

[!] The Runner [Debug] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The Runner [Release] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The Runner [Profile] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The ImageNotification [Debug] target overrides the CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER build setting defined in `Pods/Target Support Files/Pods-ImageNotification/Pods-ImageNotification.debug.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The ImageNotification [Release] target overrides the CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER build setting defined in `Pods/Target Support Files/Pods-ImageNotification/Pods-ImageNotification.release.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The ImageNotification [Profile] target overrides the CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER build setting defined in `Pods/Target Support Files/Pods-ImageNotification/Pods-ImageNotification.profile.xcconfig'. This can lead to problems with the CocoaPods installation

Did you check FlutterFlow's Documentation for this topic?
Yes
2