Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2018.2.X
Votes
0
Found in
2018.1.0a5
2018.2.0a3
2018.2.0a8
Issue ID
1024859
Regression
Yes
[iOS] "No certificate for team ' ' matching iPhone Development found" using manual signing
Reproduction steps:
1. Create a new project.
2. Switch platform to iOS in the Build Settings.
3. Go to Player Settings.
4. Uncheck the 'Automatically Sign' checkbox.
5. Set Bundle Identifier.
5. Input 'Signing Team ID' (Tested ID provided in the edit below).
6. On the right of 'iOS Provisioning Profile' Click 'Browse'.
7. Navigate and select a provisioning profile (Tested with '~/Library/MobileDevice\Provisioning Profiles').
8. Set 'Profile Type' to 'Development'.
9. Go to Build Settings and click 'Build and Run'.
Actual behavior:
- Xcode build fails with error messages:
= 2018.2.0a3 - 2018.2.0a8:
No certificate for team '' matching 'iPhone Development' found
Select a different signing certificate for CODE_SIGN_IDENTITY, a team that matches your selected certificate, or switch to automatic provisioning.
Provisioning profile "iOS Team Provisioning Profile: com.Company.ProductName" is Xcode managed, but signing settings require a manually managed profile.
= 2018.1.0a6 - 2018.1.0f1, 2018.2.0a1 - 2018.2.0a2:
Provisioning profile "iOS Team Provisioning Profile: com.Company.ProductName" is Xcode managed, but signing settings require a manually managed profile.
Not reproducible with:
2018.1.0a5
Note:
- It may be 2 separate issues.
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
matbean
Jul 18, 2018 16:12
Same issue in 2018.1.0f2
pajamajama
Jun 19, 2018 20:58
Same issue in 2018.1.5