Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?

We are no longer getting a different value for trueHeading vs magneticHeading with the new ipad pro 6th generation M2 device. The M1 iPad Pro works and other iPad and iPhone devices work fine. Apple told one of our users that we need to update our app - but we did only 4 weeks ago. Has something changed to the use of the CLHeading api for the M2 chip?

We are using the apple sample Streaming an AR Experience app ( https://developer.apple.com/documentation/arkit/streaming_an_ar_experience ) to share an AR experience between an iPhone and iPad. This works fine over a local Wifi network but it never gets to connected over Bluetooth (Wifi turned off on both devices and devices connected over Bluetooth). Over bluetooth it gets to connecting state receiving the invite in didReceiveInvitationFromPeer which is handled but then never gets any further and eventually timesout. [GCKSession] Not in connected state, so giving up for participant [7DB7CDF8] on channel [0] ..... [GCKSession] Not in connected state, so giving up for participant [08E02193] on channel [7]. Is anyone else able to get this working over Bluetooth on iOS15? Is there a new permission that has to be added?

Our app built with Xcode 11 works fine on iOS15 with custom map tiles. We are now building and running it using the latest version of Xcode 13 and we have a serious problem with the custom map tiles flashing in an ugly way every time we try to update an annotation or move the map. It flashes bits of the apple map behind the already displayed tiles. Two screenshots are attached from a video capturing the flashing change in state from the normal map to the map with lots of tiles missing when a map annotation was updated. Is this a known bug with MKTileOverlay and Mapkit in iOS15 and is there a work around or fix? This behaviour is also present if we run the app on Mac OS12 on a Macbook M1Pro

Since upgrading to iOS15 the custom tile overlays on our maps are flickering There is an example of the problem here:- https://www.frso.se/cachly_tile_maps.mp4 Is this a known iOS 15 bug? When will it be fixed?

Is there a way us developers can lend our support to Tim Cooke and Apple’s fight against the European Digital Markets Act and the dangers it poses to both our users and us as developers?