You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am integrating a "today extension" into our app, and I noticed some funky behavior with the Swift version not being set correctly by this plugin.
I believe this is because this plugin is treating build names (e.g. Debug, Release) as unique. However, in the scenario where a project has multiple targets, there can be multiple Debug/Release sections in the build target section. This plugin uses xcodeProject.getBuildProperty which will use the last reference found for a given build name.
The result is that Swift version will not get set properly on all targets if the last build section already has it set. Example section below shows the last 2 sections already have SWIFT_VERSION set (these are for the today extension). When this plugin runs it will not add SWIFT_VERSION for the other build sections (they are initially unset and remain unset).
I am integrating a "today extension" into our app, and I noticed some funky behavior with the Swift version not being set correctly by this plugin.
I believe this is because this plugin is treating build names (e.g. Debug, Release) as unique. However, in the scenario where a project has multiple targets, there can be multiple Debug/Release sections in the build target section. This plugin uses
xcodeProject.getBuildProperty
which will use the last reference found for a given build name.The result is that Swift version will not get set properly on all targets if the last build section already has it set. Example section below shows the last 2 sections already have
SWIFT_VERSION
set (these are for the today extension). When this plugin runs it will not addSWIFT_VERSION
for the other build sections (they are initially unset and remain unset).The text was updated successfully, but these errors were encountered: