I'm having the same issue, did you find a solution?

Hello! There is actually a way to run an iPhone 8 simulator (or other models) using Xcode 14 and iOS 16. To do this you just have to open Xcode > Window > Devices and Simulator. When the window appears you can just tap on the "Simulator" tab and on the "+" button. From here you can choose "iPhone 8" as for the Device type and also the OS version. Here is some screenshots that might help:

Hello, could you specify if you are getting an error from the compiler? Thank you!

By looking at the email your app is successfully unlisted. This means that regular users can't reach the app through a normal App Store search.

@srthploid, what's the error (if any) reported by the compiler?

Hello! This is definitely something possible with the MapKit Framework. Probably it's not straightforward but possible! A couple of documentation you might find useful: MKDirections: You can use this class to get turn-by-turn directions from point A to point B. E.g. you can call let directions: MKDirections = .init(request: request) directions.calculate { handler in ... } MKLocalSearch: You can use this class to search for locations. Maybe the user search destinations through a search bar, you can use MKLocalSearch to get all the places like a city or a shop. MKMapView: You can use the MKMapView UIKit view to display the map itself and add annotations or turn-by-turn directions in it. Hope this answer your question!

Hello. I'll try to address the error reported by the compiler first. As stated on Apple List documentation the List type should conform to Identifiable. This is done as SwiftUI needs to know how to identify each and every cell in our list in order to optimize it and perform any operation like displaying, removing cells. That being said it seems by the error you reported that multiple cells have the same id. This is not acceptable since by design the id needs to be different for each cell. This is so SwiftUI can understand which cell is which. I would advise to double-check that the id is different in each Artwork type. In the example below we assign a new unique UUID so that it's almost fully guaranteed that each cell have a different id: struct Artwork: Identifiable { let id = UUID() }

Hello! Have you tried Apple Search Ads its an easy and effective way to promote your app inside the App Store and eventually get more daily downloads

Hello, you can find an example of the implementation on the Apple Developer Documentation here: https://developer.apple.com/documentation/avfoundation/capture_setup/setting_up_a_capture_session/. If you scroll down you should be able to find the Display A Camera Preview section. Here is the example code: class PreviewView: UIView { override class var layerClass: AnyClass { return AVCaptureVideoPreviewLayer.self } /// Convenience wrapper to get layer as its statically known type. var videoPreviewLayer: AVCaptureVideoPreviewLayer { return layer as! AVCaptureVideoPreviewLayer } } self.previewView.videoPreviewLayer.session = self.captureSession

Hello, I've noticed the same thing on an iPhone 13 Pro Max and an iPad Air 4 both running iOS 16 Beta 1. I've opened a radar: FB10313246. I've tried different configurations but couldn't get it to work.

Same happened to me with an iPhone 12 Pro Max with iOS14.4 installed along with Xcode 12.4. The only solution that worked for me was restarting the iPhone. I've just opened a bug report FB9019586

Currently Apple Official UI Kits are not available, please file a feedback on http://feedbackassistant.apple.com requesting it. Thanks!!

Have you tried using a sample UIColor like UIColor.black? The only thing that comes to my mind is that iOS 12 doesn't handle dark mode and if your color is on the .xcassets with dark mode set maybe it gives it some problems

Hello, first of all have you tried with the delegate textViewDidChange? https://developer.apple.com/documentation/uikit/uitextviewdelegate/1618599-textviewdidchange Probably this is going to act the same as your Notification, but worth a try. Otherwise the only thing I would see is to use the shouldChangeTextIn and fixing the problem it has doing so: func textField(_ textField: UITextField, shouldChangeCharactersIn range: NSRange, replacementString string: String) -> Bool { 	 	 let	char = string.cString(using: String.Encoding.utf8)! 	 	 let isBackSpace = strcmp(char, "\\b") 	 	 var currentText = "" 	 	 if (isBackSpace == -92) { 			currentText = textField.text!.substring(to: textField.text!.index(before: textField.text!.endIndex)) 	 } 	 else { 			 currentText = textField.text! + string 	 } return true } This removes the backspaced string from your currentText as well as adds it if you have typed it in.

Hello, I think the best place to send Apple feedbacks is through their dedicated website: https://feedbackassistant.apple.com/welcome Thank you and I agree with what you are suggesting!