如果您想了解无法在macOS上找到“Frameworks/App.framework/flutter_assets”的资产路径和无法在您的库中找到prodefs的知识,那么本篇文章将是您的不二之选。我
如果您想了解无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径和无法在您的库中找到prodefs的知识,那么本篇文章将是您的不二之选。我们将深入剖析无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径的各个方面,并为您解答无法在您的库中找到prodefs的疑在这篇文章中,我们将为您介绍无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径的相关知识,同时也会详细的解释无法在您的库中找到prodefs的运用方法,并给出实际的案例分析,希望能帮助到您!
本文目录一览:- 无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径(无法在您的库中找到prodefs)
- -bash: /usr/local/bin/pod: /System/Library/Frameworks/Ruby.framework
- /Library/Frameworks/Python.framework/Versions/3.7/bin/python3和/usr/local/bin/python3中的Python有什么区别
- /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python:无法打开文件“esptool.py”
- 13 fabulous frameworks for Node.js
无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径(无法在您的库中找到prodefs)
如何解决无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径
IOS应用卡在白屏上。我已经尝试应用以下链接中提供的所有方法:
https://github.com/flutter/flutter/issues/29974
failed-to-find-assets-path-for-frameworks-app-framework-flutter-assets
ios-project-migration
除此之外,我还尝试切换到频道 master ,稳定和 beta ,然后切换到Flutter upgrade
以下错误在ios上显示为白色屏幕。
Runner[1469:358771] Failed to find assets path for "Frameworks/App.framework/Flutter_assets"
2020-09-25 11:23:36.139301+0300 Runner[1469:358771] Metal API Validation Enabled
2020-09-25 11:23:36.255401+0300 Runner[1469:359037] Flutter: Observatory listening on http://127.0.0.1:60092/RGJQkAJoLdQ=/
2020-09-25 11:23:36.267284+0300 Runner[1469:359021] 6.26.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled,will swizzle remote notification receiver handlers. If you''d prefer to manually integrate Firebase Messaging,add "FirebaseAppDelegateProxyEnabled" to your Info.plist,and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2020-09-25 11:23:36.268203+0300 Runner[1469:359016] 6.26.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60600000 started
2020-09-25 11:23:36.268648+0300 Runner[1469:359016] 6.26.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see some link here)
2020-09-25 11:23:36.523458+0300 Runner[1469:358771] WF: === Starting WebFilter logging for process Runner
2020-09-25 11:23:36.523517+0300 Runner[1469:358771] WF: _userSettingsForUser mobile: {
filterBlacklist = (
);
filterWhitelist = (
);
restrictWeb = 1;
useContentFilter = 0;
useContentFilterOverrides = 0;
whitelistEnabled = 0;
}
2020-09-25 11:23:36.523578+0300 Runner[1469:358771] WF: _WebFilterIsActive returning: NO
2020-09-25 11:23:36.524278+0300 Runner[1469:358771] [Firebase/Crashlytics] Version 4.1.1
2020-09-25 11:23:36.527135+0300 Runner[1469:359023] 6.26.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-09-25 11:23:36.529562+0300 Runner[1469:359023] 6.26.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting,set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2020-09-25 11:23:36.539596+0300 Runner[1469:359021] 6.26.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2020-09-25 11:23:36.570952+0300 Runner[1469:358771] Failed to find assets path for "Frameworks/App.framework/Flutter_assets"
2020-09-25 11:23:36.572494+0300 Runner[1469:358771] Failed to find assets path for "Frameworks/App.framework/Flutter_assets"
2020-09-25 11:23:36.573146+0300 Runner[1469:358771] database path: /var/containers/Bundle/Application/3875121B-A000-4B67-96A7-DEE8B14FAFB8/Runner.app/Frameworks/Flutter_downloader.framework/FlutterDownloaderDatabase.bundle/download_tasks.sql
2020-09-25 11:23:36.573321+0300 Runner[1469:358771] MAXIMUM_CONCURRENT_TASKS = 1
2020-09-25 11:23:36.580536+0300 Runner[1469:358771] init NSURLSession with id: com.vt.vt.download.background.1601022216.573343
2020-09-25 11:23:36.580575+0300 Runner[1469:358771] AllFilesDownloadedMessage: All files have been downloaded
2020-09-25 11:23:36.582748+0300 Runner[1469:359026] [VERBOSE-2:engine.cc(134)] Engine run configuration was invalid.
2020-09-25 11:23:36.582785+0300 Runner[1469:359026] [VERBOSE-2:shell.cc(486)] Could not launch engine with configuration.
2020-09-25 11:23:36.833783+0300 Runner[1469:358771] [VERBOSE-2:FlutterObservatoryPublisher.mm(115)] Failed to register observatory port with mDNS.
2020-09-25 11:23:37.016415+0300 Runner[1469:358771] [assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
2020-09-25 11:23:37.016456+0300 Runner[1469:358771] [ProcessSuspension] 0x10fcccbc0 - ProcessAssertion: Failed to acquire RBS Background assertion ''WebProcess Background Assertion'' for process with PID 1470,error: Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}
2020-09-25 11:23:43.788525+0300 Runner[1469:359042] [connection] nw_resolver_start_query_timer_block_invoke [C3] Query fired: did not receive all answers in time for firebasedynamiclinks-ipv4.googleapis.com:443
颤抖的医生
[✓] Flutter (Channel master,1.22.0-10.0.pre.356,on Mac OS X 10.15.6 19G2021
x86_64,locale en-ET)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.48.2)
[✓] Connected device (3 available)
如果我的构建阶段有问题,这里就是它的样子
Podfile看起来像这样
# Uncomment this line to define a global platform for your project
platform :ios,''9.0''
# CocoaPods analytics sends network stats synchronously affecting Flutter build latency.
ENV[''COCOAPODS_disABLE_STATS''] = ''true''
project ''Runner'',{
''Debug'' => :debug,''Profile'' => :release,''Release'' => :release,}
def Flutter_root
generated_xcode_build_settings_path = File.expand_path(File.join(''..'',''Flutter'',''Generated.xcconfig''),__FILE__)
unless File.exist?(generated_xcode_build_settings_path)
raise "#{generated_xcode_build_settings_path} must exist. If you''re running pod install manually,make sure Flutter pub get is executed first"
end
File.foreach(generated_xcode_build_settings_path) do |line|
matches = line.match(/FlutteR_ROOT\\=(.*)/)
return matches[1].strip if matches
end
raise "FlutteR_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig,then run Flutter pub get"
end
require File.expand_path(File.join(''packages'',''Flutter_tools'',''bin'',''podhelper''),Flutter_root)
Flutter_ios_podfile_setup
target ''Runner'' do
use_frameworks!
use_modular_headers!
Flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
Flutter_additional_ios_build_settings(target)
end
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
# Here are some configurations automatically generated by Flutter
# You can remove unused permissions here
# for more infomation: https://github.com/BaseflowIT/Flutter-permission-handler/blob/develop/permission_handler/ios/Classes/PermissionHandlerEnums.h
# e.g. when you don''t need camera permission,just add ''PERMISSION_CAMERA=0''
config.build_settings[''GCC_PREPROCESSOR_DEFinitioNS''] ||= [
''$(inherited)'',## dart: PermissionGroup.calendar
''PERMISSION_EVENTS=0'',## dart: PermissionGroup.reminders
''PERMISSION_REMINDERS=0'',## dart: PermissionGroup.contacts
''PERMISSION_CONTACTS=0'',## dart: PermissionGroup.camera
# ''PERMISSION_CAMERA=0'',## dart: PermissionGroup.microphone
# ''PERMISSION_MICROPHONE=0'',## dart: PermissionGroup.speech
''PERMISSION_SPEECH_RECOGNIZER=0'',## dart: PermissionGroup.photos
# ''PERMISSION_PHOTOS=0'',## dart: [PermissionGroup.location,PermissionGroup.locationAlways,PermissionGroup.locationWhenInUse]
''PERMISSION_LOCATION=0'',## dart: PermissionGroup.notification
# ''PERMISSION_NOTIFICATIONS=0'',## dart: PermissionGroup.mediaLibrary
''PERMISSION_MEDIA_LIBRARY=0'',## dart: PermissionGroup.sensors
''PERMISSION_SENSORS=0''
]
end
end
end
-bash: /usr/local/bin/pod: /System/Library/Frameworks/Ruby.framework
-bash: /usr/local/bin/pod: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby: bad interpreter: No such file or directory
这是Mac升级系统导致,当你的Mac系统升级为 high siera的时候,别忘记更新cocoapods。
执行命令:
$ sudo gem update --system
$ sudo gem install cocoapods -n/usr/local/bin
文章出处:https://www.cnblogs.com/jyking/p/8041841.html
/Library/Frameworks/Python.framework/Versions/3.7/bin/python3和/usr/local/bin/python3中的Python有什么区别
如何解决/Library/Frameworks/Python.framework/Versions/3.7/bin/python3和/usr/local/bin/python3中的Python有什么区别
我最近格式化了我的 Macbook,我只记得下载过一次 python3。所以当我去改变我的解释器路径时,它显示了 2 个不同的 python3 路径。我知道我的系统默认安装了最上面的一个,但至于最下面的两个,我不太确定它们之间有什么区别。
解决方法
第一个 (Python2.7) 是系统默认/内置 Python。
中间的 (Python3,/Library/Frameworks/Python.framework/
) 是您使用 macOS 安装程序(类似于 {{1} }).
最下面的(Python3,python-3.8.7-macosx10.9-1.pkg
)是你使用 Homebrew 安装 Python 时通常得到的:Python Releases for Mac OS X。
/usr/local/bin/python3
python.org 和 Homebrew 之间在功能方面没有区别。如果您安装了相同的版本,它们的工作方式应该相同。除了路径之外,唯一的区别是当您需要升级和/或删除您的安装时(例如从 python3.8 到 python3.9),使用 Homebrew 使用 ~$ brew info python3
python@3.9: stable 3.9.1 (bottled)
...
Python has been installed as
/usr/local/bin/python3
...
You can install Python packages with
pip3 install <package>
They will install into the site-package directory
/usr/local/lib/python3.9/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
和 {{1 }}。
至于为什么 VS Code 会找到这些 Python 解释器,请参阅 https://docs.brew.sh/Homebrew-and-Python 的 VS Code 文档部分,其中列出了“标准安装路径,例如 brew upgrade python3
、{{1 }}、brew uninstall python3
、/usr/local/bin
、/usr/sbin
等”。
/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python:无法打开文件“esptool.py”
如何解决/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python:无法打开文件“esptool.py”
我正在 mac OS X 上使用 ESP8266Flash.app 更新 ESP8266 固件。 但是当我开始刷固件时出现以下错误:
/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python: can''t open file ''esptool.py'': [Errno 1] Operation not permitted."
我该如何解决这个问题?
13 fabulous frameworks for Node.js
Node.js may be several years old now, but it''s still in the spring of its life. The options are multiplying, as everyone experiments with new and better ways to deliver information from the platform. These efforts translate into dozens of frameworks for Node.js enthusiasts and newbies to explore, and new growth everywhere.
What follows are a few of the most prominent frameworks that have caught our eye. They make it simpler to build a complex website filled with pages, panels, fragments, and more. If you''re starting a new project, try out a few of these to quickly build on all the prior work and experience that has been bundled into these projects.
[ Beyond jQuery: An expert guide to JavaScript frameworks. | Keep up with hot topics in programming with InfoWorld''s Application Development newsletter. ]
Express is a very thin shell that offers a framework for lightweight processing of requests. It maps the URL to a template and fills in the values with data from a generic data store. The standard template engine is Consolidate, but the pattern is simple enough that most template engines will work quite well.
The Express team promises that MySpace is trying to upgrade its hipness score by building the next version in Express. If you don''t remember MySpace, ask your grandparents. They may still have an account.
Express is distributed under the MIT license from GitHub.
The team that built Express decided to move on and build the next generation with a new, telescoping call stack called Koa.js that''s designed to let you add new features to the call and response handshake. You start by writing a bit of code to handle the request, but then you can customize anything along the path. The middleware that handles all of the telemetry and error handling are open for your changes. There are also dozens of plug-in packages that add compression, caching, JSON encoding, and more to the stack.
The image above shows some of the Jade markup used by one of the templating libraries bundled with Koa.
Koa is distributed under the MIT license from GitHub.
The Total.js stack is designed to automate as much as possible. You start with a markup template for the HTML and CSS, and Total then compiles it into raw code and compresses it for delivery. In a sense, Total is one big compiler of websites masquerading as a framework.
The image above shows an example built to support a sushi bar website with ordering and more.
Total is distributed under the MIT license from GitHub.
One of the points of Node.js is to use the same language in the browser and the server. Derby.js takes this to the extreme by trying to run the same code in both and synchronizing the results. Then it tosses in template rendering, packaging, and some MVC to simplify the process. You don''t need to worry about, say, compiling your CSS because Derby has it integrated.
The image above shows a basic To Do example distributed with the code.
Derby is distributed under the MIT License at GitHub.
Meteor.js is a real-time application designed to build Web apps that constantly synchronize with the server. Your changes to templates and data flow from the server to the browser automatically. The redrawing and the updating are handled directly by the underlying framework. This works, by the way, in both directions. Your browser code can make changes or write data as if the database is right there. The synchronization happens in the background.
The image above shows an app for synchronizing the work of emergency first responders built in Meteor.
Meteor is distributed under the Apache license with its own install script from the Meteor website and from Github.
Not every application requires full support for a browser. Restify is one of the server-side frameworks designed to serve up data and only data through an API. You fire it up and out comes JSON to everyone who shows up.
Restify places special emphasis on debugging and profiling so that you can drill down and optimize the performance of your server. DTrace is well-integrated and supported to make it possible to watch what happens and when it might go wrong.
The image above shows an audit packet saved from a debugging session.
Restify is available from GitHub under a very basic license that requires little except a notice of copyright.
You can build full websites with the Hapi framework, but many who use Hapi focus on building services that pull data from the background and deliver it quickly and efficiently. Each server is only a collection of maps between URL paths and functions that generate answers, and these routes are configured using the Hapi API rather than being baked into new code. The Hapi community supports a wide variety of plug-ins that tackle many of the chores of authentication and security necessary for building services.
The screenshot above shows a few of the standardized errors that are formalized by the Boom plug-in, which provides a set of utilities to help users better understand what has gone wrong when an HTTP error arises.
Hapi is available with a license requiring basic attribution from GitHub.
If you need to create a business-grade custom Web application, the Sails.js MVC framework will handle many of your app’s core tasks while remaining flexible enough to work with other tools. It is both “front-end agnostic” and ready to work with “any database,” according to the maintainers. The magic in between is largely automated, at least if you want to work with the standard REST API generated by the framework. If you’ve enjoyed the Ruby philosophy of convention and MVC separation, everything will be familiar to you -- and ready to go.
The illustration above shows the basic directory structure of a Sails app.
Sails is available under the MIT license from GitHub.
Most of the work of creating an API can be automated. Once you know the data model, building the tools for editing the data is largely an exercise. StrongLoop automates much of this and adds connectors for most of the big data stores like Oracle, MySQL, and MongoDB. To add more flexibility, they support either dynamic data models that evolve with time or static models with a fixed schema. It''s your choice. There''s also a ready-made security layer with access control lists and some good mobile services. All of this is built on top of Express so that you start with all of the Express feature set.
You can see StrongLoop''s API explorer in the image above.
StrongLoop is available with either a hybrid open source license for test projects or under a subscription that includes support and more connectors to high-end databases like Oracle. Code is available at GitHub.
Many frameworks aim to deliver high-end support for full-featured users running browsers and interacting via JSON. ActionHero does that but also works on a lower-level, communicating directly with the TCP with wire protocols. It''s great if you need something simpler than JSON. This can be quite useful if you want to send out raw files too because ActionHero delivers like a CDN without forcing you to run Apache or Nginx.
The image above shows ActionHero''s stack with the sections devoted to handling the different actions and its connection to Redis.
ActionHero is available under the Apache license from GitHub.
Express and MongoDB are key components of the Node.js stack, but you need to knit them together and add a bit more functionality to actually deliver your message to the world. Keystone.js is meant to join Express and MongoDB together to complete the arch, in this case a content management system. This is now a bit easier thanks to Keystone’s scaffold-building service called Yeoman, which fills out the files and installs everything you might need to run a blog or post other content.
The image above shows a corner of an image-sharing demonstration page built using Yeoman and Keystone.
Keystone is available under the MIT license from GitHub.
SQL databases like PostgresQL or MySQL are from the old transactional world where you send off a command and wait for the answer. Node is built on the more asynchronous call-back architecture common in JavaScript. Sequelize merges the two. When you create an SQL query for any of the five major databases it supports, Sequelize sends the query off and promises to call your function when an answer arrives from the database. It marries the old world with the new architectural imperative.
The image above shows how an old SQL query can be rewritten to work in the modern world of Node.
Sequelize’s source code is released under a basic attribution license from GitHub.
Mean isn’t really a framework for Node.js; it’s a collection of frameworks and technologies that are pre-optimized to play well together, under the acronym MEAN, which stands for MongoDB, Express, Angular, and Node. Each component is among the most popular parts of the Node ecosystem on their own; together, they’re even easier to use.
The image above shows how the Node package manager will install the parts and a new command, mean, for developing applications.
The parts that make up Mean are available under their own licenses from their own repositories.
关于无法在macOS上找到“ Frameworks / App.framework / flutter_assets”的资产路径和无法在您的库中找到prodefs的介绍已经告一段落,感谢您的耐心阅读,如果想了解更多关于-bash: /usr/local/bin/pod: /System/Library/Frameworks/Ruby.framework、/Library/Frameworks/Python.framework/Versions/3.7/bin/python3和/usr/local/bin/python3中的Python有什么区别、/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python:无法打开文件“esptool.py”、13 fabulous frameworks for Node.js的相关信息,请在本站寻找。
本文标签: