Skip to content
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

Fixing ios build #1001

Merged
merged 2 commits into from
Oct 6, 2023
Merged

Fixing ios build #1001

merged 2 commits into from
Oct 6, 2023

Conversation

DGoiana
Copy link
Collaborator

@DGoiana DGoiana commented Oct 5, 2023

We had to bump the add_2_calendar version to 2.2.4 because of changes in swift.
We also stage the podfile to ease the build of the project, we don't stage the podlock because dependencies are tracked by flutter. In order to the build process to work properly we had to create a RunnerTests target, since the podfile requires it.

Copy link
Member

@LuisDuarte1 LuisDuarte1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔨

@codecov
Copy link

codecov bot commented Oct 5, 2023

Codecov Report

Merging #1001 (265229a) into master (59558fc) will not change coverage.
Report is 2 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #1001   +/-   ##
======================================
  Coverage      16%     16%           
======================================
  Files         201     201           
  Lines        6361    6361           
======================================
  Hits          986     986           
  Misses       5375    5375           

@bdmendes bdmendes merged commit d43af89 into master Oct 6, 2023
6 checks passed
@bdmendes bdmendes deleted the fix/ios-build branch October 6, 2023 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants