Skip to content

iOS build fails at link step , Undefined symbol: _OBJC_CLASS_$_CMMotionManager (CoreMotion not linked in generated Podfile) #7233

Description

@muhammadtaha211

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

iOS App Store deployment fails at the "Flutter build ipa and automatic versioning" step. The project compiles and the Xcode archive completes, then the LINKER fails:

Failed to build iOS app
Error (Xcode): Undefined symbol: OBJC_CLASS$_CMMotionManager
Error (Xcode): Linker command failed with exit code 1
Encountered error while archiving for device.

CMMotionManager is from Apple's CoreMotion framework. The undefined symbol means CoreMotion.framework is not being linked into the Runner target by the generated Podfile, even though a bundled native dependency references it.

This is NOT project-specific - multiple users report the identical error on different apps:

My project does NOT use google_maps_flutter, local_auth, geolocator, sensors_plus, or google_mobile_ads (confirmed in App Settings → Project Dependencies). The CoreMotion reference comes from a transitive native dependency of the core stack - most likely the reCAPTCHA Enterprise SDK pulled in by firebase_auth for iOS phone-auth verification - which cannot be removed without breaking core functionality.

Expected Behavior

The generated iOS build should link CoreMotion.framework so the archive succeeds. Please add CoreMotion to the linked frameworks in the generated Podfile (post_install hook or the Runner target), or pin the offending transitive dependency to a version that links it correctly.

Steps to Reproduce

  1. Project using firebase_auth with Firebase phone authentication, deployed to the App Store via FlutterFlow's build pipeline.
  2. Trigger the iOS App Store build.
  3. Build fails at the linker with the CoreMotion error above. Already confirmed on the latest FlutterFlow version after a clean rebuild.

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4klcr15Y1gocNf7arLbexGoGU4OVw5TLJEpu0bWUkbGO/4OrMIZuDRZRJCcNyzaH9mB079ij8zpdbOiN+WU/kEZEydRohC+c55WxPPYzqhacTQBc6oYUBQO/pbGlS438OV3QlQPftsSlku2mGAO+uUaz6Cf9qOYwx5e6fDbOY=

Visual documentation

Image Image

Here is the list of Flutterflow pub dependencies in my project:

auto_size_text: 3.0.0
cached_network_image: 3.4.1
cached_network_image_platform_interface: 4.1.1
cached_network_image_web: 1.3.1
collection: 1.19.1
cross_file: 0.3.5+1
csslib: 1.0.2
dropdown_button2: git
easy_debounce: 2.0.1
equatable: 2.0.7
file_picker: 10.1.9
firebase_auth: 5.6.0
firebase_auth_platform_interface: 7.7.0
firebase_auth_web: 5.16.0
firebase_core: 3.14.0
firebase_core_platform_interface: 5.4.0
firebase_core_web: 2.23.0
firebase_performance: 0.10.1+7
firebase_performance_platform_interface: 0.1.6+7
firebase_performance_web: 0.1.7+13
flutter_animate: 4.5.0
flutter_blurhash: 0.9.1
flutter_cache_manager: 3.4.1
flutter_credit_card: git
flutter_google_places: git
flutter_plugin_android_lifecycle: 2.0.28
flutter_svg: 2.1.0
font_awesome_flutter: 10.7.0
from_css_color: 2.0.0
go_router: 12.1.3
google_api_headers: 4.5.3
google_fonts: 6.3.3
google_sign_in: 6.3.0
google_sign_in_android: 6.2.1
google_sign_in_ios: 5.9.0
google_sign_in_platform_interface: 2.5.0
google_sign_in_web: 0.12.4+4
html: 0.16.6
http: 1.4.0
image_picker: 1.1.2
image_picker_android: 0.8.12+23
image_picker_for_web: 3.0.6
image_picker_ios: 0.8.12+2
image_picker_linux: 0.2.1+2
image_picker_macos: 0.2.1+2
image_picker_platform_interface: 2.10.1
image_picker_windows: 0.2.1+1
intl: 0.20.2
json_path: 0.7.2
lottie: 3.1.2
mime_type: 1.0.0
octo_image: 2.1.0
package_info_plus: 8.0.2
package_info_plus_platform_interface: 3.0.1
page_transition: 2.1.0
path_provider: 2.1.4
path_provider_android: 2.2.10
path_provider_foundation: 2.4.0
path_provider_linux: 2.2.1
path_provider_platform_interface: 2.1.2
path_provider_windows: 2.3.0
percent_indicator: 4.2.2
photo_view: 0.15.0
plugin_platform_interface: 2.1.8
provider: 6.1.5
rxdart: 0.27.7
shared_preferences: 2.5.3
shared_preferences_android: 2.4.10
shared_preferences_foundation: 2.5.4
shared_preferences_linux: 2.4.1
shared_preferences_platform_interface: 2.4.1
shared_preferences_web: 2.4.3
shared_preferences_windows: 2.4.1
sign_in_with_apple: 7.0.1
sign_in_with_apple_platform_interface: 2.0.0
sign_in_with_apple_web: 3.0.0
sqflite: 2.3.3+1
sqflite_common: 2.5.4+3
stop_watch_timer: 3.0.2
timeago: 3.7.1
url_launcher: 6.3.1
url_launcher_android: 6.3.16
url_launcher_ios: 6.3.3
url_launcher_linux: 3.2.1
url_launcher_macos: 3.2.2
url_launcher_platform_interface: 2.3.2
url_launcher_web: 2.4.1
url_launcher_windows: 3.1.4
video_player: 2.10.0
video_player_android: 2.8.7
video_player_avfoundation: 2.7.1
video_player_platform_interface: 6.3.0
video_player_web: 2.3.6

Note: no google_maps_flutter, local_auth, geolocator, sensors_plus, or google_mobile_ads in this list - none of the usual CoreMotion-linking packages are present, which points to the CoreMotion reference coming from a transitive native dependency (likely reCAPTCHA via firebase_auth phone auth) rather than anything removable in my project.

Environment

- FlutterFlow version: 7.0.13
- Platform: iOS (App Store build via FlutterFlow's build pipeline)
- Browser name and version: Google Chrome 149.0.7827.116
- Operating system and version affected: iOS (target build). Building from Windows 10 via FlutterFlow web - note the build runs on FlutterFlow's cloud macOS, so the host OS isn't the factor.

Additional Information

This is fully blocking my App Store launch. My Android version is already submitted and under review on Google Play; the iOS build is the only thing standing between me and shipping, and it fails 100% of the time at the linker step.

I'm a solo founder on a no-code FlutterFlow build, so I can't edit the Podfile or add a framework manually , the fix has to come from FlutterFlow's generated iOS build. I've already confirmed I'm on the latest FlutterFlow version and rebuilt (same failure), and reviewed the entire Pub Dependencies list , no removable package accounts for the CoreMotion reference, so there's nothing on my end to disable.

Since this same error is hitting multiple other users (links in Current Behavior), I believe it's a build-template issue affecting many projects, not specific to mine. Adding CoreMotion.framework to the linked frameworks would unblock all of us.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions