Xcode 15 doesn't fix Info.plist management bugs introduced in Xcode 14

Xcode 14 introduced some ridiculous Info.plist management bugs which are not yet fixed in Xcode 15:

The bugs are manifested in the General and Info tabs of target management:

-The Build value in the General tab is not in sync with the CFBundleVersion value in the Info tab (that is, changing the value in the General tab won't affect the Info tab and vice versa).

-The App Category value in the General tab isn't in sync with the LSApplicationCategoryType value in the Info tab.

-Additional document type properties in the Info tab cannot be added: clicking "Click here to add..." doesn't do anything.

-Document types in Info tab cannot be deleted: once you added a document type instance (even as a test) there's no way to remove it.

Up vote post of Leo Braun Down vote post of Leo Braun
1.4k views
Posted by
Leo Braun
Reply
Add a Comment

Replies

...and none of this is fixed in the Xcode 15.0 release.

The first bug (Build value) affects EVERY Xcode user.

I find it astonishing that Apple refuses to address such glaring deficiencies in fundamental Xcode functionality. Especially something that should be trivial to fix.

Posted by
Leo Braun
Up vote reply of Leo Braun Down vote reply of Leo Braun

  • This comment is added on Apple's request to test a forum notification bug.

    —
    Leo Braun

  • This comment is added on Apple's request to test a forum notification bug.

    —
    Leo Braun

  • Notification test.

    —
    App Store Connect Engineer
Add a Comment

And here we are: still NONE of the issues are fixed in Xcode 15 beta 4.

Once again, some of them (such as build number mismatch) affects ALL Xcode users - 100% of them.

It's unfathomable how Apple managed to break Info.plist management in Xcode 14 (something that worked with no issues since the first Xcode release).

It's even harder to understand why they still refuse to fix it while, once again, this affects ALL Xcode users.

I encourage every Xcode user to submit a bug report regarding this severe problem as soon as possible.

Maybe Apple pays attention to this once they receive a few hundred reports on this bug.

Posted by
Leo Braun
Up vote reply of Leo Braun Down vote reply of Leo Braun
Add a Comment