FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
124 stars 25 forks source link

Deployment Failing Since October 22 Update #4449

Open cartworthy opened 1 week ago

cartworthy commented 1 week ago

Can we access your project?

Current Behavior

Deployment is failing to the App Store. The error recommends downgrading the version of two dependencies but those versions also fail to deploy (along with any other version attempted).

Screenshot 2024-10-22 at 4 46 18 PM

After downgrading, I get this error:

Screenshot 2024-10-22 at 12 24 02 PM

Expected Behavior

I would expect to be able to deploy to the App Store — and for the error output recommendations to work but they do not.

Steps to Reproduce

  1. Click "Deploy"
  2. Wait a few minutes and observe Failed Logs

Reproducible from Blank

Bug Report Code (Required)

-

Visual documentation

Screenshot 2024-10-22 at 4 46 18 PM

^ The first error

Screenshot 2024-10-22 at 12 24 02 PM

^ The error I get after downgrading versions according to the previous errors recommendation.

Environment

- FlutterFlow version: 5.0.8+
- Platform: Mac (Desktop app or web both with the latest update)
- Browser name and version: Chrome
- Operating system and version affected: Mac

Additional Information

I am feeling incredibly stressed because my app is a camera app that depends heavily on the camera functionality and this error has completely halted my progress. I've wasted this entire day hoping to find a solution on my own. I'm also not a developer so if this dependency issue isn't able to be resolved easily I'll have no idea how to fix it.

paulperez-dev commented 1 week ago

Hi @cartworthy,

Could you please try upgrading the camerawesome dependency to its latest version and let us know if that resolves the issue?

Thanks!

chicacode commented 1 week ago

### FlutterFlow v5.0.8 + released October 22 2024 + Flutter 3.24.2 Package Upgrades - Failed App Deployment on App Store & Play Store.

After upgrading FlutterFlow to version 5.0.8 and Flutter to version 3.24.2, I encountered issues while deploying my app to both the App Store and Play Store. The recent changes in Flutter and package upgrades seem to be causing compatibility or build-related problems, preventing successful deployments. These issues were not present prior to the upgrade.

Environment:

FlutterFlow Version: 5.0.8 Flutter Version: 3.24.2 Target Platforms: iOS (App Store) & Android (Play Store) Package Manager: pubspec.yaml Issue Occurred On: Build and Deploy

Steps to Reproduce:

Upgrade FlutterFlow to version 5.0.8 and Flutter to version 3.24.2. Implement the changes in an existing project or create a new one. Try to deploy the app to the App Store or Play Store. Observe build or deployment failures many times since yesterday.

Expected Behavior: The app should build and deploy successfully to both the App Store and Play Store without errors.

Actual Behavior: The app fails to build or is rejected during deployment, either due to compatibility issues with Flutter packages or unhandled exceptions in the latest upgrade.

Error Logs/Output

Failed Step: Install pods

┌─────────────────────────────────────────────────────────┐ │ A new version of Flutter is available! │ │ │ │ To update to the latest version, run "flutter upgrade". │ └─────────────────────────────────────────────────────────┘

╔════════════════════════════════════════════════════════════════════════════╗ ║ Welcome to Flutter! - https://flutter.dev ║ ║ ║ ║ The Flutter tool uses Google Analytics to anonymously report feature usage ║ ║ statistics and basic crash reports. This data is used to help improve ║ ║ Flutter tools over time. ║ ║ ║ ║ Flutter tool analytics are not sent on the very first run. To disable ║ ║ reporting, type 'flutter config --no-analytics'. To display the current ║ ║ setting, type 'flutter config'. If you opt out of analytics, an opt-out ║ ║ event will be sent, and then no further information will be sent by the ║ ║ Flutter tool. ║ ║ ║ ║ By downloading the Flutter SDK, you agree to the Google Terms of Service. ║ ║ The Google Privacy Policy describes how data is handled in this service. ║ ║ ║ ║ Moreover, Flutter includes the Dart SDK, which may send usage metrics and ║ ║ crash reports to Google. ║ ║ ║ ║ Read about data we send with crash reports: ║ ║ https://flutter.dev/to/crash-reporting ║ ║ ║ ║ See Google's privacy policy: ║ ║ https://policies.google.com/privacy ║ ║ ║ ║ To disable animations in this tool, use ║ ║ 'flutter config --no-cli-animations'. ║ ╚════════════════════════════════════════════════════════════════════════════╝

Resolving dependencies... Because vivi depends on flutter_web_plugins any which doesn't exist (could not find package flutter_web_plugins at https://pub.dev), version solving failed.

Build failed :| Step 6 script Install pods exited with status code 69

Potential Causes:

Compatibility issues between new package versions and Flutter 3.24.2. Build script changes introduced in the recent FlutterFlow upgrade. Additional Notes:

This issue is affecting both iOS and Android platforms. Reverting to the previous versions of FlutterFlow and Flutter resolves the issue. Screenshot 2024-10-23 at 8 11 57 AM Screenshot 2024-10-23 at 9 02 37 AM

rzambroni commented 1 week ago

Hey @chicacode, that's a different issue, it has been resolved and it should now be fixed according to the original ticket status.

cartworthy commented 1 week ago

@paulperez-dev I have tried updating the CamerAwesome package to the latest version 2.1.0.

Deploying with the latest 2.1.0 version results in this error:

Screenshot 2024-10-23 at 12 40 12 PM

There's also a migration guide for upgrading to camerAwesome 1.X.X to 2.X.X. I'm guessing my code won't work with the latest version. I was using 1.4.0 before.

For reference, I am not a developer. I pay for FlutterFlow Pro because I am not a developer and I like the platforms ease of accessibility for non-technical people, while also being scalable with custom coding. It is frustrating running into these errors because of updates to the platform that I didn't accept or ask for. I am hoping this is something that can be solved without hiring more developers.

chicacode commented 1 week ago

Hey @chicacode, that's a different issue, it has been resolved and it should now be fixed according to the original ticket status.

No, it is not fixed. I still have the issue I cannot deploy the app in App Store or Play Store

agreaves commented 1 week ago

@chicacode, do you still face the same issue? The fix for the issue you encountered has been deployed, so wondering if it's fixed for you or if you're running into another issue now. If there's still an issue, please provide a Bug Report Code to help us debug! Thanks.

cartworthy commented 1 week ago

@agreaves Hi Alex, can I get an update on my issue? 🙏

DevKursat commented 4 days ago

I get this error when distributing my app on the App Store but I haven't had any issues with the Play Store. @agreaves

Failed Step: Install pods

┌─────────────────────────────────────────────────────────┐ │ A new version of Flutter is available! │ │ │ │ To update to the latest version, run "flutter upgrade". │ └─────────────────────────────────────────────────────────┘

╔════════════════════════════════════════════════════════════════════════════╗ ║ Welcome to Flutter! - https://flutter.dev ║ ║ ║ ║ The Flutter tool uses Google Analytics to anonymously report feature usage ║ ║ statistics and basic crash reports. This data is used to help improve ║ ║ Flutter tools over time. ║ ║ ║ ║ Flutter tool analytics are not sent on the very first run. To disable ║ ║ reporting, type 'flutter config --no-analytics'. To display the current ║ ║ setting, type 'flutter config'. If you opt out of analytics, an opt-out ║ ║ event will be sent, and then no further information will be sent by the ║ ║ Flutter tool. ║ ║ ║ ║ By downloading the Flutter SDK, you agree to the Google Terms of Service. ║ ║ The Google Privacy Policy describes how data is handled in this service. ║ ║ ║ ║ Moreover, Flutter includes the Dart SDK, which may send usage metrics and ║ ║ crash reports to Google. ║ ║ ║ ║ Read about data we send with crash reports: ║ ║ https://flutter.dev/to/crash-reporting ║ ║ ║ ║ See Google's privacy policy: ║ ║ https://policies.google.com/privacy ║ ║ ║ ║ To disable animations in this tool, use ║ ║ 'flutter config --no-cli-animations'. ║ ╚════════════════════════════════════════════════════════════════════════════╝

Resolving dependencies... Downloading packages...

CocoaPods 1.15.0 is available. To update use: gem install cocoapods

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.15.0

[!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: Firebase/Messaging

firebase_messaging (from `.symlinks/plugins/firebase_messaging/ios`) was resolved to 15.1.3, which depends on
  Firebase/Messaging (= 11.2.0)

CocoaPods could not find compatible versions for pod "FirebaseCore": In Podfile: firebase_core (from .symlinks/plugins/firebase_core/ios) was resolved to 3.6.0, which depends on Firebase/CoreOnly (= 11.2.0) was resolved to 11.2.0, which depends on FirebaseCore (= 11.2.0)

firebase_storage (from `.symlinks/plugins/firebase_storage/ios`) was resolved to 12.3.2, which depends on
  Firebase/Storage (= 11.2.0) was resolved to 11.2.0, which depends on
    FirebaseStorage (~> 11.2.0) was resolved to 11.2.0, which depends on
      FirebaseCore (~> 11.0)

CocoaPods could not find compatible versions for pod "GTMSessionFetcher/Core": In Podfile: firebase_storage (from .symlinks/plugins/firebase_storage/ios) was resolved to 12.3.2, which depends on Firebase/Storage (= 11.2.0) was resolved to 11.2.0, which depends on FirebaseStorage (~> 11.2.0) was resolved to 11.2.0, which depends on GTMSessionFetcher/Core (~> 3.4)

google_sign_in_ios (from `.symlinks/plugins/google_sign_in_ios/darwin`) was resolved to 0.0.1, which depends on
  GTMSessionFetcher (>= 3.4.0) was resolved to 4.0.0, which depends on
    GTMSessionFetcher/Full (= 4.0.0) was resolved to 4.0.0, which depends on
      GTMSessionFetcher/Core (= 4.0.0)

google_sign_in_ios (from `.symlinks/plugins/google_sign_in_ios/darwin`) was resolved to 0.0.1, which depends on
  GoogleSignIn (~> 7.1) was resolved to 7.1.0, which depends on
    GTMAppAuth (< 5.0, >= 4.1.1) was resolved to 4.1.1, which depends on
      GTMSessionFetcher/Core (< 4.0, >= 3.3)

google_sign_in_ios (from `.symlinks/plugins/google_sign_in_ios/darwin`) was resolved to 0.0.1, which depends on
  GoogleSignIn (~> 7.1) was resolved to 7.1.0, which depends on
    GTMSessionFetcher/Core (~> 3.3)

CocoaPods could not find compatible versions for pod "nanopb": In Podfile: FirebaseFirestore (from https://github.com/invertase/firestore-ios-sdk-frameworks.git, tag 11.2.0) was resolved to 11.2.0, which depends on FirebaseFirestoreBinary (= 11.2.0) was resolved to 11.2.0, which depends on FirebaseFirestoreInternalBinary (= 11.2.0) was resolved to 11.2.0, which depends on nanopb (~> 3.30910.0)

google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`) was resolved to 1.0.0, which depends on
  Google-Mobile-Ads-SDK (~> 10.11.0) was resolved to 10.11.0, which depends on
    GoogleAppMeasurement (< 11.0, >= 7.0) was resolved to 7.3.0, which depends on
      nanopb (~> 2.30906.0)

Build failed :| Step 6 script Install pods exited with status code 1

Alezanello commented 4 days ago

Hello everyone!

To help us identify the issue more efficiently, could you please share a Bug Report Code from your project? This will assist us in debugging the dependency issues specific to your setup

cartworthy commented 4 days ago

@Alezanello I have provided all of the relevant deployment errors with descriptions above. What is a "Bug Report Code"? I am not a developer so please elaborate on how I can best help you help me.

Alezanello commented 4 days ago

To obtain the Bug Report Code, follow these steps:

  1. Open any page in your project.
  2. Go to the Widget Tree.
  3. Right-click on the Scaffold widget to open the menu.
  4. Select Bug Report Code from the menu.
  5. Wait for the confirmation that the code has been copied to your clipboard.
image.png
cartworthy commented 4 days ago

@Alezanello Does this look right?

ITFfhvHlz4xOocsA7q6IYPlsiiEWHDIcTIMziNZ+exUbfaL1BuwcOsz7VBRDTcvhaVNcPlejoE010639ktrmUccrFz6qbNlHyZdQFgzke2iQM4yUBpCWX3FtN51PIGKw5ruR2BJNPftoWF0jw0OYG+ysYBLDFOu/Zwh9f6PHaOI=

Alezanello commented 4 days ago

Perfect!!

Yes this is it!

Thank you!

Alezanello commented 4 days ago

@cartworthy

If I have this packages is going to throw error:

image.png

If I downgrade camerawesome to 1.1.0 and leave carousel_slider in 5.0.0 it should compile without any issues:

image.png
cartworthy commented 4 days ago

@Alezanello I'm pretty sure I've tried that combination last week and it still didn't work but I just attempted to build it again just to get you the exact errors but building timed out after about an hour:

Screenshot 2024-10-28 at 1 36 47 PM
cartworthy commented 3 days ago

@Alezanello Here's the error. Second build failed with this error.

Screenshot 2024-10-28 at 3 43 19 PM

The code has a green check like it's compiling correctly, but there are red marks throughout the code for padding, alignment, and buttons:

Screenshot 2024-10-28 at 3 46 24 PM

I hired a developer to build this. I'm hoping there is some solution here that does not require hiring another developer to fix this code just because FlutterFlow pushed an update.

Also — I'm a bit disappointed that because FlutterFlow pushed an "update" I have to downgrade packages in my app. That doesn't seem right, does it?

Ideally I would like to be using more recent version of the packages in my app.

mtruebe commented 3 days ago

Hi, also having the same issue "ios/Runner/AppDelegate.swift uses the deprecated @UlApplication Main attribute, updating."

Alezanello commented 3 days ago

Hello @cartworthy,

First, I apologize for the issues you're experiencing with your project. We previously notified users about the update to Flutter version 3.24.2, which also brought updates to several SDK packages and dependencies used in projects.

In your project, you’re using the Carousel Slider package in the "Buy Points," "Profile," and "Image Loader" pages. This package now requires an update to version 5.0.0 to remain compatible with other FlutterFlow widgets. However, updating the Carousel Slider package also requires updating the rxdart package, which the Carousel depends on. Unfortunately, the other package you are implementing requires an older version of rxdart, creating a compatibility issue.

To resolve this, you have two options:

  1. Remove the Carousel Slider from your project and replace it with another component, such as PageView, to achieve a similar functionality.
  2. Update the custom widget code to ensure compatibility with Carousel version 5.0.0, including adjustments for any dependencies.

Let us know if you need further assistance with implementing these changes, and we’ll be happy to help.

cartworthy commented 2 days ago

@Alezanello Words can not describe my frustration and anger in this situation. I appreciate your patience and thoughtful reply, but you're giving me these two options:

  1. Spend my time re-designing and removing widgets that are native features provided by FlutterFlow — which will likely result in sacrifices of the UX.
  2. Pay developers to DOWNGRADE a core custom-code feature in my app to an OLDER version — which I have no idea what that will cost or other barriers may arise from that.

My frustration is that this is because of a breaking "update" from FlutterFlow that I did not consent to and I am unable to go back from. None of the new features FlutterFlow is pushing are of any use for me. I just want to know that what I'm investing my time into building on the platform is stable and not going to be broken because of so-called "updates" that are forced upon me from FlutterFlow.

You "notified users" the update was coming. That's the most frustrating part. So what? What was I supposed to do with that information? Brace myself for impact?! I don't remember being given any options to decline this update. It was involuntary and forced upon on me.

I want my app to just continue working once it's working. I've been paying for FlutterFlow Pro for over 2 years and this is by far my most disappointing experience with the platform. I would like to continue loving the platform, but this is going to change the way I tell others about it.

If there is any other support you can offer, please let me know. Are your developers able to fix my camera feature for me? Free months off my subscription? Any other creative solutions for possibly fixing my app so I can continue working on it after over a week of down-time?

leighajarett commented 2 days ago

Hi there! So sorry you're experiencing this issue. I totally understand your frustration and we're working on a better solution for opting into these sort of updates in the future - it's a hard thing to support but we know it's super important to everyone to prevent issues like this. Can you please send me an email leigha@flutterflow.io so we can discuss how we can help with your specific custom code? Thanks so much!