-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlutterFire: IOS simulator not building #13599
Comments
Hi @StaffordInnovations, I'm unable to reproduce this issue. Can you try the solutions here to see if it resolves your issue. |
Hi Selase, I don't seem to have any of those options in my Runner or runner.xcworkspace file when I open it in Xcode. Reset package caches is greyed out. I've cleaned pods/flutter, deleted/reset pods, checked all my updates, reset my computer multiple times after trying all sorts of different variations in my podfile. I am in Flutter so I'm more used to that than Xcode |
Can you create a new flutter project, add |
I was wondering if maybe there was something going on with Flutter eventually moving to the swift package manager?
I made a new Flutter package and the only thing I added was Firebase_core and ended up with the original crash report I had before I figured out there was a package issue I used Translated Report (Full Report Below)Incident Identifier: FD24AC5D-34D0-4994-AFE4-DF0EA659897E Date/Time: 2024-11-01 13:47:43.0242 +0000 Exception Type: EXC_CRASH (SIGABRT) Triggered by Thread: 0 Last Exception Backtrace: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3: Thread 4:: com.apple.uikit.eventfetch-thread Thread 5: Thread 6: Thread 7: Thread 8: Thread 9:: io.flutter.1.ui Thread 10:: io.flutter.1.raster Thread 11:: io.flutter.1.io Thread 12:: io.flutter.1.profiler Thread 13:: io.worker.1 Thread 14:: io.worker.2 Thread 15:: io.worker.3 Thread 16:: io.worker.4 Thread 17:: dart:io EventHandler Thread 18:: Dart Profiler ThreadInterrupter Thread 19:: Dart Profiler SampleBlockProcessor Thread 20:: DartWorker Thread 21:: DartWorker Thread 22:: DartWorker Thread 23:: DartWorker Thread 24: Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 0 Binary Images: EOF Full Report{"app_name":"Runner","timestamp":"2024-11-01 13:47:44.00 +0000","app_version":"1.0.0","slice_uuid":"701168ed-38da-33b1-9b98-c426161c9fda","build_version":"1","platform":7,"bundleID":"com.example.firebasePlay","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 15.0.1 (24A348)","roots_installed":0,"name":"Runner","incident_id":"FD24AC5D-34D0-4994-AFE4-DF0EA659897E"}
], Model: MacBookPro16,1, BootROM 2069.0.0.0.0 (iBridge: 22.16.10353.0.0,0), 8 processors, 8-Core Intel Core i9, 2.3 GHz, 16 GB, SMC |
If I should manually add the ios and android elements from the flutter firebase project I can discard all my changes in git. It might have something to do with the flutter config file. My original thought was a difference in the project id or something like that but then I found the package errors |
I suspect this may be a misconfiguration on your end. Can you create a complete minimal repo with steps to reproduce this issue? Kindly share the link here once you're done. |
My github desktop is having issues uploading at the moment. The steps consist of creating a new flutter app, following the instructions on console.firebase.google.com for "add firebase to your flutter app" using flutterfire configure --project=kohnen2025 adding // ... await Firebase.initializeApp( to main.dart with firebase_core: ^3.6.0 in pubspec.yaml I can try to upload later |
@StaffordInnovations - have you enabled Swift package manager? To disable run: flutter config --no-enable-swift-package-manager Open a new terminal, do usual clean |
didn't help :( technically it should have been disabled since I was on stable and not main but still manually tried turning it off then fully restarted Android Studio and my computer before deleting podfile.lock and doing the clean steps |
Hi Selase please see below for the link to the github package for just a basic flutter app that's not working properly |
Hi @StaffordInnovations, thanks for sharing. I was able to successfully build and launch your project. The crash appears to be caused by an invalid Firebase app name containing spaces (NGT life). You have to use a valid name(NGT_life). Let me know if this resolves your issue. |
Hi Selase, it looks like it's the firebase config tool that ends up causing an issue in my case because of the length of my bundle id. I've actually had the firebase project for a long time so it wasn't the project name, although I went ahead and changed it to a _ instead of a space I had to run instead of
|
Hey @StaffordInnovations , I'm facing the same issue as you and following this thread, it's a bit unclear what the fix was for you. Do you mind sharing? |
Hi Garry, so it was a configuration issue, basically conflict between my firebase project naming and the app. So I would say the first step is to make sure everything matches on your firebase console and the flutter app. Because my app name was longer (ie.staffordinnovations.app) I had to manually do use the flutterfire configure as I mentioned above. This issue was kind of similar maybe it could help? There's always the updating cocoa pods, deleting/reinstalling or the good ole pod cache clean --all followed by flutter clean flutter pub get, |
Hey @StaffordInnovations , thank you for your response! It was definitely a configuration issue, I ended up deleting my iOS folder and re-generated it and it worked fine afterwards :) |
Is there an existing issue for this?
Which plugins are affected?
Core, Analytics, Auth, Cloud Functions, In-App Messaging, Messaging
Which platforms are affected?
iOS
Description
This is similar but not quite to issue #13563 however I've tried the solutions and they're not working for me plus the error reports aren't quite the same.
I expected to add FlutterFire/Firebase_core to my new Flutter app and be able to build on the IOS simulator.
I've already tried a million things.
I took out
use_frameworks! use_modular_headers!
from the target 'Runner' do in my podfile and tried the manual
pod 'Firebase', :modular_headers => true
for each packageI've done the delete podfile.lock, clean cache, clean flutter etc over and over any time I've tried a new solution
doing the following didn't help:
post_install do |installer| installer.pods_project.targets.each do |target| if target.name == 'abseil' target.build_configurations.each do |config| config.build_settings['CLANG_CXX_LANGUAGE_STANDARD'] = 'gnu++14' end end end end
I tried adding the packages to Runner in Xcode but then got conflict there. I took out url_launcher in case that was causing an issue. I'm really at a loss as to how to fix this.
Reproducing the issue
I created a new flutter app in order to refactor an existing app. The app built on both the IOS simulator Iphone 15 (18.0) and android emulator prior to adding flutter core. I used the Flutter config instructions from the Firebase console in order to install Firebase but then I got crash reports. It took me a long time to find it's an issue with the packages.
Firebase Core version
3.6.0
Flutter Version
3.24.4
Relevant Log Output
Flutter dependencies
Expand
Flutter dependencies
snippetAdditional context and comments
I'm wondering if maybe there might be related to the swift package manager or maybe I should migrate to that? I'm currently on Flutter Channel Stable
Doctor summary (to see all details, run flutter doctor -v): [✓] Flutter (Channel stable, 3.24.4, on macOS 15.0.1 24A348 darwin-x64, locale en-IE) [✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc3) [✓] Xcode - develop for iOS and macOS (Xcode 16.1) [✓] Chrome - develop for the web [✓] Android Studio (version 2024.1) [✓] VS Code (version 1.95.0) [✓] Connected device (4 available) [✓] Network resources
The text was updated successfully, but these errors were encountered: