android studio 忽略已经被索引的文件output-metadata.json

最新推荐文章于 2025-06-11 07:00:00 发布
最新推荐文章于 2025-06-11 07:00:00 发布
阅读量397 收藏
点赞数 2
CC 4.0 BY-SA版权
文章标签： android studio json elasticsearch
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/sooxin/article/details/139552994

Terminal输入

cd .\app\noAnalytics\release\

git rm --cache -r output-metadata.json

output-metadata.json会被从changes列入到"ununservise"目录下

然后git提交窗口把output-metadata.json加入忽略文件，

对应.gitignore增加：

/noAnalytics/release/output-metadata.json

然后commit->push

sooxin
关注
blender 渲染obj 导出obj
jacke121的专栏
03-05 658
blender 渲染obj 导出obj
iData Agent 智能数据分析平台：一站式“创建-配置-分析-可视化”闭环，零代码生成图文混合智能报告
最新发布
AI天才研究院
07-24 907
iData Agent 智能数据分析平台提供一站式零代码数据分析解决方案，支持从数据接入到报告生成的全流程闭环。系统采用微服务架构，包含智能Agent工厂、数据接入中心、知识库管理、分析引擎和可视化报告工坊等核心模块。技术栈整合React前端、FastAPI/Spring后端、ElasticSearch向量检索、DuckDB计算引擎及LLM能力，支持自定义分析框架DSL和插件化扩展。平台通过向导式配置实现Agent创建，自动完成语义解析、数据计算与洞察生成，最终输出图文混合的可交互报告，满足企业级数据分析需
ception: Error loading build artifacts from: 路经\项目名\app\build\outputs\apk\debug\output-metadata.json
彬sir哥的博客
01-14 8160
android studio的报错提示： Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: Error loading build artifacts from: D:\Android2\CustomeListViewFastDrawable1\app\build\outputs\apk\debug\output-metadata.json 解决： ...
andriod studios找不到output-metadata.json的解决方法
qq_44016573的博客
06-20 2359
原因是最后一行的output-metadata.json在应用的build文件夹中找不到，这与应用的build.grandle文件中output-metadata.json的生成路径有关系。当如上图中注释掉build.grandle红框中的生成选项后，不再报该错误。在Android studios上安装运行时，无法直接安装，会报如上错误。
Android 打包 APK 问题：java.io.IOException: Couldn‘t delete ...\app\release\output-metadata.json
weixin_52173250的博客
06-11 191
Android 打包 APK 问题：java.io.IOException: Couldn't delete ...\app\release\output-metadata.json
output-metadata.json
09-14
output-metadata.json
APK打包 output-metadata.json‘ which doesn‘t exist.
一个北漂的程序员
03-03 9047
自定义apk输出路径打包时，出现这个bug A problem was found with the configuration of task ':app:createReleaseApkListingFileRedirect' (type 'ListingFileRedirectTask'). - In plugin 'com.android.internal.version-check' type 'com.android.build.gradle.internal.tasks.Listing.
Android人体检测和人体关键点检测APP Demo安装包
06-21
Android人体检测和人体关键点检测APP，支持CPU多线程和GPU加速，可实时检测(这是 Demo APP)，原文请参考《2D Pose人体关键点实时检测(Python/Android /C++ Demo)》https://panjinquan.blog.csdn.net/article/details/115765863
Android APP 自动更新实现(适用Android9.0)
moon2000boy的博客
04-16 2795
安卓程序在线检查更新
基于jenkins进行定制化开发
Lighthouse
09-15 1500
Jenkins是一个开源的、提供友好操作界面的持续集成(CI)工具，起源于Hudson（Hudson是商用的），主要用于持续、自动的构建/测试软件项目、监控外部任务的运行（这个比较抽象，暂且写上，不做解释）。Jenkins用Java语言编写，可在Tomcat等流行的servlet容器中运行，也可独立运行。通常与版本管理工具(SCM)、构建工具结合使用。常用的版本控制工具有SVN、GIT，构建工具有Maven、Ant、Gradle。
Collecting pin==2.7.0 (from -r requirements.txt (line 55)) Using cached pin-2.7.0.tar.gz (61.8 MB) Installing build dependencies ... error error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> [170 lines of output] Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cu118 Collecting cmeel-boost~=1.83.0 Using cached cmeel_boost-1.83.0.tar.gz (4.0 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'error' error: subprocess-exited-with-error Preparing metadata (pyproject.toml) did not run successfully. exit code: 1 [144 lines of output] -- Building for: Visual Studio 17 2022 -- The C compiler identification is MSVC 19.44.35211.0 -- The CXX compiler identification is MSVC 19.44.35211.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Python3: C:\Users\__CellMan\.conda\envs\foundationpose\python.exe (found version "3.9.23") found components: Interpreter Development.Module -- CONFIGURE_COMMAND: ./bootstrap.sh;--prefix=C:/Users/__CELL~1/AppData/Local/Temp/cmeel-1somp3uw/whl/cmeel.prefix -- BUILD_COMMAND: ./b2;hardcode-dll-paths=true;dll-path='$ORIGIN';link=shared;python=3.9 -- Configuring done (16.4s) -- Generating done (0.0s) CMake Warning: Manually-specified variables were not used by the project: BUILD_TESTING Boost_NO_WARN_NEW_VERSIONS CMAKE_APPLE_SILICON_PROCESSOR CMAKE_INSTALL_LIBDIR CMEEL_JOBS PYTHON_SITELIB -- Build files have been written to: C:/Users/__CELL~1/AppData/Local/Temp/cmeel-1somp3uw/bld 閫傜敤浜\x8e .NET Framework MSBuild 鐗堟湰 17.14.14+a129329f1 C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(548,5): w arning MSB8029: 涓\xad闂寸洰褰曟垨杈撳嚭鐩\xae褰曟棤娉曢┗鐣欏湪涓存椂鐩\xae褰曚笅锛屽洜涓鸿繖鍙\xaf鑳戒細瀵艰嚧澧為噺鐢熸垚鍑 虹幇闂\xae棰樸\x80\x82 [C:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\ZERO_CHECK.vcxproj] 1>Checking Build System C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(548,5): w arning MSB8029: 涓\xad闂寸洰褰曟垨杈撳嚭鐩\xae褰曟棤娉曢┗鐣欏湪涓存椂鐩\xae褰曚笅锛屽洜涓鸿繖鍙\xaf鑳戒細瀵艰嚧澧為噺鐢熸垚鍑 虹幇闂\xae棰樸\x80\x82 [C:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\Boost.vcxproj] Creating directories for 'Boost' Building Custom Rule C:/Users/__CellMan/AppData/Local/Temp/pip-install-5pxl6tt_/cmeel-boost_4fb6f8d6aeca48aab18582433951fa01/CMakeLists.txt Performing download step (download, verify and extract) for 'Boost' -- Downloading... dst='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' timeout='none' inactivity timeout='none' -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 22% complete] -- [download 58% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 58% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 9% complete] -- [download 22% complete] -- [download 58% complete] -- [download 70% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 22% complete] -- [download 58% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 22% complete] -- [download 34% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... -- Using src='https://boostorg.jfrog.io/artifactory/main/release/1.83.0/source/boost_1_83_0.tar.bz2' -- [download 100% complete] -- [download 22% complete] -- [download 34% complete] -- [download 58% complete] -- [download 100% complete] -- verifying file... file='C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2' -- SHA256 hash of C:/Users/__CellMan/AppData/Local/Temp/cmeel-1somp3uw/bld/Boost-prefix/src/boost_1_83_0.tar.bz2 does not match expected value expected: '6478edfe2f3305127cffe8caf73ea0176c53769f4bf1585be237eb30798c3b8e' actual: 'e0f020de72913559199b5698b1f50a733dcfd7e1b0532de4a2357c3baca95e0f' -- Hash mismatch, removing... CMake Error at Boost-stamp/download-Boost.cmake:163 (message): Each download failed! C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: 鈥淐:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-mk dir.rule;C:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-download.ru le;C:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-update.rule;C:\Us ers\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-patch.rule;C:\Users\__CEL L~1\AppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-configure.rule;C:\Users\__CELL~1\A ppData\Local\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-build.rule;C:\Users\__CELL~1\AppData\Lo cal\Temp\cmeel-1somp3uw\bld\CMakeFiles\755458b903e4cca2d215a37840379c36\Boost-install.rule;C:\Users\__CELL~1\AppData\Local\Tem p\cmeel-1somp3uw\bld\CMakeFiles\afcbe1798a3d8227aea59f65cb94f1da\Boost-complete.rule;C:\Users\__CELL~1\AppData\Local\Temp\cmee l-1somp3uw\bld\CMakeFiles\e26596573a2d2b2916d37c037e150495\Boost.rule;C:\Users\__CellMan\AppData\Local\Temp\pip-install-5pxl6t t_\cmeel-boost_4fb6f8d6aeca48aab18582433951fa01\CMakeLists.txt鈥濈殑鑷\xaa瀹氫箟鐢熸垚宸查\x80\x80鍑猴紝浠ｇ爜涓\xba 1銆\x82 [C:\Users\__CELL~1\AppData\Local\Temp\cmeel-1somp3uw\bld\Boost.vcxproj] Traceback (most recent call last): File "C:\Users\__CellMan\.conda\envs\foundationpose\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 389, in <module> main() File "C:\Users\__CellMan\.conda\envs\foundationpose\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 373, in main json_out["return_val"] = hook(**hook_input["kwargs"]) File "C:\Users\__CellMan\.conda\envs\foundationpose\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 178, in prepare_metadata_for_build_wheel whl_basename = backend.build_wheel(metadata_directory, config_settings) File "C:\Users\__CellMan\AppData\Local\Temp\pip-build-env-qq50mhk3\overlay\Lib\site-packages\cmeel\build.py", line 26, in build_wheel return build_impl(wheel_directory, editable=False) File "C:\Users\__CellMan\AppData\Local\Temp\pip-build-env-qq50mhk3\overlay\Lib\site-packages\cmeel\impl.py", line 105, in build_impl check_call(build_cmd) File "C:\Users\__CellMan\.conda\envs\foundationpose\lib\subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '--build', 'C:\\Users\\__CELL~1\\AppData\\Local\\Temp\\cmeel-1somp3uw\\bld', '-j4']' returned non-zero exit status 1. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed Encountered error while generating package metadata. See above for output. note: This is an issue with the package mentioned above, not pip. hint: See above for details. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip.
07-11
我们注意到用户的问题是关于安装pin==2.7.0时，由于Boost...> **关键提示**：校验失败通常表明下载文件被修改或不完整，使用官方源或可信镜像源至关重要[^1][^2]。清华源镜像已通过严格同步验证，可解决99%的校验问题。
Android性能优化(5)：APK瘦身优化
老蒋也疯狂
12-10 3584
文章目录1. APK文件结构2. APK瘦身优化2.1 优化dex文件大小2.1.1 Proguard2.1.2 AndResGuard2.2 优化资源文件大小2.2.1 Android Lint2.2.2 [tinypng](http://leonshi.com/2015/11/02/tinypng-compress/)2.2.3 WebP2.3 优化libs目录大小2.3.1 裁剪libs目录...
深入探索 Android 包体积优化（匠心制作）
IT元老的博客
03-26 5744
前言 成为一名优秀的Android开发，需要一份完备的 知识体系，在这里，让我们一起成长为自己所想的那样~。 在 Android 性能优化的知识体系当中，包体积优化一直被排在优先级比较低的位置，从而导致很多开发同学对自身应用的大小并不重视。在项目发展的历程中，一般可划分为如下三个阶段： 初创期 => 成长期 => 成熟期 通常来说，当应用处于成长期的中后阶段时，才会考虑去做系统的包体......
kts之自定义输出apks目录的几种方法和bug解决
情随事迁个人博客
01-24 711
自定义文件名虽然很ok,但是这个目录因为渠道多了就显得乱七八糟的，我认为所有渠道应该度放到一个单独的文件夹，方便git忽略。 实现方法1： applicationVariants.all { val artifactSuffix = buildString { productFlavors.getOrNull(0)?.name?.let { billingF...
Android--＞产物收集(含apk文件重命名, aab文件重命名)
<angcyo>菜鸟视角
08-13 822
产物收集(含apk文件重命名, aab文件重命名)
qt plugin metadata file does not exist解决方案
weixin_42037123的博客
06-20 1342
做项目的时候经常用自己编写的插件供第三方使用，在vs2015升级到2017后，出现上述问题，查阅了很多资料，都无法解决，vscode突然使用cmake编译时出现了metadata的json文件no exist。 Q_plugin_metadata(iid "***"，FILE,"*.json")报错，导致无法成功编译。 解决方案:删除file以后的东西即可 ...
Android工具: Android Studio中的gradle文件详解
Venus 的博客
10-08 4457
Android Studio 使用的编译环境是Gradle，目前，最新版本是6.5。使用Gradle进行配置和编译，灵活维护性好，而且有较强的自动化，升级容易。Android Studio版本和Gradle的版本也具有一定的关联性，升级到高版本的Android Studio时，它会自动下载和配置相应的gradle版本。
Springboot之additional-spring-configuration-metadata.json自定义提示
热门推荐
z69183787的专栏
10-09 1万+
简介 additional-spring-configuration-metadata.json、spring-configuration-metadata.json在springboot-starter官方项目或第三方starter项目中随处可见，那它起的作用是什么？让我们一起探讨一下。 官方文章 官方一篇文章很详细讲解了Configuration Metadata的作用。 有兴趣的小伙伴可以查看下(配置元数据)。 Configuration Metadata Appendix B. Conf
安卓output-metadata.json是什么文件
11-17
安卓output-metadata.json是一个用于存储应用程序输出的元数据的JSON文件。在安卓应用程序开发中，开发者通常需要生成和输出一些结果或数据，如图片、音频、视频等等。而output-metadata.json文件则用于记录这些输出的相关信息。 output-metadata.json文件包含了每个输出文件的详细描述，比如文件路径、文件类型、文件大小、创建时间等等。这些信息对于应用程序的后续使用、管理和展示都非常重要。例如，当应用程序需要读取之前生成的图片文件时，可以通过查阅output-metadata.json文件来获取图片的路径和其他属性。 此外，output-metadata.json文件还可用于向其他应用程序或设备共享应用程序的输出结果。通过读取output-metadata.json文件，其他应用程序可以获得输出的文件信息，并进行相应的处理和展示。 总而言之，安卓output-metadata.json文件是一个用于记录应用程序输出结果相关信息的JSON文件，可以用于应用程序内部管理和后续使用，也可用于与其他应用程序或设备的数据传输和共享。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值