Using Developer iOS and iPadPS 18.2 - I noticed a communications issue with AirTags. They airtag shows last location, but cannot communicate to make it make a sound. I reset one of the AirTags and now it will not connect to either iPhone 15Pro or IPad Pro. The battery is good and I've completed every troubleshooting step. has anyone else experienced this behavior?

Hello there, Has anyone else experienced a problem displaying fresh RSS feeds from this source? https://www.apple.com/rss/ Almost every feed is linked to ax.itunes.apple.com, which is not considered safe by my actual browser. For example, this feed: https://ax.itunes.apple.com/WebObjects/MZStore.woa/wpa/MRSS/justadded/limit=10/rss.xml. It seems like a certificate problem. Thanks for the reply

Pouvez vous me donner un code d’uns et demander un code d’un et après m’envoyer un courriel et comme ça j’ora mon code.

Pouvez vous me donner un code d’uns et demander un code d’un et après m’envoyer un courriel et comme ça j’ora mon code.

I work as the end user compute engineer at my employer. My test managed shared iPad Pro was on iOS 18.0.1 and from the sign in screen I was able to double click the lock/wake button twice to open the Wi-Fi picker. I upgraded it to the latest iOS 18.1 update and the Wi-Fi picker screen no longer comes up when double clicking the lock/wake button. Has this feature been removed? If so, this will pose a huge issue when it comes to new users signing in when not on a known Wi-Fi network.

After the upgrade from 15.0.1 to 15.1 yesterday, the video from the built-in camera on my M1 pro MacBook Pro 14“ has become extremely grainy. It’s definitely related to the macOS upgrade. I had several video calls just before the upgrade, and everything looked fine. However, immediately after the upgrade, the video is almost unusable.

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.

I have a 2020 Toyota Camry XSE. Ever since the iOS 18 and 18.1 updates while connected to my car via the USB cable to CarPlay when receiving or making calls the calls are lagging. A little bit of background is I have the new iPhone 16 Pro, the phone is completely up to date and my car has all the latest updates available as well so everything is up to date. I also bought a new USB cord to make sure it was not a cord issue. When I connect to my car through the cable and go to car play, everything works except for when I make or receive a call. When making or receiving a call upon answering or starting the call the moment the person picks up the system delays both voices on the call. What happens is the "time on phone display" that shows during the call, the time does not move like the call is frozen on the screen. Because of that the call is lagged when I speak or they speak and you are unable to have a normal conversation because of this. If I put the phone on speaker while still connected all of a sudden the call time unfreezes on the screen and starts counting again but the moment it take it off speaker the time freezes again and the call starts lagging again. I have NEVER had an issue until the iOS 18 updates. Please provide any feedback or suggestions, or if this is a known issue and it is currently being worked on. Like I said everything else works except for making/receiving calls that is when the issues start and the CarPlay screen freezes and starts the issues.

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 have a new USB-C Trackpad and Keyboard. The touch-id on the Keyboard does not function and multi-touch on the trackpad does not function.

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 ?

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

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.

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

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'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.