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

Can't compile an iOS release app with this package #2

Open
ljmatan opened this issue Sep 9, 2022 · 4 comments
Open

Can't compile an iOS release app with this package #2

ljmatan opened this issue Sep 9, 2022 · 4 comments

Comments

@ljmatan
Copy link

ljmatan commented Sep 9, 2022

No description provided.

@derolf
Copy link
Owner

derolf commented Sep 9, 2022

Do you have an example or an error log?

@ljmatan
Copy link
Author

ljmatan commented Sep 9, 2022

Flutter doctor:

[✓] Flutter (Channel master, 3.4.0-19.0.pre.88, on macOS 12.0.1 21A559
    darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.71.0)
[✓] VS Code (version 1.72.0-insider)
[✓] Connected device (3 available)
    ! Device BA6H5LVWDAROW4V4 is not authorized.
      You might need to check your device for an authorization dialog.
[✓] HTTP Host Availability

• No issues found!

Steps:

  1. Remove .symlinks, Pods, and Podfile.lock from ios folder
  2. Run pod install --repo-update
  3. Run flutter pub get
  4. Run flutter build ios --verbose

Logs:

Can't reproduce any longer after running flutter pub cache repair. It complained about iOS deployment target.

Many thanks.

@ljmatan ljmatan closed this as completed Sep 9, 2022
@derolf
Copy link
Owner

derolf commented Sep 9, 2022

Btw what feature are you using?

@ljmatan ljmatan reopened this Sep 11, 2022
@ljmatan
Copy link
Author

ljmatan commented Sep 11, 2022

It seemed to happen again today - after removing the package from pubspec.yaml the issue disappears, sadly I haven't recorded any logs just yet.

Today it happened with running for MacOS, nothing was working to fix the issue until I've removed the package

BTW we're only testing this package to see how it'd work with our automated error reporting, sadly we haven't been able to test it due to compile issues.

I've reopened an issue as this issue seems to recurr with the package, I won't be testing it any longer, so if you'd like to you can close the issue.

Thanks again.

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

No branches or pull requests

2 participants