a build only device cannot be used to run this targe

最新推荐文章于 2020-04-02 15:48:24 发布
原创 最新推荐文章于 2020-04-02 15:48:24 发布 · 7.8k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了在iOS开发过程中遇到的一个常见编译错误：“abuildonlydevicecannotbeusedtorunthistarget”。文中提供了详细的错误信息，并给出了具体的解决办法：通过选择正确的iOS模拟器来避免此类错误。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

1、  编译的时候  报这个消息


a build only device cannot be used to run this targe



2.  解决办法


选中项目，如下图   选择一个ios simulators




什么是In-Memory计算？ Mastering In Memory Computing:A Comprehensive Guide
AI天才研究院
07-20 3181
作者：禅与计算机程序设计艺术 什么是In-Memory计算？ In-memory computing refers to the process of executing computational tasks by storing input and output data i
[Openwrt]一步一步搭建MT7981A uboot、atf、openwrt-21.02开发环境操作说明
wgl307293845的博客
08-16 3474
软件安装包。
A build only device cannot be used to run this target异常
yanhaijunyan的博客
04-02 1万+
A build only device cannot be used to run this target. 原因 1) DeploymentTarget适配的硬件设备环境版本号选择出错 Generic iOS Device适用于ipa产品打包 不用于USB联调（USB联调选择真机设备） 2）可以手动添加需要的设备 步骤为：启动Xcode，选择菜单Window->Devices，然后弹出窗...
iOS程序打包步骤:A build only device cannot be used to run this target问题解决
weixin_30686845的博客
04-05 313
# 02-打包测试出现A build only device cannot be used to run this target问题解决:模拟器deployment修改成8.0即可....:: 场景描述: 你在上海一家外包公司工作, 给一西藏的客户开发一款App, 那么当你开发完毕之后, 需要给客户演示,客户需要体验,该怎么做? ::- 方案1: 客户坐飞机到公司, 通过真机调试安装- 方案2: ...
A build only device cannot be used to run this target.----献给新手
onebutterfly
03-18 1万+
今天师弟问了个问题，说他弄了一天都没结果，所以下面的解决方法是想给新手的A build only device cannot be used to run this target. 造成这个错误的原因是，你选择的版本号，在虚拟机中没有， 所以我们要重新选择版本号 （1）可能选择的版本号，在虚拟机中没有（2）如果还是不行，还可以手动添加需要的模拟器 步骤为：启动Xcode，选择菜
A build only device cannot be used to run this target.
热门推荐
追求无止尽，永不停步
09-10 1万+
A build only device cannot be used to run this target. 造成这个错误的原因是，你选择的版本号，在虚拟机中没有， 所以我们要重新选择版本号
unity代码在Xcode上提示：A build only device cannot be used to run this target
chuanzhuchu0617的博客
06-23 761
unity代码在Xcode上提示：A build only device cannot be used to run this target。 如果没有连接手机，则会有以上提示，可以先用仿真器搞定。 解决办法： In Unity, you must click on Buil...
Return SnapshotManager::CreateUpdateSnapshots(const DeltaArchiveManifest& manifest) { auto lock = LockExclusive(); if (!lock) return Return::Error(); auto update_state = ReadUpdateState(lock.get()); if (update_state != UpdateState::Initiated) { LOG(ERROR) << "Cannot create update snapshots in state " << update_state; return Return::Error(); } // TODO(b/134949511): remove this check. Right now, with overlayfs mounted, the scratch // partition takes up a big chunk of space in super, causing COW images to be created on // retrofit Virtual A/B devices. if (device_->IsOverlayfsSetup()) { LOG(ERROR) << "Cannot create update snapshots with overlayfs setup. Run `adb enable-verity`" << ", reboot, then try again."; return Return::Error(); } const auto& opener = device_->GetPartitionOpener(); auto current_suffix = device_->GetSlotSuffix(); uint32_t current_slot = SlotNumberForSlotSuffix(current_suffix); auto target_suffix = device_->GetOtherSlotSuffix(); uint32_t target_slot = SlotNumberForSlotSuffix(target_suffix); auto current_super = device_->GetSuperDevice(current_slot); auto current_metadata = MetadataBuilder::New(opener, current_super, current_slot); if (current_metadata == nullptr) { LOG(ERROR) << "Cannot create metadata builder."; return Return::Error(); } auto target_metadata = MetadataBuilder::NewForUpdate(opener, current_super, current_slot, target_slot); if (target_metadata == nullptr) { LOG(ERROR) << "Cannot create target metadata builder."; return Return::Error(); } // Delete partitions with target suffix in |current_metadata|. Otherwise, // partition_cow_creator recognizes these left-over partitions as used space. for (const auto& group_name : current_metadata->ListGroups()) { if (android::base::EndsWith(group_name, target_suffix)) { current_metadata->RemoveGroupAndPartitions(group_name); } } SnapshotMetadataUpdater metadata_updater(target_metadata.get(), target_slot, manifest); if (!metadata_updater.Update()) { LOG(ERROR) << "Cannot calculate new metadata."; return Return::Error(); } // Delete previous COW partitions in current_metadata so that PartitionCowCreator marks those as // free regions. UnmapAndDeleteCowPartition(current_metadata.get()); // Check that all these metadata is not retrofit dynamic partitions. Snapshots on // devices with retrofit dynamic partitions does not make sense. // This ensures that current_metadata->GetFreeRegions() uses the same device // indices as target_metadata (i.e. 0 -> "super"). // This is also assumed in MapCowDevices() call below. CHECK(current_metadata->GetBlockDevicePartitionName(0) == LP_METADATA_DEFAULT_PARTITION_NAME && target_metadata->GetBlockDevicePartitionName(0) == LP_METADATA_DEFAULT_PARTITION_NAME); std::map<std::string, SnapshotStatus> all_snapshot_status; // In case of error, automatically delete devices that are created along the way. // Note that "lock" is destroyed after "created_devices", so it is safe to use |lock| for // these devices. AutoDeviceList created_devices; const auto& dap_metadata = manifest.dynamic_partition_metadata(); CowOptions options; CowWriter writer(options); bool cow_format_support = true; if (dap_metadata.cow_version() < writer.GetCowVersion()) { cow_format_support = false; } LOG(INFO) << " dap_metadata.cow_version(): " << dap_metadata.cow_version() << " writer.GetCowVersion(): " << writer.GetCowVersion(); bool use_compression = IsCompressionEnabled() && dap_metadata.vabc_enabled() && !device_->IsRecovery() && cow_format_support; std::string compression_algorithm; if (use_compression) { compression_algorithm = dap_metadata.vabc_compression_param(); if (compression_algorithm.empty()) { // Older OTAs don't set an explicit compression type, so default to gz. compression_algorithm = "gz"; } } else { compression_algorithm = "none"; } PartitionCowCreator cow_creator{ .target_metadata = target_metadata.get(), .target_suffix = target_suffix, .target_partition = nullptr, .current_metadata = current_metadata.get(), .current_suffix = current_suffix, .update = nullptr, .extra_extents = {}, .compression_enabled = use_compression, .compression_algorithm = compression_algorithm, }; auto ret = CreateUpdateSnapshotsInternal(lock.get(), manifest, &cow_creator, &created_devices, &all_snapshot_status); if (!ret.is_ok()) return ret; auto exported_target_metadata = target_metadata->Export(); if (exported_target_metadata == nullptr) { LOG(ERROR) << "Cannot export target metadata"; return Return::Error(); } ret = InitializeUpdateSnapshots(lock.get(), target_metadata.get(), exported_target_metadata.get(), target_suffix, all_snapshot_status); if (!ret.is_ok()) return ret; if (!UpdatePartitionTable(opener, device_->GetSuperDevice(target_slot), *exported_target_metadata, target_slot)) { LOG(ERROR) << "Cannot write target metadata"; return Return::Error(); } // If compression is enabled, we need to retain a copy of the old metadata // so we can access original blocks in case they are moved around. We do // not want to rely on the old super metadata slot because we don't // guarantee its validity after the slot switch is successful. if (cow_creator.compression_enabled) { auto metadata = current_metadata->Export(); if (!metadata) { LOG(ERROR) << "Could not export current metadata"; return Return::Error(); } auto path = GetOldPartitionMetadataPath(); if (!android::fs_mgr::WriteToImageFile(path, *metadata.get())) { LOG(ERROR) << "Cannot write old metadata to " << path; return Return::Error(); } } SnapshotUpdateStatus status = ReadSnapshotUpdateStatus(lock.get()); status.set_state(update_state); status.set_compression_enabled(cow_creator.compression_enabled); if (cow_creator.compression_enabled) { if (!device()->IsTestDevice()) { bool userSnapshotsEnabled = IsUserspaceSnapshotsEnabled(); const std::string UNKNOWN = "unknown"; const std::string vendor_release = android::base::GetProperty( "ro.vendor.build.version.release_or_codename", UNKNOWN); // No user-space snapshots if vendor partition is on Android 12 if (vendor_release.find("12") != std::string::npos) { LOG(INFO) << "Userspace snapshots disabled as vendor partition is on Android: " << vendor_release; userSnapshotsEnabled = false; } // Userspace snapshots is enabled only if compression is enabled status.set_userspace_snapshots(userSnapshotsEnabled); if (userSnapshotsEnabled) { is_snapshot_userspace_ = true; status.set_io_uring_enabled(IsIouringEnabled()); LOG(INFO) << "Userspace snapshots enabled"; } else { is_snapshot_userspace_ = false; LOG(INFO) << "Userspace snapshots disabled"; } // Terminate stale daemon if any std::unique_ptr<SnapuserdClient> snapuserd_client = SnapuserdClient::Connect(kSnapuserdSocket, 5s); if (snapuserd_client) { snapuserd_client->DetachSnapuserd(); snapuserd_client->CloseConnection(); snapuserd_client = nullptr; } // Clear the cached client if any if (snapuserd_client_) { snapuserd_client_->CloseConnection(); snapuserd_client_ = nullptr; } } else { bool userSnapshotsEnabled = true; const std::string UNKNOWN = "unknown"; const std::string vendor_release = android::base::GetProperty( "ro.vendor.build.version.release_or_codename", UNKNOWN); // No user-space snapshots if vendor partition is on Android 12 if (vendor_release.find("12") != std::string::npos) { LOG(INFO) << "Userspace snapshots disabled as vendor partition is on Android: " << vendor_release; userSnapshotsEnabled = false; } userSnapshotsEnabled = (userSnapshotsEnabled && !IsDmSnapshotTestingEnabled()); status.set_userspace_snapshots(userSnapshotsEnabled); if (!userSnapshotsEnabled) { is_snapshot_userspace_ = false; LOG(INFO) << "User-space snapshots disabled for testing"; } else { is_snapshot_userspace_ = true; LOG(INFO) << "User-space snapshots enabled for testing"; } } } if (!WriteSnapshotUpdateStatus(lock.get(), status)) { LOG(ERROR) << "Unable to write new update state"; return Return::Error(); } created_devices.Release(); LOG(INFO) << "Successfully created all snapshots for target slot " << target_suffix; return Return::Ok(); }解析王法
最新发布
07-24
LOG(ERROR) << "Cannot write target metadata"; return Return::Error(); } ``` - 将目标元数据写入到目标槽位的超级分区中。 #### 11. 保存当前元数据（如果启用压缩） ```cpp if (cow_creator.compression_...
Win10 + Qt Creator + Android：如何build一个项目
Something and Nothing
05-17 3729
本文创建于2019年5月。 Qt在更新，Android 开发的各种kits在更新，一切都在更新，于是不可避免地，很多资料都过时了。比如SDK不再提供GUI服务，只提供命令行模式；又比如NDK R19C版本似乎不支持C/C++ Clang……博主尝试用Qt Creator在安卓虚拟机上编译运行项目，遇到了很多问题，因而在此依此记录，如果有人碰到类似的问题，可以参考。 相关环境 NDK： up...
How to Use WinUSB to Communicate with a USB Device
Ilovejiuer的专栏
12-05 2642
How to Use WinUSB to Communicate with a USB Device March 30, 2009 Abstract Independent hardware vendors (IHVs) who manufacture USB devices must often provide a way for applications to access the devic
ios a build only device cannot be used to run this target
帅帅的博客
03-26 643
干开发这么久了，光看别人写技术博客了，自己反而一篇都没写过，愧对做程序这么多年了，从今天起记录自己开发中遇到的问题 解决办法
Xcode运行时，出现“xcode cannot run using the selected device”问题解决方法
般若的BLOG
03-18 1256
今天Xcode运行时，总是出现xcode cannot run using the selected device警告，这种情况以前也遇到过，今天又遇到，想了好久忘了解决方法，网上搜索好多解决方法，解决不了，浪费好长时间！ 现在终于想起来了，趁现在在脑袋里还热乎着，还是记录下来吧！好记性不如烂笔头！ 首先，点击项目名称查看警告列表，如图， 出现Missing "Dufault-568
Xcode cannot run using the selected device
Langeldep的专栏
04-15 4634
网上下载的第三方的xcode工程， 编译提示错误， 如图所示
Xcode cannot run using the selected device的解决办法
Louis__2014的专栏
06-18 1085
Xcode cannot run using the selected device.这个问题有一些是因为真机
Error:Cannot build artifact
天生卷发
06-03 2029
项目将上前，给项目打的war包重新编辑别名。我用的maven自动打包，clean，package都没问题。但是idea上启动项目报异常：Error:Cannot build artifact 'ghostPlanner:war exploded' because it is included into a circular dependency (artifact 'ghostPlanne...
Runscript：高效项目构建与运行管理工具
从标签“build-tool runscript script-manager Rust”中我们可以得知，runscript是一个构建工具，它与脚本管理有关，是由Rust语言开发的。Rust是一种系统编程语言，它以安全和并发性而闻名，所以runscript利用Rust来...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值