Plaase select at least one of the signature versions to use 问题的解决

最新推荐文章于 2024-07-27 22:54:34 发布
原创 最新推荐文章于 2024-07-27 22:54:34 发布 · 453 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了在进行应用签名过程中遇到的V2签名错误，并提供了解决方案。指出V2签名方式仅支持Android 7.0及更高版本，建议使用V1或V1+V2混合签名来确保兼容性。

签名时候遇到下面这个错误:


解决办法:



V2仅支持7.0及以上版本，不能在7.0以下版本手机上安装。签名时只勾选v2打的包（即生成的apk）安装时会提示“未安装”。通用签名方式：勾选v1或者v1+v2（v1和v2同时勾选）。

V1: 支持7.0 以上的手机!



Chrome的启动参数
Criss@陈磊
02-23 5938
List of Chromium Command Line Switches Condition Explanation --[1]⊗ Classic, non-material, mode for the |kTopChromeMD| switch.↪ --0⊗ Value of the --profiler-timing flag that will disable timin...
my cloud test bed (by quqi99)
技术并艺术着
03-10 2327
若容器里如果上不了网，如无法访问api.snapcraft.io，是因为lxd容易默认使用了eth1上的dns=10.10.10.1，下面的配置可让eth0, eth1, eth2都默认使用dns=192.168.99.1来避免特色网络对api.snapcraft.io的污染。下列netplan配置创建了br-eth0，也让br-eth0支持wol通过魔术包唤醒，也创建了一个没有dhcp的br-maas用于maas实验。
【android】Android Studio2.3打包提示Please select at least one of the signature versions to use
baidu_hxl的博客
08-22 4366
Android Studio2.3在打包过程中提示Please select at least one of the signature versions to use。
studio2.3.1中please select at least one of the signature versions to use及提示未安装
早有蜻蜓立上头
04-17 9491
android studio2.3.1版本打包签名时弹出提示please select at least one of the signature versions to use解决方式 需要勾选
R与RStudio的安装教程
weixin_54106682的博客
12-30 7252
R与RStudio详细安装教程
Android studio 3.0.1版本出现的问题： Please select at least one of the signature versions to use
那_个秋天的博客
11-27 1007
Please select at least one of the signature versions to use 请至少选择使用一个签名版本 V1：旧的签名方式，使用jar包V2：Android 7.0 引入一项新的应用签名方案 APK Signature Scheme v2，它能提供更快的应用安装时间和更多针对未授权 APK 文件更改的保护。打包时选择的签名版本时，要不就只选V1；要不就
Dockerfile出现GPG error: At least one invalid signature was encountered 进入死循环
wuyinmingyue的博客
10-14 3301
Dockerfile进行docker build的时候出现GPG error
GitLab and SSH keys Git is a distributed version control system, which means you can work locally, then share or "push" your changes to a server. In this case, the server is GitLab. GitLab uses the SSH protocol to securely communicate with Git. When you use SSH keys to authenticate to the GitLab remote server, you don't need to supply your username and password each time. Prerequisites To use SSH to communicate with GitLab, you need: The OpenSSH client, which comes pre-installed on GNU/Linux, macOS, and Windows 10. SSH version 6.5 or later. Earlier versions used an MD5 signature, which is not secure. To view the version of SSH installed on your system, run ssh -V. Supported SSH key types To communicate with GitLab, you can use the following SSH key types: ED25519 RSA DSA (Deprecated in GitLab 11.0.) ECDSA (As noted in Practical Cryptography With Go, the security issues related to DSA also apply to ECDSA.) Administrators can restrict which keys are permitted and their minimum lengths. ED25519 SSH keys The book Practical Cryptography With Go suggests that ED25519 keys are more secure and performant than RSA keys. OpenSSH 6.5 introduced ED25519 SSH keys in 2014 and they should be available on most operating systems. RSA SSH keys Available documentation suggests that ED25519 is more secure than RSA. If you use an RSA key, the US National Institute of Science and Technology in Publication 800-57 Part 3 (PDF) recommends a key size of at least 2048 bits. The default key size depends on your version of ssh-keygen. Review the man page for your installed ssh-keygen command for details. See if you have an existing SSH key pair Before you create a key pair, see if a key pair already exists. On Windows, Linux, or macOS, go to your home directory. Go to the .ssh/ subdirectory. If the .ssh/ subdirectory doesn't exist, you are either not in the home directory, or you haven't used ssh before. In the latter case, you need to generate an SSH key pair. See if a file with one of the following formats exists: Algorithm Public key Private key ED25519 (preferred) id_ed25519.pub id_ed25519 RSA (at least 2048-bit key size) id_rsa.pub id_rsa DSA (deprecated) id_dsa.pub id_dsa ECDSA id_ecdsa.pub id_ecdsa Generate an SSH key pair If you do not have an existing SSH key pair, generate a new one. Open a terminal. Type ssh-keygen -t followed by the key type and an optional comment. This comment is included in the .pub file that's created. You may want to use an email address for the comment. For example, for ED25519: ssh-keygen -t ed25519 -C "<comment>" For 2048-bit RSA: ssh-keygen -t rsa -b 2048 -C "<comment>" Press Enter. Output similar to the following is displayed: Generating public/private ed25519 key pair. Enter file in which to save the key (/home/user/.ssh/id_ed25519): Accept the suggested filename and directory, unless you are generating a deploy key or want to save in a specific directory where you store other keys. You can also dedicate the SSH key pair to a specific host. Specify a passphrase: Enter passphrase (empty for no passphrase): Enter same passphrase again: A confirmation is displayed, including information about where your files are stored. A public and private key are generated. Add the public SSH key to your GitLab account and keep the private key secure. Configure SSH to point to a different directory If you did not save your SSH key pair in the default directory, configure your SSH client to point to the directory where the private key is stored. Open a terminal and run this command: eval $(ssh-agent -s) ssh-add <directory to private SSH key> Save these settings in the ~/.ssh/config file. For example: # GitLab.com Host gitlab.com PreferredAuthentications publickey IdentityFile ~/.ssh/gitlab_com_rsa # Private GitLab instance Host gitlab.company.com PreferredAuthentications publickey IdentityFile ~/.ssh/example_com_rsa For more information on these settings, see the man ssh_config page in the SSH configuration manual. Public SSH keys must be unique to GitLab because they bind to your account. Your SSH key is the only identifier you have when you push code with SSH. It must uniquely map to a single user. Update your SSH key passphrase You can update the passphrase for your SSH key. Open a terminal and run this command: ssh-keygen -p -f /path/to/ssh_key At the prompts, type the passphrase and press Enter. Upgrade your RSA key pair to a more secure format If your version of OpenSSH is between 6.5 and 7.8, you can save your private RSA SSH keys in a more secure OpenSSH format. Open a terminal and run this command: ssh-keygen -o -f ~/.ssh/id_rsa Alternatively, you can generate a new RSA key with the more secure encryption format with the following command: ssh-keygen -o -t rsa -b 4096 -C "<comment>" Add an SSH key to your GitLab account To use SSH with GitLab, copy your public key to your GitLab account. Copy the contents of your public key file. You can do this manually or use a script. For example, to copy an ED25519 key to the clipboard: macOS: tr -d '\n' < ~/.ssh/id_ed25519.pub | pbcopy Linux (requires the xclip package): xclip -sel clip < ~/.ssh/id_ed25519.pub Git Bash on Windows: cat ~/.ssh/id_ed25519.pub | clip Replace id_ed25519.pub with your filename. For example, use id_rsa.pub for RSA. Sign in to GitLab. In the top right corner, select your avatar. Select Preferences. From the left sidebar, select SSH Keys. In the Key box, paste the contents of your public key. If you manually copied the key, make sure you copy the entire key, which starts with ssh-ed25519 or ssh-rsa, and may end with a comment. In the Title text box, type a description, like Work Laptop or Home Workstation. Optional. In the Expires at box, select an expiration date. (Introduced in GitLab 12.9.) The expiration date is informational only, and does not prevent you from using the key. However, administrators can view expiration dates and use them for guidance when deleting keys. GitLab checks all SSH keys at 02:00 AM UTC every day. It emails an expiration notice for all SSH keys that expire on the current date. (Introduced in GitLab 13.11.) GitLab checks all SSH keys at 01:00 AM UTC every day. It emails an expiration notice for all SSH keys that are scheduled to expire seven days from now. (Introduced in GitLab 13.11.) Select Add key. 翻译一下
最新发布
07-04
### GitLab 与 SSH 密钥的配置 GitLab 是一个流行的 DevOps 平台，支持使用 SSH 密钥进行安全的身份验证。SSH（Secure Shell）是一种加密协议，允许用户通过不安全的网络连接到远程服务器并执行命令。...
Architecture of the Solana Validator
chengbin20101的博客
07-27 1077
Architecture of the Solana ValidatorClustersOverviewOverview of a Solana ClusterCreating a Cluster​Joining a Cluster​Sending Transactions to a Cluster​Confirming Transactions​Solana ClustersAvailable Solana ClustersDevnetTestnetMainnet BetaBenchmark a Clus
Puppeteer开发过程中遇到的问题及解决方案
m0_54849806的博客
02-21 8045
工欲善其事必先利其器，请先检查本机是否安装NodeJS环境以及查阅API： Google官方文档：https://developers.google.com/web/tools/puppeteer API（v12.0.1）文档：https://pptr.dev/#?product=Puppeteer&version=v12.0.1&show=outline 问题：如何处理各种验证码？ 解决方案：建议大家去搜索对应的解决方案，Puppeteer并无此类解决方案。 问题：某些网站做了JS防爬检测
fping
01-15
fping是一款很好用的网络诊断工具，可以对多个ip地址或地址段发送ICMP数据包进行诊断，是比os自带的ping工具要好用的一款工具
android studio打包签名错误please select the product flavors to build and sign
商务合作|问题讨论|交流学习 请联系作者微信，加微信请务必注明来意，博客主页有联系方式
03-06 5654
打包签名app 都选择完后 点击 Finish提示Please select the product flavors to build and sign这种情况看下 图中红线的地方 是不是没有点击选中，背景变为蓝色为选中状态。选中后再点击Finish即可解决。如果大家还有其他问题欢迎加入我的开发群讨论交流：开发一群：454430053开发二群：537532956...
Android studio 2.3版本出现的问题： Please select at least one of the signature versions to use
追梦赤子心
05-08 9074
Please select at least one of the signature versions to use请至少选择使用一个签名版本 V1：旧的签名方式，使用jar包 V2：Android 7.0 引入一项新的应用签名方案 APK Signature Scheme v2，它能提供更快的应用安装时间和更多针对未授权 APK 文件更改的保护。 打包时选择的签名版本时，要不就只选V1；要不就V
安卓APK打包签名
热门推荐
xxdw1992的博客
09-08 1万+
上篇文章讲了打包签名问题，这边我来解释下。 key storepath:keystore文件路径 key store password :开启keystore文件的密码 key alias:key的别名 key password:key的密码 我们这里点击红色区域设置新的keystore如图： validity(years):这个keystore的有效期 从certifi......
Android studio 3.0 版本的出现的bug
那_个秋天的博客
11-24 2949
android-apt plugin is incompatible with future version of Android Gradle plugin. use ‘annotationProWarning:android-apt plugin is incompatible with future version of Android Gradle plugin. Please use ‘a
modelsim Unable to checkout a viewer license necessary for use of the Modelsimgraphical user interface
06-21
The error message "Unable to checkout a viewer license necessary for use of the ModelSim graphical user interface. Vsim is closing" typically indicates an issue with the licensing system of ModelSim. ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值