-
Notifications
You must be signed in to change notification settings - Fork 130
iOS build faild #160
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
Comments
LiquidCore version: 0.7.3 |
This is an incredibly strange set of symbols to be undefined (and just those?). Very odd. I cannot reproduce this. What does your podfile look like? |
@ericwlange Thank you for your response. This is happened on my office iMac, build is ok on myself macbookpro. |
Hi, there. I had the same problem.
load '.liquidcore/liquidcore.rb'
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'
target 'LiquidCoreTest' do
# liquidcore_pods
pod 'LiquidCore', git: 'https://github.com/LiquidPlayer/LiquidCore.git', commit: 'HEAD'
# Comment the next line if you don't want to use dynamic frameworks
use_frameworks!
# Pods for LiquidCoreTest
target 'LiquidCoreTestTests' do
inherit! :search_paths
# Pods for testing
end
target 'LiquidCoreTestUITests' do
# Pods for testing
end
end |
I've also run into this issue, and I think I finally have a satisfactory reason why it failed in the first place and what to do about it. I spotted this in the pod install --verbose log when attempting to use this module via a Flutter plugin, after a day or so of banging my head against the problem:
This looks to be a python 2.7 vs python 3 error being emitted from the prepare_command step in the Pod install script. Resolving it is simple - make sure you change to use a global python 2.7 version instead. If you're seeing this on macOS, this is probably (but not strictly) down to using pyenv to use a python 3 script environment; just switch to using the system version instead. Doing so causes all the scripts in the prepare_command to be executed completely. As a suggestion for this issue, it would be good to get the pod installation to fail with a proper error message explaining the python environment isn't right - for anyone affected by it however, it is at least simple to work around. You will need to clean the Cocoapods cache directory and rebuild the pod after switching to python 2.7:
|
That's right! #setting path for python 2.7 to .bash_profile If you are a chip of m1, you need to download python 2.7.18 in advance!!!!! **【非常重要】1.需要提前下载python2.7.18 !!这一点非常重要,然后确定python2.7.18可以正常在你的环境上运行起来 flutter 删掉你工程下的 pubspec.lock pod cache clean 'LiquidCore' |
xcode: 11.4
macos: 10.15.4
The text was updated successfully, but these errors were encountered: