Downloaded and installed iOS 16.4 beta and trying to recompile app projects using Xcode 14.2 on macOS Monterey.
Getting error message: 'Failed to prepare the device for development. This operation can fail if the version of the OS on the device is incompatible with the installed version of Xcode. You may also need to restart your Mac and device in order to correctly detect compatibility.'
Unable to download Xcode 14.3 beta for testing because it requires macOS Ventura 13.0 or later.
Do not have a current Mac device available to install macOS13.
Will there be a revision to Xcode 14.2 to enable compilations and testing of apps using devices running the iOS 16.4 releases?
Does anyone know?
Please advise.
Thank you.
Post
Replies
Boosts
Views
Activity
Need a minimum of 9.0., as available with current Xcode Version 13.4.1 (13F100).
Is this a new restriction by design or a flaw in Xcode Version 14.0 beta 4 (14A5284g)?
Anyone knows the answer?
Please advise.
Thanks,
D.J
Used to be able to assign a Live Photo as a new Wallpaper showing the static and video image prior to iOS 16. The beta version of iOS 16.0 accepts the Live Photo as a static image only.
Not sure if this is a bug in the current prerelease or a permanently dropped feature.
Anyone else observed this issue?
Compiled existing app (ObJective-C) with XCode Version 13.0 beta 5 (13A5212g) without any source code changes. Tested on iPhone XR running iOS 15 beta 7(19A5337a) and noticed that the PDFKit Instance Method 'insertPage:atIndex:' generates incorrect results when appending multiple pages from input .pdf files into one consolidated output .pdf.
The resulting output .pdf contains the total number of pages appended. However, all pages following the second page are a copy of the second page.
Compiling the identical app with Xcode Version 12.5.1 (12E507) and running on another iPhone XR with iOS 14.7.1 does work as expected. The app also works as expected on iOS releases prior to version 14.6.
Downloading the app from the App Store and executing it on the Phone with iOS 15(beta) shows the same issue.
Has anyone experienced a similar problem using iOS 15 (beta) and found a solution. Any recommendations, including from Apple, are welcome. Thanks, DJ
Compiled existing app with XCode Version 13.0 beta (13A5154h) without any source code changes and tested on iPhone XR running iOS 15 (beta) and noticed that the Device Proximity sensor features quit working.
Compiling the identical app with Xcode Version 12.5 release (12E262) and running on another iPhone XR with iOS 14.6 does work as expected. The app also works as expected on iOS releases prior to version 14.6.
Also, downloading the app from the AppStore and executing it on the Phone with iOS 15 (beta) shows the same issue.
Has anyone experienced a similar problem using iOS 15 (beta) and found a solution.
Any recommendations are welcome.
Thanks, DJ
After many months of being listed on the App Store, the latest version of an app was rejected because the App Preview video (unchanged) does now not meet current publication guidelines.I am trying to proceed with the app review without any App Preview video. However, there is no method under the app entry in the App Store Connect to enable for the modification/deletion of the App Review metadata causing the rejection. As a matter of fact, only the screen shots are shown, but no App Preview metadata.I have already resubmitted the app for review multiple times with explanations and received repeated rejects for the same reason, showing the pages of the App Preview which are causing the disapproval.I noticed that the App Preview will not show when the currently pubished version is displayed using the App Store app on a device running iOS 13.x. However, when the app is displayed using App Store on an iPad running iOS 9.3.5, the App Preview video is made available.So the video is out there somewhere but not accessible for me as the developer to edit the associated metadata in order to remove the App Preview video.Has anyone else experienced this issue, or does anyone maybe know what I am missing in order to take appropriate steps so progress can be made with the app approval process.?Any suggestions would be most welcome.