A:当你用私钥加密时它被称为 siging, 之后用公钥解密的过程称为 verify signature.
Why are you encrypting with the private key? When you encrypt with the private key, that is considered signing not encrypting, becuase it provides no confidentiality. If you want to “encrypt” with the private key, look into data signing, and that should allow you to “encrypt” (read “sign”) with the private key and “decrypt” (read “verify signature”) with the public key.
pod install --verbose, 安装报了上面的错误。工程是一个公共库，之前都是好的，它依赖了一个私有版本的 JSONModel,这本来也没什么问题，居然报出这么一错误，挺奇怪的。按提示先显示指定版本，依旧报错，看来并不是这个原因；又运行
pod update JSONModel,有输出安装私有版本的 JSONModel 的日志，问题解决。不过不清楚为什么会出这种很诡异的问题。
3.What is the use of entitlements.plist file?
Entitlements confer specific capabilities or security permissions to your iOS or macOS app.
- The entitlements file defines certain capabilities of your app. Usually, the file is automatically generated by Xcode when you enable a capability for your app.
- You only need the file if you enable certain capabilities, e.g. Healthkit integration. If you’d like to use these features, you have to add it. Otherwise, Apple will reject your app.
- You can name the file like you want. You can also rename it as long as the build settings point to the correct file name for it.
4.A valid provisioning profile for this executable was not found
A:Because Xcode compain about provisioning profile, so I decide to check the installed profiles on device, detail instructs are Window > Devices and Simulators > Select your device > right click > Show Provisioning Profiles…; Yes, no profile is here. It looks like we should mannual install one.
Where is the provisioning profiles Xcode managed? We can locate it by a simple way:Show project navigator > Select your project > General > Signing > Click info button follow Provisioning Profile > Drag the profile icon in popup menu to terminal. One of my profiles is :
/Users/dongmeiliang/Library/MobileDevice/Provisioning\ Profiles/1923e84f-743b-4453-8876-9763596ad09b.mobileprovision , My Xcode version is 10.1 (10B61).