We have a bit of a complicated build process and need to build the Widget outside of our main app and repackage since we are using a cross platform framework. I tried scripting out updating my Widget's Marketing Version but agvtool won't update the MARKETING_VERSION in the project.pbxproj file. Therefore, we end up getting these emails from Apple: ITMS-90473: CFBundleShortVersionString Mismatch - The CFBundleShortVersionString value ‘1.2.2’ of extension ‘MyiOSApp.app/PlugIns/widgetExtension.appex' does not match the CFBundleShortVersionString value ‘1.2.3' of its containing iOS application ‘MyiOSApp.app'. I run this and it says it's updating in the Widget plist (but not the project.pbxproj) so when I build with xcode via command line it doesn't update and when we submit to the App Store we get the above message from Apple: /usr/bin/agvtool new-marketing-version $(/usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString" ../My.Crossplatform.App/My.Crossplatform.App.iOS/Info.plist) Setting CFBundleShortVersionString of project ios to:    1.2.3. Updating CFBundleShortVersionString in Info.plist(s)... Cannot find "ios.xcodeproj/../YES" Updated CFBundleShortVersionString in "ios.xcodeproj/../widget/Info.plist" to 1.2.3 I've had to resort to manually updating then submitting every time. What is the correct way to update the MARKETING_VERSION in the project.pbxproj file in a CI environment using bash?

Strong Password suggestion works just fine from a developer signed app on a development device. However, when we try to send it to QA for testing with our ad-hoc signed or even from TestFlight our distribution signed app, the Strong Password feature doesn't present itself. Our AASA file is up in production and is captured by the Apple CDN. Our associated domains entitlement has for example: webcredentials:*.mydomain.com Again, this works in development (did not need to use ?mode=developer) and our AASA file is up in production. Has anyone had issues testing the Strong Password or any Associated Domain feature in TestFlight?

https://developer.apple.com/app-store/user-privacy-and-data-use/ User Privacy and Data Use - App Store - Apple Developer ”With iOS 14.5,iPadOS 14.5, and tvOS 14.5 and later, you’re required to ask users for their permission to track them across apps and websites owned by other companies.” Seems odd that macOS isn’t mentioned but that you have to disclose in a privacy nutrition label the usage. Can someone from Apple reply so we know what we have to do when updating our old Mac App? Thanks.

We have an iOS app that loads up custom documents. We allow pagination through bluetooth pedal controllers which pose as a bluetooth keyboard/mouse that send left/right or up/down to paginate. The way we were doing this before is via UIKeyCommand on overriding the KeyCommands property and becoming first responder. This worked great up to iOS 15.0. Our fix was then to override presses began on iOS 15.0 and that worked except some customers (new devices with iOS 15.1 it seems) have "Full Access Keyboard" turned on by default. We have also tried setting wantsPriorityOverSystemBehavior to true. What is happening is that left/right or up/down highlights elements on our view but we just want it to paginate as that's what most customers would expect, especially the ones using bluetooth pedals. How do I force left/right or up/down to just paginate our documents instead of highlighting UI elements when Full Access Keyboard in accessibility is turned on?

So I've already been able to do this for a different Mac M1. I don't know exactly how I got it to show up other than added the device to the Device list and then I was able to select the device when I go into the Provisioning Profile. No problems, but then I tried doing this for another M1 device (macbook) and for the life of me I can't get it to show up so I can select it in the Provisioning Profile. I've already added it to the Device list and even successfully created developer and distribution certs from it after logging in with a developer account different than before since this is a different developer's laptop I was walking him through. The original account I used has "admin" role. Could that be the difference? "Include Mac Devices" is toggled on in the Provisioning Profile.

We have been testing IAP Consumable using sandbox against our internal Dev server. We would like to test consumables against prod/live but understand that the consumables need to go through the approval process. Consumables are new to our app. Can this happen in test flight to allow external users to test without releasing? Has anybody submitted a new binary (with no change) just to get consumables approved before releasing code which used the consumables? If not, do we wait to submit with the update to the app which will use consumables, wait for approval, then don't release and test in test flight? Again, we have been testing internally using sandbox but want external users to test against production/live without releasing the app to the public. Thanks!