When I upgraded to iOS 18 beta, I don’t recall setting a screen time passcode, however one is set. I am locked out from changing the passcode. I have clicked “forgot passcode” down at bottom but it doesn’t do anything. I am the only user on this phone. I am currently running iOS iOS 18.2 (22C5125e). Please advise, as screen time is locked and cannot be viewed nor change passcode

Okay, so this seems like a silly thing to ask, but in the past couple days when I start up my ipad there is an icon or a button on the left hand side of the screen which is about the size of a regular icon. It only appears before pulling up the passcode screen for the first time and subsequently disappears. It seems to only appear when using one of the default solar system wallpapers. It is always mostly transparent but it changes color depending on which planet is being used eg reddish brown for Mars or yellowish brown for Saturn etc. it also moves position based on which wallpaper is being used. The button has no icon or any other features. Tapping on the button causes it to blink as if it was pressed, but nothing else happens. Just curious what this button or icon is.

I am making app which one of functionality is register user with firebase, but sometime when I register user I got app crash but user is added into db. I am getting error like this: EXC_BAD_ACCESS (code=2, address=0x2600000000) or adres = 0x10 which mean the is some memory leak but when I use instrumental leak every thing is ok. Second weird thing is that when I use instrumental leak I am not getting error (I added something like 40 users) but when I close instrumental and rebuilt I got crash in max 3 attempts. // FormComponent.swift // SpaceManager // // Created by Kuba Kromomołowski on 17/04/2024. // import Foundation import SwiftUI struct FormComponent: View { var isRegister: Bool = true @State private var repeatedPassword: String = "" @StateObject private var loginHandler = LoginViewModel() @StateObject private var registerHandler = RegisterViewModel() @EnvironmentObject var permissionViewModel: PermissionViewModel var body: some View { Form { TextField("Email", text: isRegister ? $registerHandler.email : $loginHandler.email) .textFieldStyle(RoundedBorderTextFieldStyle()) .font(.system(size: 25)) .multilineTextAlignment(.center) .autocapitalization(.none) .disableAutocorrection(true) SecureField("Hasło", text: isRegister ? $registerHandler.password : $loginHandler.password) .textFieldStyle(RoundedBorderTextFieldStyle()) .font(.system(size: 25)) .multilineTextAlignment(.center) .autocapitalization(.none) .disableAutocorrection(true) if (isRegister) { SecureField("Powtórz haslo", text: $registerHandler.repeatedPassword) .textFieldStyle(RoundedBorderTextFieldStyle()) .font(.system(size: 25)) .multilineTextAlignment(.center) .autocapitalization(.none) .disableAutocorrection(true) } BtnClearComponet(btnText: isRegister ? "Zarejestruj się" : "Zaloguj się", btnRegister: isRegister, action: { if isRegister { registerHandler.registerUser() { permissionViewModel.getPermission() } } else { loginHandler.userLogin() { permissionViewModel.getPermission() } } }, loginHandler: loginHandler, registerHandler: registerHandler ) .padding(.bottom, 5) } .frame(width:350,height:400) .scrollContentBackground(.hidden) .padding(.top, 50) } } // // RegisterViewModel.swift // SpaceManager // // Created by Kuba Kromomołowski on 03/05/2024. // import Foundation import Firebase import FirebaseAuth import FirebaseFirestore class RegisterViewModel : ObservableObject { @Published var email: String = "" @Published var password: String = "" @Published var repeatedPassword: String = "" @Published var isFail: Bool = false @Published var message: String = "" func registerUser(completion: @escaping () -> Void) { if(!validInput()){ return } Auth.auth().createUser(withEmail: email, password: password) { [weak self] res, err in guard let self = self else { return } if let err = err { self.isFail = true self.message = "Błąd przy rejestracji \(err.localizedDescription)" return } guard let userID = res?.user.uid else { return } // DispatchQueue.main.async { // print("Starting adding...") self.addIntoDatabe(userID: userID, email: self.email) // } completion() } } private func addIntoDatabe(userID: String, email: String) { let newUser = User(uid: userID, email: email, permission: Permission.Admin, itemReads: [["Prop":2]], numberOfAddedItem: 0, numberOfReadItem: 0) let db = Firestore.firestore() db.collection("users") .document(userID) .setData(["uid": newUser.uid, "email": newUser.email, "permission": newUser.permission.rawValue, "itemReads": newUser.itemReads, "numberOfAddedItem": newUser.numberOfAddedItem, "numberOfReadItem": newUser.numberOfReadItem]) print("User has been added into db") } }

I joined the waitlist for the early access as soon as I updated to the 18.2 beta, I’ve now installed the 18.2 beta 2 but still have no access. I can see the app when I swipe down the from the early access requested but it still closes the app straight away. Anyone else still having trouble getting access?

I’m a novice developer seeking insight from those more experienced. My goal is to buils an app UI platform for a streaming series and content + games tethered to a new crypto asset in development. I know this has been done on the App Store with products like Axie Infinity (Ronin/ETH currency) and am also looking over the Hedera white paper. Gaming is easily the most substantive case use for crypto currency, I’m just interested in what are the challenges to integration and if anyone has other examples or thoughts on the topic. Specifically tied to products developed for the Apple platform. What’s the playbook? cheers

Hello, After upgrading to iPad OS 18.1, Rest Finger To Open not working on my device - which is an 9th-generation iPad (10.2 inch) - anymore, now I have to actually press the Home button, only then I can unlock the screen with Touch ID. It was fine on iPad OS 17, where I just need to rest my finger on the Touch ID (or Home button) and it would unlock the device right away, no need to press. I'm sure all the required settings have been checked (please check out the screenshots). Not sure if anyone else is facing this. Hope it's not only me. Please take a look at this and fix it if it's a genuine issue. Thank you.

Dear Apple Developer Team, After installing the iOS 18.2 Beta, I encountered a language inconsistency in the iCloud interface. Although my system language is set to Traditional Chinese, the iCloud section in Settings now displays in Simplified Chinese. This issue only affects the iCloud page, as other sections retain the correct language setting. I kindly request that you address this issue by providing a fix, either through an executable update or an upcoming Beta release. A timely solution would help improve the beta experience for users who rely on specific language settings. Thank you for your attention.

Hello all, I’ve had the iOS 18 beta since it’s been available, but recently when I updated to iOS 18.2 beta 2 I’ve been experiencing random crashes and frozen screens. I can’t seem to find any common reason for it, as it’s seemingly random. My screen will turn black and show the loading icon like I’ve run out of battery before the screen turns back on showing the Lock Screen. I’ve experienced crashes anywhere from 1-5 times daily for roughly 3-5 days, though the screen has only frozen once and gone completely unresponsive for a solid minute. When it froze I attempted to power off the phone, but all buttons were y responsive as well. After around a minute had passed, the screen went black and it crashed before returning to the Lock Screen and working otherwise fine afterwards. Has anyone else experienced this, or know a potential reason this is happening ?

Last Update blocked me from being able to runoff My iPad. I became untrusted!!!!!!!!!!!!

Hi there; Apple CarPlay has some issues after updating IOS18. Initially when updated to 18.01 Carplay Maps stopped responding, cannot Mute or unmute voice, cursor doesn’t allow, cannot navigate. After updating it to 18.1 maps still continue to behave unresponsive. 18.1 has also affected other application response. This is dangerous given CarPlay stops responding during driving. I am driving an Acura MDX.

Hello, I have a 2024 Chevrolet Silverado LTZ with the Bose system. Ever since I updated to ios 18.1 on my iPhone 11 Pro Max Carplay no longer works. The truck will connect no problem to the phone but the Carplay will not start. I have tried restarting the phone and every other trick. The option for apple car play has totally disappeared from the bluetooth menu (when opening the "i" menu). Please help or release an update to help. Thank you.

Bonjour , j ai un problème de son avec les boutons du volume. Je ne peux que baisser le son. La touche du haut ne marche plus. Je ne peux plus augmenter le son avec. Je suis obligée d aller dans le centre de contrôle pour augmenter le son. pour la musique et les vidéos. Pour les sonneries c est pareil je ne peux pas augmenter le son.

Hi just wanted to ask if it's normal to have a screen who looks like there's slashes all over text, what I mean is there's a visible lines everywhere and it looks like a slashes. For context I recently brought my first Iphone and installed privacy tempered. I only noticed it after I installed the tempered glass. I probably used to much force to erase the bubbles so wondering if that is the caused? Thanks a lot to whoever can answer this. Thanks.

I have a 2023 MacBook Pro M2 Pro, and for some time now, every time I go to Settings and then to Display, or when I access the Control Center and then Screen Mirroring, or when I try to use the Handoff or AirPlay controls while connected to Wi-Fi, the screen starts flickering, showing dotted horizontal lines in a grayish color. I’ve done a clean format, booted in safe mode, run Apple’s diagnostic tests, ensured all updates are current, and unpaired all external devices. It’s unbelievable that Apple isn’t interested in resolving this issue, which seems to affect many users with their new M chips. Apple should also realize that not everyone has the ability to visit their stores since some people live far away, as if the U.S. were the center of the universe. Steve would be very upset to see how those in charge are allowed to do whatever they want to make money. Interestingly, this started happening right when my warranty expired.

I was thinking that I would like to share tips on how to improve the iPad’s interface. Here seems to be a good place. Out of constantly seeing little important details that would improve the user’s experience, I also thought that it would be really nice to exchange about such improvements and of who fun it could become. My mind likes it when Interfaces display the minimum options at once while those representing all the given necessities. The scope of this thread is broader and was created to have a space for thinking about software efficiency design. Like why on my key board should I press .?123 to then uncover #+= under the shift button? Meanwhile there are now a + sign displayed at twice upon my eyes! Ah! If I could be hired to redesign the iPads keyboard user’s experience, this world would slightly be a more efficiently structured place.

Dear Apple Support Team, I hope this message finds you well. I am writing to report an issue I have encountered with Wi-Fi connectivity on my iPhone 16 series running iOS 18.0. The problem occurs as follows: When attempting to connect my iPhone 16 series (iOS 18.0) to a Wi-Fi network, the connection always fails. After this failed attempt, any other iPhone (not from the 16 series) running iOS 18.0 also fails to connect to the same Wi-Fi network. However, if I restart the Wi-Fi router, the non-iPhone 16 series devices can successfully connect to the Wi-Fi network. To further investigate, I used Wireshark to monitor the network traffic. I observed that the iPhone sends a DHCP Discover message, but the Wi-Fi router does not respond with a DHCP Offer message. Based on these observations, it appears that the issue is triggered by the iPhone 16 series running iOS 18.0, which causes the Wi-Fi router to malfunction and prevents other devices from connecting. Additionally, I have tried all the steps listed on the following site, but the issue persists: https://support.apple.com/en-us/111786 Could you please investigate this issue and provide guidance on how to resolve it? If this is a known bug, is there a planned update to address it? Thank you for your assistance. I look forward to your prompt response. Best regards, WJohn

I have an app that was written in UIKit. It's too large, and it would be much too time consuming at this point to convert it to SwiftUI. I want to incorporate the new limited contacts into this app. The way it's currently written everything works fine except for showing the limited contacts in the contact picker. I have downloaded and gone though the Apple tutorial app but I'm having trouble thinking it through into UIKit. After a couple of hours I decided I need help. I understand I need to pull the contact IDs of the contacts that are in the limited contacts list. Not sure how to do that or how to get it to display in the picker. Any help would be greatly appreciated. func requestAccess(completionHandler: @escaping (_ accessGranted: Bool) -> Void) { switch CNContactStore.authorizationStatus(for: .contacts) { case .authorized: completionHandler(true) case .denied: showSettingsAlert(completionHandler) case .restricted, .notDetermined: CNContactStore().requestAccess(for: .contacts) { granted, error in if granted { completionHandler(true) } else { DispatchQueue.main.async { [weak self] in self?.showSettingsAlert(completionHandler) } } } // iOS 18 only case .limited: completionHandler(true) @unknown default: break } } // A text field that displays the name of the chosen contact @IBAction func contact_Fld_Tapped(_ sender: TextField_Designable) { sender.resignFirstResponder() // The contact ID that is saved to the Db getTheCurrentContactID() let theAlert = UIAlertController(title: K.Titles.chooseAContact, message: nil, preferredStyle: .actionSheet) // Create a new contact let addContact = UIAlertAction(title: K.Titles.newContact, style: .default) { [weak self] _ in self?.requestAccess { _ in let openContact = CNContact() let vc = CNContactViewController(forNewContact: openContact) vc.delegate = self // this delegate CNContactViewControllerDelegate DispatchQueue.main.async { self?.present(UINavigationController(rootViewController: vc), animated: true) } } } let getContact = UIAlertAction(title: K.Titles.fromContacts, style: .default) { [weak self] _ in self?.requestAccess { _ in self?.contactPicker.delegate = self DispatchQueue.main.async { self?.present(self!.contactPicker, animated: true) } } } let editBtn = UIAlertAction(title: K.Titles.editContact, style: .default) { [weak self] _ in self?.requestAccess { _ in let store = CNContactStore() var vc = CNContactViewController() do { let descriptor = CNContactViewController.descriptorForRequiredKeys() let editContact = try store.unifiedContact(withIdentifier: self!.oldContactID, keysToFetch: [descriptor]) vc = CNContactViewController(for: editContact) } catch { print("Getting contact to edit failed: \(self!.VC_String) \(error)") } vc.delegate = self // delegate for CNContactViewControllerDelegate self?.navigationController?.isNavigationBarHidden = false self?.navigationController?.navigationItem.hidesBackButton = false self?.navigationController?.pushViewController(vc, animated: true) } } let cancel = UIAlertAction(title: K.Titles.cancel, style: .cancel) { _ in } if oldContactID.isEmpty { editBtn.isEnabled = false } theAlert.addAction(getContact) // Select from contacts theAlert.addAction(addContact) // Create new contact theAlert.addAction(editBtn) // Edit this contact theAlert.addAction(cancel) let popOver = theAlert.popoverPresentationController popOver?.sourceView = sender popOver?.sourceRect = sender.bounds popOver?.permittedArrowDirections = .any present(theAlert,animated: true) } func requestAccess(completionHandler: @escaping (_ accessGranted: Bool) -> Void) { switch CNContactStore.authorizationStatus(for: .contacts) { case .authorized: completionHandler(true) case .denied: showSettingsAlert(completionHandler) case .restricted, .notDetermined: CNContactStore().requestAccess(for: .contacts) { granted, error in if granted { completionHandler(true) } else { DispatchQueue.main.async { [weak self] in self?.showSettingsAlert(completionHandler) } } } // iOS 18 only case .limited: completionHandler(true) @unknown default: break } } // MARK: - Contact Picker Delegate extension AddEdit_Quote_VC: CNContactPickerDelegate { func contactPicker(_ picker: CNContactPickerViewController, didSelect contact: CNContact) { selectedContactID = contact.identifier let company: String = contact.organizationName let companyText = company == "" ? K.Titles.noCompanyName : contact.organizationName contactNameFld_Outlet.text = CNContactFormatter.string(from: contact, style: .fullName)! companyFld_Outlet.text = companyText save_Array[0] = K.AppFacing.true_App setSaveBtn_AEQuote() } } extension AddEdit_Quote_VC: CNContactViewControllerDelegate { func contactViewController(_ viewController: CNContactViewController, shouldPerformDefaultActionFor property: CNContactProperty) -> Bool { return false } func contactViewController(_ viewController: CNContactViewController, didCompleteWith contact: CNContact?) { selectedContactID = contact?.identifier ?? "" if selectedContactID != "" { let company: String = contact?.organizationName ?? "" let companyText = company == "" ? K.Titles.noCompanyName : contact!.organizationName contactNameFld_Outlet.text = CNContactFormatter.string(from: contact!, style: .fullName) companyFld_Outlet.text = companyText getTheCurrentContactID() if selectedContactID != oldContactID { save_Array[0] = K.AppFacing.true_App setSaveBtn_AEQuote() } } dismiss(animated: true, completion: nil) } }

I'm unable to pair my Apple Watch Ultra (watch os 11.1 GA) onto Ios 18.2 beta 2 (had same issue with beta 1). I get a Phone out of date Error and was wondering if someone had a workaround. I tried backing up my phone, restoring on a 18.1 GA phone and tried to pair there (in hopes of later restoring backup on 18.2 b2) but I got the same error on 18.1 after the restore; I'm guessing somewhere in the backup it incorrectly restores the iOS version. I am able to pair watch on a non restored 18.1. HELP!

For some reason im facing problem: "We are unable to process your request. An unknown error occurred." I really in love with Apple but i cant understand this... I googled this error around 30 mins and didn't find any solution. What i have to do? I have 2FA, I have payment method setted.

We are now encountering a new issue where the application gets stuck after login and gives an error as “An element could not be located on the page using the given search parameters”. We were working on a solution, but the issue is still unresolved could you please assist us to get it resolved ? We have 2 different Mac machines, and we could replicate the issue on of the macs where the latest Sonoma OS and supported Xcode and Appium is installed. Please refer below details for the same: Mac machine and iOS device details: macOS: Sonoma 14.4 and 14.7 Xcode: 15 and 16 Device: iPad 17, 17.7, 18.0.1 Appium: 2.0.1 and 2.11.5 ipa file: Created on Xcode 15.4 and 16 Issue: The page goes blank and gets stuck after login.