Skip to content

Mobile deployment button is blocked by FF due to "errors in your project" even when trying to deploy from a perfectly-working github branch #5759

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

Open
2 tasks done
isegal opened this issue Apr 28, 2025 · 1 comment
Labels
regression status: needs triage A potential issue that has not been confirmed as a bug.

Comments

@isegal
Copy link

isegal commented Apr 28, 2025

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

When pressing deploy, an error is displayed "Cannot deploy due to errors in the project. Please fix and try again." even though the deployment is set to use a github branch. FF has no way of knowing whether the branch is working or contains workarounds, therefore it should never block deployment when the deploy source is set to a github branch.

If flutterflow finds an error in a custom function, even if it's a false-positive error, Flutterflow mobile deployment is blocked at the deploy button level. This makes some workarounds impossible for an artifically-forced reason.

Some errors in FF are not fixable because FF code analysis appears to have a limited visibility. For example, it appears to not know about some types that get generated by Firestore. Although it's perfectly valid code, FF will flag it as an error and block deployment even if the project is perfectly valid.

Expected Behavior

Deploy button should never block especially if the source is set to a github branch.

FlutterFlow error checker appears to have limited visibility and therefore no true way of knowing ahead of time whether there are actual errors in the project, especially when deploying from a github branch.

Even if FF checked was 100% perfect, it still has no way of knowing whether a github branch is valid. Therefore it should not block a deploy when the source is set to a github branch.

There are also cases where FlutterFlow's error detection is incorrect and there are false-positives.

Steps to Reproduce

  1. Set up a project with firestore.
  2. Integrate it with github.
  3. Create a firestore document schema (eg name it products) give it a field - it does not matter what fields you create. In this example we have a field called title
  4. Create a custom function that returns the document (NOTE: Not a reference).Eg:
List<ProductsRecord> createPlaceholderProduct(
) {

    final placeholderData = createProductsRecordData(
      title: "Placeholder",
    );
    final reference = FirebaseFirestore.instance.collection('products').doc();
    return ProductsRecord.getDocumentFromData(placeholderData, reference);
}
  1. Check the functions for errors
  2. Push the project to github.
  3. Build the project locally.
  4. Set deployment source to be github. Attempt to deploy using mobile deployment button from FlutterFlow.
  • Flutterflow will erroneously report that createProductsRecordData is not defined (it actually is!).
  • Flutterflow will falsely report that getDocumentFromData is not defined (it also is).
  • This happens even if Project will build locally.

Reproducible from Blank

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

Bug Report Code (Required)

IT40hcnfz5Fgod9c1rrUK/lahmU5JlN9RI0Nke57aCgofePtOol3evWkVBBVYMylS29EOESmmlwx+aHOudntCu0oZEirRphczJBidjvhXlK6UZOBBs2WbX98HZ5hCnXD4bbQsBB4GPB2c1oFw12MGeqQdDLYN7WxImdISq/LZO4=

Visual documentation

Image

Environment

- FlutterFlow version: 
FlutterFlow v5.4.4 released April 22, 2025


- Platform: Likely all, but we tested Android mobile deployment button.
- Browser name and version: Chrome
- Operating system and version affected: All

Additional Information

This appears to be some kind of regression, as we were able to deploy with this false-positive error a while ago.

@isegal isegal added the status: needs triage A potential issue that has not been confirmed as a bug. label Apr 28, 2025
@Juansarmi Juansarmi self-assigned this Apr 29, 2025
Copy link
Collaborator

Hi,
Sorry to hear you're experiencing this issue. This bug has been reported before and appears to be related to a regression.
I’ll forward this case to the appropriate team for further investigation and will keep you updated on any developments.

Best regards

@Juansarmi Juansarmi added the regression label Apr 29, 2025 — with Linear
@Juansarmi Juansarmi removed their assignment Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression status: needs triage A potential issue that has not been confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants