-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS] Set provisioning style for both iPhone Developer
and iPhone Distribution
to automatic
#86748
Conversation
I don't think there's anything strange with the |
It's probably better to change these two lines to keep mode to godot/platform/ios/export/export_plugin.cpp Lines 230 to 231 in fbaab3c
|
I don't think it's a good idea to expect the game developer to have a
It's definitely an improvement, I will do as you said, what about changing the default of release to |
Then just change it? It's not a forced name, the default should be that you use a different identity for release, for security etc., does it not work by changing manually? The default assumption should be that you do it for production according to general recommendations IMO, much harder to do it wrong by accident (or rather, to realize or remember that, not that you should keep them as is), but still possible to change if you want to do differently |
If I change it, then as I mentioned in the original post
That's why I'm asking "what about it?" with a question mark in the end which means other than agreeing with "what is said", I'm suggesting something new which is changing the default for "Code Sign Identity Release" filed to "iPhone Developer" instead of "iPhone Distribution". The rational behind this suggestion is people may not have created a distribution profile and they may don't know by typing "iPhone Developer" in "Code Sign Identity Release" field. |
I missed a detail and therefore removed that part of my note 🙂 I think the solution, as suggested above, should be to handle that case, not to change the default 🙂 To me it sounds like the check should involve both vases, so it uses automatic for both "Developer" and "Distribution", but keep the default values, that's at least what I'd suggest as a solution here |
Sorry, I didn't notice you have edited 🙂 Btw I really appreciate your quick responses. So I will just make it keep |
No worries, easy to miss 🙂 |
I updated this pull request, please review it when you got the time. |
@AThousandShips @bruvzg Sorry to ping you, since last time you responded in less than 5 minutes, I thought maybe you haven't noticed yet PR is updated. |
…bution" to automatic
iPhone Developer
and iPhone Distribution
to automatic
Thanks! And congrats for your first merged Godot contribution 🎉 |
Cherry-picked for 4.2.2. |
@akien-mga Hello! Sorry to bother, can we get this cherry picked for 3.x too? Thanks! |
Related: #57195
I think it should work with development certificate by default (both for debug and release builds)
I do have a distribution certificate and yet I keep getting this error: in
Signing & Capabilities
tab of the target in Xcode:... is automatically signed for development, but a conflicting code signing identity iPhone Distribution has been manually specified. Set the code signing identity value to "Apple Development" in the build settings editor, or switch to manual signing in the Signing & Capabilities editor.
If I replace these two lines in
project.pbxproj
file:to
things start to work, you may say you can set it in the Godot export wizard for iOS template, but the thing is as soon as I set a value for code sign identity, the
export_plugin.cpp
will setCODE_SIGN_STYLE
toMANUAL
instead ofAUTOMATIC
and it also causes an error in Xcode build. The only way things work is whenCODE_SIGN_STYLE
is keptAUTOMATIC
and the above lines are changed. so there is no way I'm aware of that I (and I guess the people who commented on that issue and probably others) can get a working export out of the box using the export dialog, and the ipa file generation always fails.If this PR is not accepted, please explain in details what's going on here, what kind of certificates the developer needs to setup on their machine, what configuration is needed to make it work without this PR merged. If it is not officially documented, it needs to at least be mentioned in a GitHub thread somewhere so that a Google Search finds something. The iOS deployment code is helpful if it works smoothly for people other than the one who implemented it, and it needs documentation for this purpose.