Bug Error when building in 2022.3.5

This looks like a more general bug as I've seen it with other add capability calls since updating to 2022.3.5 but here it's coming directly from the In App Purchasing build code so though I'd mention it.

WarningException: This capability has already been added. Method ignored
UnityEditor.iOS.Xcode.PBXProject.AddCapability (System.String targetGuid, UnityEditor.iOS.Xcode.PBXCapabilityType capability, System.String entitlementsFilePath, System.Boolean addOptionalFramework) (at <ca5baea5210f43dba4e79596749d3a36>:0)
UnityEditor.iOS.Xcode.ProjectCapabilityManager.AddInAppPurchase () (at <ca5baea5210f43dba4e79596749d3a36>:0)
UnityEditor.Purchasing.AppleCapabilities.AddInAppPurchasingCapability (System.String projPath, UnityEditor.iOS.Xcode.PBXProject proj) (at ./Library/PackageCache/com.unity.purchasing@4.9.3/Editor/AppleCapabilities.cs:45)
UnityEditor.Purchasing.AppleCapabilities.OnPostprocessBuildForApple (System.String path) (at ./Library/PackageCache/com.unity.purchasing@4.9.3/Editor/AppleCapabilities.cs:35)
UnityEditor.Purchasing.AppleCapabilities.OnPostprocessBuild (UnityEditor.BuildTarget buildTarget, System.String path) (at ./Library/PackageCache/com.unity.purchasing@4.9.3/Editor/AppleCapabilities.cs:25)
UnityEditor.Purchasing.AppleCapabilities.OnPostprocessBuild (UnityEditor.Build.Reporting.BuildReport report) (at ./Library/PackageCache/com.unity.purchasing@4.9.3/Editor/AppleCapabilities.cs:19)

 

I'm getting the same issue, but mine is coming from a custom post processing script. I'm doing something like this to suppress it:

Code (CSharp):

1.  
2. //Add GameCenter capability
3. try
4. {
5.     Logging.Log($"Adding GameCenter capability to target {targetGUID}");
6.     project.AddCapability(targetGUID, PBXCapabilityType.GameCenter);
7. }
8. catch (Exception e)
9. {
10.     //Since Unity 2022.3.5f1 AddCapability() throws an exception which breaks builds (even though it's supposed to
11.     //be a warning only). So we catch it here and only throw it up the chain if it isn't a warning type.
12.     if (e is System.ComponentModel.WarningException)
13.     {
14.         Debug.LogWarning($"WarningException: {e.Message}");
15.     }
16.     else
17.     {
18.         throw e;
19.     }
20. }

Obviously I guess you can't easily edit Unity's IAP code to add this, but if you're adding the capability yourself in your own post process script (which I assume you are, hence the error) then maybe you could do something like the above instead?

It's a bit of a pain that they are making breaking changes like this in a point release... Unity is a nuisance these days.

Ben

 

@Wriggler I didn't see this under 2022.3.3 and also my colleague is using that and is not getting this issue so it seems to be something that's made it's way into .4 or .5.

 

Same here. I just upgraded from 2022.3.3f1 and wasn't getting it then.

Ben

 

Same here. Happening when using append during iOS build, replace works fine.

 

Yup! Command+B (for build&run) doesn't work, but manually Going to Build Settings -> Build and Run -> Replace works for me.

 

Getting this with 2022.3.7f1 "LTS". As others have said, replace works, but this is no good as it overwrites my info.plist and XCode project settings.

 

Holy s***...I moved from 2022.3.4 bugs to 2022.3.7 for what?! Can you Unity "developers" team asnwer me? To get another critical process breaking bug?
That's absolutely insane

I have the same logs as @andymads provided.
Yes, project replace "works", but of course we can't consider it as a working solution by a known reasons.

Btw, did someone created a bug report? Forum threads doesn't work to force that lazy machine to fix it. Each thread will be finished with the words "please submit a bug report". Proofed by a time.

If somone created a bug report, please share link, let's vote on.

 

@novaVision I submitted a bug report yesterday from 2022.3.7.

It's annoying that none of the Unity folks here have replied.

 

wanted to just chime in and report that I've also experienced this, however leezak5555's solution worked perfect for me (oddly enough).

 

Has there been any update on this? Having to completely re-do all my build settings every time I deploy on iOS is absolutely ridiculous for a "long term support" release.

 

2022.3.8 was out, but no fix there, as expected

 

This is ridiculous, just coming from this issue https://forum.unity.com/threads/crash-in-pbxprojectdata-writetostring.1465076/ where we were blocked on upgrading from anything above 2022.3.3f1 and had to deal with various editor crashes meanwhile. Was now able to implement the hack in the above thread and am now getting these new issues on incremental builds...

We upgraded to 2022 because it was considered LTS. It is absolutely unacceptable that LTS patch releases breaks these many thing, another hack to the post process scripts.. I hope the Unity team can consider this feedback and be more defensive with changes in the future.

 

This topic were just ignored by Unity "support" team. Let me remind it been started on July 24th!

 

@jwtan_unity When will 2022.3.10 be out?