search

FlutterFlow / flutterflow-issues

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

ios Deployment: Step 6 script `Install pods` exited with status code 1 - update ios pod #2758

Closed MyTechAgent closed 6 months ago

MyTechAgent commented 7 months ago

Has your issue been reported?

Current Behavior

No longer deploying to apple store.

Expected Behavior

Successful deployment message on deployment

Steps to Reproduce

  1. tried to update dependencies around google maps.
  2. tried ipad app deployment, web and windows desktop app.
  3. tried changing version codes
  4. tried deploying a completely different project that is already published on ios and since it doesn't have google maps flutter ios it deploys fine.
  5. Found apple has changed minimum requirements - https://developers.google.com/maps/documentation/ios-sdk/release-notes

Reproducible from Blank

Bug Report Code (Required)

IT40hcmAx491ofpE1876dvlahjw5Jnl6a4EZlOxraCsofePrOpkAf8/7UFtUON/kTG9fMGCJknIX/Mr8uPDhCcIEAAWcGYhdybl1FhXdQmKXSqqkBb63b0B8RPJRGGLA4J2C3Ap5JtJfLl0swE2UF+qvbD7XCb70DlUnQuaeXdeK2SrDX1iXc2URm05KZDPz

Context

i can no longer deploye to apple ios without having a mac. This is stopping me from testing the app as I use custom widgets and functions that are only ios compatible.

Visual documentation

image

Error: `Codemagic Deploy 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/docs/reference/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...

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 "google_maps_flutter_ios": In Podfile: google_maps_flutter_ios (from .symlinks/plugins/google_maps_flutter_ios/ios)

Specs satisfying the google_maps_flutter_ios (from.symlinks/plugins/google_maps_flutter_ios/ios) dependency were found, but they required a higher minimum deployment target.

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

Additional Info

I was previously able to deploy prior to the flutter update coming through.

image

Environment

- FlutterFlow version: 4.1.34+
- Platform: web, ipad, desktop
- Browser name and version: edge, chrome most recent version for both
- Operating system and version affected: windows
DefiLable commented 7 months ago

Same issue for me

MyTechAgent commented 7 months ago

Pretty sure it’s to do with the minimum requirements that changed with Apple and most dependencies having to be changed now due to it. I noticed a lot of dependency updates come through on pub. At the moment I can only suggest downloading VMware if you don’t have a Mac and get an iso image to manually push through Xcode. Hopefully someone will jump on this in the short term :).

DefiLable commented 7 months ago

Hello everyone,

If you encounter deployment issues with your Flutter app, I have found a solution that worked for me which I'd like to share. This involves a few updates both on GitHub and in the iOS-specific files of your Flutter project.

Step 1: Deploy from GitHub

Ensure your latest code is pushed to GitHub and set for deployment. This ensures that all changes are correctly synced and ready for the next steps.

Step 2: Update the Podfile

Navigate to the iOS directory in your Flutter project and open the Podfile. You will need to update the platform version to ensure compatibility with newer iOS versions. Change the line:

platform :ios, '13.0' to

platform :ios, '14.1'

Step 3: Modify the Xcode Project File

Next, go to the /ios/Runner.xcodeproj/project.pbxproj file. Here, you need to update the deployment target to match the Podfile update. Change all instances of:

IPHONEOS_DEPLOYMENT_TARGET = 13.0; to

IPHONEOS_DEPLOYMENT_TARGET = 14.1;

This ensures that the iOS deployment target is consistent across your project settings, preventing potential conflicts during the build process.

After making these changes, try redeploying your app. This resolved the deployment issues in my case and might help you too. Let me know if you have any questions or need further assistance!

MyTechAgent commented 7 months ago

mate you are a genius thank you, I learned a new skill too, which I am sure I can leverage git more than I have been. Giving it a crack now, publishing now.

MyTechAgent commented 7 months ago

spoke to soon. Seems like to merge the branches you need to be a team. Back to trying to spin up a vm to test this...

DefiLable commented 7 months ago

yes sorry I didn't mentionned it but I already had a vm to signup as a team

MyTechAgent commented 7 months ago

kk looks like codemagic.io is actually free. It allows you to connect straight to the git. I would advise trying this as it's the same process as FF.

image

MyTechAgent commented 7 months ago

@DefiLable I just upgraded... did you merge than push to git and adjusted the pods ect, than deployed? Trying to figure out the workflow you used to get it to publish

DefiLable commented 7 months ago

Well I used my flutterflow repository to push from ff, then I used the vm to open the ff repository from Xcode. You have to open from Xcode not from GitHub desktop. Then you sign the code going to runner. Once it’s signed you can push to flutterflow repository. Then you go on GitHub for browser in the main branch and you merge everything. Finally you modify the files mentioned before in our discussion. Then once ecerything is done you go to ff and publish from GitHub. Hope it’s clear,

Nic61 commented 6 months ago

It works from FF web but not from the Mac App

rzambroni commented 6 months ago

Hey everyone, So sorry you are experiencing this issue. I can't replicate this on a blank project. Are you still experiencing it? given the nature of the issue I would encourage you to follow up with our support team so you can validate the configurations specific to your project with them. You can do that either by email: support@flutterflow.io or using the in-app chat inside of FlutterFlow.

MyTechAgent commented 6 months ago

Morning, I will try that as it’s happening across all my projects. Could be that the projects are no longer updating but I have confirmed it’s the pod file minimum requirements that is throwing it all out of whack. The new minimum is 14.1 and not sure if it’s all dependencies or just google maps. I have spent the last 4 days trying to work out workarounds. I will spin up a new project and copy everything across to see if that helps…. Kind Regards, 

Sent from Yahoo Mail for iPhone

On Tuesday, April 23, 2024, 4:51 AM, rzambroni @.***> wrote:

Hey everyone, So sorry you are experiencing this issue. I can't replicate this on a blank project. Are you still experiencing it? given the nature of the issue I would encourage you to follow up with our support team so you can validate the configurations specific to your project with them. You can do that either by email: @.*** or using the in-app chat inside of FlutterFlow.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

MyTechAgent commented 6 months ago

Hey All,

I have message the flutterflow team as above. Still struggling to see why this would be placed as project specific. If it was just me than yes but there is others having the same issue? Either way I will keep everyone up to date.

MyTechAgent commented 6 months ago

So still no update on this but I managed to get GitHub linked up with codemagic. During this process I found out why it worked on a blank project and why it's only impacting particular users. The package google_maps_flutter_iOS("which is imported automatically when you use the google map widget that comes with FF) will no longer deploy for anyone using 14.1 or below. This changes to apple's policy has changed some but not all dependencies. The only way I have found is to have a physical Mac, I change the pod files as stated above, install brew cocoapods files into the same folder as podfile, than configure Xcode (launch_page, permissions ect). After this code magic should accept it once you configure code magic. Unfortunately the workflow is not as fluent as FF but if you use a package that is impacted by this then it's the only way.. @rzambroni If you add your google maps into I bet you can reproduce the issue ;).image

rpock commented 6 months ago

I can confirm that there is a deployment target issue on iOS for google maps. Upgrading it to 14.0 solves the issue in my case.

Bildschirmfoto 2024-04-24 um 17 21 57
ayjayem commented 6 months ago

I am experiencing the same issue. I tried upgrading the minimum deployment target to 14.1 as described, but this didn't solve the problem in my case. I've tried deploying from both the desktop agent and the web app.

MyTechAgent commented 6 months ago

Make sure when you upgrade it, you use control + f to search for 13.0 and than use the replace all with 14.1. Once you get this sorted and working the first time you can than go to Xcode cloud.

ayjayem commented 6 months ago

Appreciate it - did this, but with no luck directly through FF. Using codemagic.io after having updated from 13.0 to 14.1 is working for me though, so not blocked - but will be nice to see this resolved in FF soon hopefully.

MyTechAgent commented 6 months ago

Ahh yes did the same thing but hit the limit so went to Xcode cloud with 25 build hours free each month. Tbh I think FF is burning a little at the moment with the major update. I wouldn't expect this to be solved anytime soon as most people don't get to the deployment stage. Going of this though I setup a GitHub automation to auto push to iOS store. Hope I am wrong but a Quick Look around will show that they will need to fix a fair few things to update the pods. Appple has thrown a grenade in the works with the policy update, they are also requiring additional privacy files to be uploaded that FF have advised they are working on

ayjayem commented 6 months ago

Oof, challenging.

I spoke too soon as well - Codemagic build submitted successfully and processed just fine, but crashes in TestFlight.

I did notice though just now that the minimum deployment target is also listed in ios/Flutter/AppFrameworkInfo.plist, which I just corrected... hoping that along with the updates to the other references of the deployment target will remedy.

ayjayem commented 6 months ago

Yeah sadly no luck. This issue is still outstanding for me -- really hope that the FlutterFlow team can address, as I'm completely blocked at the moment.

MyTechAgent commented 6 months ago

Someone else may need to create a new git post to report this as I worry the FF team have no oversight of this as it's marked as project specific by the last contributor.. which may only show up as an impact to one user.. we need it to be marked as an incident if we want action on it. Otherwise just do workarounds. From how this was handled I ended up stopping payments to FF and went back to coding manually on top of the infrastructure FF already built. Don't see a point if I can't deploy from there :). image

paramparim commented 6 months ago

Hello! I faced the same problem. It helped me to resubmit for publication with the same version number and build number for which this error occurred. As a result, the application successfully got into TestFlight.

github-actions[bot] commented 6 months ago

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

rpock commented 6 months ago

What do you think about the following idea, to specify the deployment target for iOS in the advanced settings like the advanced settings for Android?

image
ayjayem commented 6 months ago

This makes sense to me.

leighajarett commented 6 months ago

Thanks for this feedback, I do think we need to add that as an option. We track features separately internally so I will close this issue - but this has been added to our backlog. Thanks!

DefiLable commented 6 months ago

Hi Leigha, It is also blocking one of your major feature when using a Mac : testing on a simulated iPhone, It would be great If you handle the problem ! Thank you !

leighajarett commented 6 months ago

You can test on iOS simulator using local run 🙂

DefiLable commented 6 months ago

I wish I could, but because it’s not installing pods I can only test on simulator after downloading the code, modifying the deployment target and then launch simulator but I can’t use local run with the simulator. I can on an android simulated device but not on an iPhone simulated device…

DefiLable commented 6 months ago

I have the same error when I try to local run

leighajarett commented 6 months ago

Please reach out to our support team who can better advise support@flutterflow.io

MyTechAgent commented 6 months ago

I will try and write a guide tonight on how to fix the issue in the workaround with pods. There is a couple of things you will need to do in order to get it to work. Keep in mind you will need a Mac.

leighajarett commented 6 months ago

That sounds amazing, thank you!

MyTechAgent commented 5 months ago

Hi All,

Sorry for the tutorial for the workaround taking a while. After I figured out the solution I ended up working on my MVP to try and catch up on all the lost time from this issue still being an issue. Please find attached the documentation. Step-by-Step_Tutorial_Setting_Up_CodeMagic_or_Xcode_Cloud.docx