Hello, two months ago, I got a 2024 Volkswagen ID.4. At first, there was a free trial of a hotspot through Verizon. It was fine, but I'd rather use my phone's cellular data. Not long after that, I installed the iOS 18.1 beta. That's when I noticed that my phone was offline when connected to CarPlay. I have my maps downloaded, and much of my music and podcasts are configured to download locally to my phone, so I'm not sure exactly when it began. I've exhausted the settings I can think of on my phone and my car's infotainment settings. I've tried: Resetting Network settings on my phone Confirming that Wifi Assist is enabled Re-pairing my phone with my car Turning off my car's Wifi Hotspot setting turns turns off wireless CarPlay. When I try to re-connect to CarPlay, I get a notification that it must be on to connect wirelessly. Turning cellular data off and on None have helped yet. Any ideas?

I am frequently a passenger in the car but we use my phone for CarPlay. Before the latest update, I could still use my phone to send messages, review transcript of voicemail messages and read/send message on Slack while being connected to CarPlay. However, now am unable to do so. The entire car has to listen to my text message exchange or my work slack messages. I have gone through just about every setting/function in my phone trying to figure out how to get functionality back in my iPhone while being connected to CarPlay but I can't find anything that has worked. I have tried removing my car from CarPlay and reconnecting it but that did not work. Any advice would be greatly appreciated.

Hello, I am experiencing an issue with my new Lexus LBX car. The phone will not respond to ‘Hey Siri’ when i want to make a phone call or ask for directions. A manual approach through the cars infotainment system works and Spotify seems to work okay, but the system will not respond to a voice. The iPhone itself works fine with voice commands when not connected to my Lexus.

Exact same issues on my old leather MagSafe wallet, so I brought a new one from the Apple Store ‘blackberry’ colour. Yep that’s a word we don’t hear often in tech anymore. Anyway, I’ve reported it in all versions of iOS 18.1 when in beta and they still exist in iOS 18.2 beta 1. I’ve removed them, restarted phone to no avail unfortunately.

Hello, Apple Developer Community, In recent years, I've found myself increasingly concerned about the future of native ecosystems (iOS, Android), and I'd like to share my thoughts with you. It seems that small startups and cost-conscious companies are increasingly opting for cross-platform technologies like React Native, Flutter, and WebView, aiming to reduce expenses and speed up development cycles. Even large companies are following this trend in many cases. While this approach may be efficient from a business perspective, can it truly match the quality of user experience (UX) provided by native interfaces? Personally, I don't believe it does. There are undeniable advantages to cross-platform (or web-based) development, including rapid deployment and quick updates, as well as the ability to incorporate user feedback without going through a review process at every iteration. However, from my experience, once the initial version of a product has been somewhat stabilized, most companies tend to stick with cross-platform rather than transitioning to native development. In South Korea, where I am based, interest in native development education and entry-level training is on the decline. Most students and educational institutions favor frontend or backend development, and even mobile development curricula often prioritize cross-platform approaches. If this trend continues, we may face a shortage of native developers in the long run, which could lead companies to fall back on cross-platform solutions. This cyclical trend raises questions about whether a career in native development will continue to hold its advantages. On the surface, Apple appears invested in maintaining and expanding the native ecosystem. However, in practice, I feel that support for startups and smaller businesses trying to approach native development has been limited. I believe platform providers like Apple should place more focus on sustaining this ecosystem by providing practical, accessible support. (Perhaps including something as extreme as requiring a minimum percentage of native development?) I'm curious to hear what other developers in the community, particularly those who work extensively with Apple platforms, think about this shift. I'd appreciate hearing a variety of perspectives on this topic. Thank you.

While running Swift's SpeechRecognition capabilities I get the error below. However, the app successfully transcribes the audio file. So am not sure how worried I have to be, as well, would like to know that if when that error occurred, did that mean that the app went to the internet to transcribe that file? Yes, requiresOnDeviceRecognition is set to false. Would like to know what that error meant, and how much I need to worry about it? Received an error while accessing com.apple.speech.localspeechrecognition service: Error Domain=kAFAssistantErrorDomain Code=1101 "(null)"

I have a 2013 13-inch MacBook Pro and for some wild reason, the right side of my screen has become untouchable. My mouse icon can go over to that side of the screen and even click the clock and search icons above. But on the main screen, both in an application, web browser, or on the desktop, it won't click nor even let me drag any files over. I have reset, powered down and powered it up, tried zooming in and out but alas, nothing works. Please, help!

i recorded a call and try to share from the notes, the recorded file i selected and i tried to share from there to WhatsApp and i select the concern person and i tried to send the green button its not working and got stuck over there

I have noticed that my iPhone keeps jerking. I notice this juddering especially when the iPhone has been in my pocket and the always on display is not switched off. Normally, the always on display is switched off by the proximity sensor. Sometimes it doesn't recognize this and the display in the pocket stays on. When I then unlock my iPhone and swipe across the home screen, it happens more and more often that it doesn't recognize my input and the display starts to jerk. It actually looks as if the refresh rate of the display has been reduced to 60 Hz or less. Instead of the actual 120 Hz. In addition, accurate input is not really possible. The iPhone sometimes does not recognize any input and generally does not behave like a pro model. I have tried all types of resets and none of them offer a permanent solution. Resetting by “pressing and releasing the volume up button, pressing and releasing the volume down button and then holding the power button until the Apple logo appears” sometimes helps less than switching off in general. I am currently on iOS 18.2 Developer Beta

Team have noticed wireless disconnect right after 18.0 upgrade. It does recover by itself, logs show that disconnect initiated by device. Anyone have seen something similar ?

Hello, Apple Developer Community, In recent years, I've found myself increasingly concerned about the future of native ecosystems (iOS, Android), and I'd like to share my thoughts with you. It seems that small startups and cost-conscious companies are increasingly opting for cross-platform technologies like React Native, Flutter, and WebView, aiming to reduce expenses and speed up development cycles. Even large companies are following this trend in many cases. While this approach may be efficient from a business perspective, can it truly match the quality of user experience (UX) provided by native interfaces? Personally, I don't believe it does. There are undeniable advantages to cross-platform (or web-based) development, including rapid deployment and quick updates, as well as the ability to incorporate user feedback without going through a review process at every iteration. However, from my experience, once the initial version of a product has been somewhat stabilized, most companies tend to stick with cross-platform rather than transitioning to native development. In South Korea, where I am based, interest in native development education and entry-level training is on the decline. Most students and educational institutions favor frontend or backend development, and even mobile development curricula often prioritize cross-platform approaches. If this trend continues, we may face a shortage of native developers in the long run, which could lead companies to fall back on cross-platform solutions. This cyclical trend raises questions about whether a career in native development will continue to hold its advantages. On the surface, Apple appears invested in maintaining and expanding the native ecosystem. However, in practice, I feel that support for startups and smaller businesses trying to approach native development has been limited. I believe platform providers like Apple should place more focus on sustaining this ecosystem by providing practical, accessible support. (Perhaps including something as extreme as requiring a minimum percentage of native development?) I'm curious to hear what other developers in the community, particularly those who work extensively with Apple platforms, think about this shift. I'd appreciate hearing a variety of perspectives on this topic. Thank you.

Hi, I’ve seen an issue regarding scrolling in images there was a black line “ghost line” when you scroll a little longer and will be disappeared in a certain time. I hope it will be fixed in next ios update. I’m using iphone 13 pro max

I have two machines (a Studio and a MacBook Pro) and I use Universal Control to share a mouse between them. It's far from perfect, but it works. When I upgraded the second machine to 15.1 yesterday (29/10/2024), Universal Control between the machines became completely unusuable (connection drops up within a second or so of occurring). Has anyone else experienced this? I did reach out to Apple Support. I got Apple but not Support.

My Iphone is connected to the car via wireless carplay. Technically, the onboarding works via bluetooth, then via the car's hotspot (SSID from the car). I have noticed that an SSID appears under the "known networks" that has no name. The SSID can no longer be deleted, not even with a network reset on the Iphone. I asked my car dealer if he could reproduce the problem with his Iphone and another car. And he can! So it's not my device, it's an Apple problem. To be precise: The fact that you can no longer delete the SSID is Apple's problem, why the car stores an SSID without a name on the Iphone when connecting is possibly the problem of the car manufacturer. Here are a few more screens on this case.

Dear Apple Pay Support, I am writing to request a refund of $1296.59 for a transaction made on September 23, 2024, with Express Oil Change & Tires Engineering. I paid for auto repair services which were not performed. I explained to the merchant the specific repairs my car needed, and they accepted payment with the understanding that these services would be completed. However, after paying, the agreed-upon repairs were not done. This transaction depleted my savings. I am currently in my final semester of college, and having a working vehicle is essential for attending classes and completing my studies. The lack of promised repairs is creating a significant hardship and is impacting my ability to succeed academically. I have no family support system to fall back on financially; they are facing their own difficulties and I am unable to ask them for assistance. After discovering the repairs were not completed, I contacted Express Oil Change & Tires Engineering on 9/23/2024 to request they rectify the situation and complete the repairs as originally promised. I explained the significant financial strain this placed on me, especially given the large sum of the purchase. They informed me they would not be able to complete the repairs without further charges. I understand that Apple Pay acts as an intermediary for payments, and I would appreciate your assistance in contacting the merchant on my behalf to resolve this issue and secure a refund. If direct contact with the merchant is not possible, I request that you consider my difficult circumstances and grant a refund due to the fraudulent nature of this transaction. Thank you for your time and consideration. Sincerely, Jason Joseph 5044102960

I am a developer, please send me the authentication code, I need the code for the test flight application!

Upgraded to iPhone16 with iOS18. Now Apple CarPlay does not work with my 2019 Kia Niro EV. Tried some workarounds suggested on other panels but no joy. Airplay icon shows up on menu screen but is grayed out.

I was on iOS 18.1 beta 6 on my iPhone 14 Pro Max when my iPhone 16 Pro Max arrived. I took it out of the box and started to set it up as usual. I scanned the moving blue circle with my camera and began setting up the device. When I reached the software update screen, it was going to update to iOS 18.0.1. The phone restarted, and everything seemed normal. However, it brought me back to another update screen, asking me to go through the same setup steps again, which I found odd. This time, the update was for iOS 18.1 beta 7. After the update, the device restarted and appeared to be good to go, but it wasn’t. It wouldn’t go past the lock screen and kept respringing when I held down the power button to turn it off. I tried to restore the device from my computer using Apple devices, and it began to restore. The Apple logo appeared on the black screen with a loading bar, but it got stuck at about 15%. It remained like that for over an hour while plugged in. I hard restarted the device, following Apple Support’s directions, and the device became corrupted, stuck on the restore screen. I attempted to restore it again from my computer, but it only gave error codes and once again stalled at 15% of the loading bar. The error and videos and images are linked below one error is not in pictures but it was unexpected error 3503 could not complete update and restore. Betas are Apple Original, they are developer betas as I have a developer account.

Recently after the update of iOS 18.0.1 my iPhone 15 pro max drains very fast if I'm in normal usage only at one day i.e. on 19th of October I checked my battery health it shows me 99% as of today i.e. 30th October it is 96% I'm bit confused is there any issue like this to anyone i would like to know.And is there any solution for this?

I'm developing an ACME server to issue identity certificates to macOS/iOS devices for MDM attestation, following RFC 8555. Per RFC, the client creates an order, performs authorization, verifies the challenge, and finalizes the order by submitting a CSR to the CA. In my setup, the CA sometimes takes longer to issue the certificate (around 50 seconds). According to RFC 8555, if certificate issuance isn’t complete after the /finalize call, the server should respond with an "order" object with a "processing" status. The client should then send a POST-as-GET request to the order resource (e.g., /order/<order_id>) to check the current state. If the CA still hasn’t issued the certificate, the server should return the order object with the same "processing" status and include a "Retry-After" header, indicating when the client should retry. The client is expected to poll the order resource at this specified interval with POST-as-GET requests. However, it seems the Apple ACME client ignores the "Retry-After" header and instead returns the error: "Profile failed - Order status is processing, not yet valid" immediately upon the first poll response with "processing." Apple ACME client deviating from the RFC documentation. Has anyone found a reliable solution to this issue? Ref -https://datatracker.ietf.org/doc/html/rfc8555#:~:text=A%20request%20to%20finalize%20an%20order%20will%20result%20in%20error,to%20the%20%22certificate%22%20field%20of%20the%20order.%20%20Download%20the%0A%20%20%20%20%20%20certificate. To work around this, I’m holding the /finalize call until the CA issues the certificate. This works when issuance is quick (under 20 seconds), but if it takes more than that , the client times out. Interestingly, the Apple ACME client’s timeout appears shorter than the usual 60-second URLSession default.