User Profile

We are in the midst of testing camera and photo/video access using iPadPro 17 Beta (21A5326a) from within our application, and we are encountering an error message on only one device (iPad Pro 12.9-inch, A2229). Full access to the camera roll has been explicitly granted to the application when prompted. On only the above device, attempting to select an existing photo results in this error popup: "Photo or Video Unavailable: This app is using the Photos picker in an unsupported configuration." (We are able to take and save new photos from within our application on this device with no issues.) I have a second device on hand (iPadPro 10.5-inch, A1701) that presently also has the same iPadOS version installed and is running the same application, and we are able to select existing photos and take new photos with no errors. I have compared the Photos settings on both devices, and they appear to be identical. On a third iPad device running with the same iPadOS version, application, and Photos settings (that device is not in my possession), it has been reported that no errors are encountered when either taking new photos or selecting existing photos via the Photo Picker from within our app. We are trying to figure out what might be causing this error to appear when selecting existing photos on only the A2229 device, and/or what aspect of the configuration or settings would need to be modified in order to use the photo picker on that one iPad Pro. This issue had not been encountered on the A229 device while running with iPadOS 16. Searching the text of this error message online has not returned anything significantly meaningful thus far.

During our testing of iPadOS 17 Beta 4 and now 5, we have observed that DateTime objects appear to be initialized differently from what we had seen in iPadOS 16. Presently, we are running Xcode 14.3.1 with Xamarin.iOS v16.0.0.72, in Visual Studio for Mac 2022 v17.6.3 on a MacBook running Ventura 13.3.1 (although several combinations of different versions of these components have not resolved the issue). Examples of what we are seeing when creating DateTime variables: In iPadOS 16, a typical DateTime (ToString()) shows as "7/27/2021 4:49:10 PM". In iPadOS 17 Beta, the same DateTime shows as "7/27/2021 4:49:10 a". A subsequent DateTime.Parse operation on the iPadOS 17 string leads to a "Format_UnknownDateTimeWord" exception in our application. The behavior is the same whether we are operating on a DateTime value from a database, or even just when creating a new DateTime object in code from scratch. Is this an expected behavior in iPadOS 17, or is it a known issue that is expected to be resolved in a future iPadOS 17 Beta release, and/or Xcode / Xamarin.iOS update? We would like any feedback or suggestions on whether others have encountered the same behavior in iPadOS 17 Beta, and how this should be addressed if it is the new expected behavior.