FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
130 stars 26 forks source link

Error deploying from GitHub #4965

Open Sandernijs opened 4 days ago

Sandernijs commented 4 days ago

Can we access your project?

Current Behavior

To be able to add the meta sdk i had to change code by using GitHub. Now i'm trying to deploy this new version to the app store, but i get a error "Failed Step: Flutter build ipa and automatic versioning" (see images). Schermafbeelding 2024-11-23 101522

Schermafbeelding 2024-11-23 101512

Expected Behavior

It should deploy correctly.

Steps to Reproduce

Deploying a new build through GitHub

Reproducible from Blank

Bug Report Code (Required)

not relevant

Visual documentation

Schermafbeelding 2024-11-23 145737 Schermafbeelding 2024-11-23 101522 Schermafbeelding 2024-11-23 101512

Environment

- FlutterFlow version: FlutterFlow v5.0.0+ released November 20, 2024
Flutter version is 3.24.2
- Platform: ios
- Browser name and version: - 
- Operating system and version affected: -

Additional Information

No response

Alezanello commented 3 days ago

It looks like your error log is pointing to some missing Swift symbols during the linking phase of your build. This can happen when certain Swift libraries aren’t properly linked to your project.

Since you’re using the Meta SDK, this is a fairly common issue in Flutter projects that involve Swift dependencies. To resolve this, you can check if the required Swift libraries are added correctly. A good starting point is to:

  1. Ensure Swift is enabled: Open your iOS project in Xcode and confirm that Swift support is set up. If not, you might need to create a dummy Swift file in your project to prompt Xcode to set up a bridging header.
  2. Update your Podfile: Add use_frameworks! and ensure your dependencies are correctly included.
  3. Run pod install: This helps link the necessary libraries.
Sandernijs commented 3 days ago

It looks like your error log is pointing to some missing Swift symbols during the linking phase of your build. This can happen when certain Swift libraries aren’t properly linked to your project.

Since you’re using the Meta SDK, this is a fairly common issue in Flutter projects that involve Swift dependencies. To resolve this, you can check if the required Swift libraries are added correctly. A good starting point is to:

  1. Ensure Swift is enabled: Open your iOS project in Xcode and confirm that Swift support is set up. If not, you might need to create a dummy Swift file in your project to prompt Xcode to set up a bridging header.
  2. Update your Podfile: Add use_frameworks! and ensure your dependencies are correctly included.
  3. Run pod install: This helps link the necessary libraries.

Thank you for the reply, but as a flutterflow user (which is a 'no code' tool this seems impossible to fix. I have no clue how to fix this. Is there a understandable way to fix this? I used this https://community.flutterflow.io/discussions/post/tutorial-add-meta-sdk-to-your-app---step-by-step-tutorial-2sNvqO3yavNJoqk tutorial to add the SDK.

Alezanello commented 3 days ago

Thank you for sharing your concern! I completely understand what you mean. However, the GitHub Issue Tracker is intended solely for reporting bugs that can be replicated within the FlutterFlow platform or issues related to Flutter itself that require fixes. Since this seems more like a custom integration issue, I recommend reaching out to our support team through the in-app chat or by emailing support@flutterflow.io. They’ll be happy to assist you further!

ready4sea commented 3 days ago

Encountering the exact same issue when trying to deploy to App Store tonight.

@Alezanello, your response, while possibly correct, does not really help. In the sense that the whole setup for Flutter and Swift is the one provided by the FlutterFlow. I just exported the code, added the Meta SDK, and then tried to deploy from the GitHub repo.

Also, please note that deploying Android went fine. And that building for iOS locally also went fine (using flutter build ipa). So I guess @Sandernijs here just reported that there seems to be an issue with either FF or the CodeMagic deployement.