Hello, so basically when I play some game and I get a notification it lags like badly to I think 20-30 fps and stutters, when notification is gone it works normally. Also sometimes when I open control panel its has slow and laggy animation. Bought this phone like a week ago and this makes me sad :(.

We have an app with a large audience (around 2.1M DAUs) and because of this, we build it with accessibility first in mind. In that app, we link to specific iOS accessibility settings (such as VoiceOver, Display & Text, etc) in our menu screens, to offer the user a shortcut to customize VO behaviour, text size etc. Unfortunately, since iOS 18, these links are no longer working, they all open the Settings app, but don't navigate. It appears (through support) users use these links to easily access the settings, mostly older people trained to go this way in computer courses. We used to open the settings app through the App-prefs scheme, but seems broken in iOS 18. eg. App-prefs:root=ACCESSIBILITY&path=VOICEOVER_TITLE I know about the AccessibilitySettings API, but seems it is only limited to once specific feature. Is there a way we can get these links to work again?

It is outrageous that Apple continue to fail to implement the Fullscreen API web standard for web apps on iPhone only, which is so important to accessibility and web app functionality. The only possible reason for this block is commercial: to promote iOS apps instead of browser based web apps. To quote a client from a major agency just now - a typical enquiry : We value accessibility greatly, and we noticed that the embedded player is missing a full screen button on iPhone. Everything else works perfectly fine, including a full screen button that appears on the mobile webpage on android devices. Is there any way we can include a button to enable full screen view for our viewers in your player that are going to watch it on iOS devices? To which, as usual, we have to reply: Apple unfortunately block fullscreen mode from being used with all web applications on iPhone. Apple will allow this to be displayed fullscreen on MacBooks and iPads, but currently not on on iPhone - so we have to hide the fullscreen button there. So fullscreen works on all devices and browsers apart from on iPhone. As you've seen with Android, all other devices and browsers follow the universal 'Fullscreen API' web standard to allow full screen. You're probably familiar with seeing the fullscreen button on normal linear videos on iPhone. These use Apple's native video player, which doesn't let buttons and scripts be used on top of it - just a single video, not an interactive web application. Our player looks like a video player but it is actually a web app combining multiple different video clips connected together by code and styling. They block it on iPhones for reasons known only to them, but the assumption is that it is to incentivise people to make iOS apps instead of web apps. The web development community is hopeful that Apple will change this unfortunate restriction soon, but we have been waiting a long time in vain. We have to send this to a lot of people. It's a very bad look for Apple. In less than a month it will be 2025. We have been waiting years for this. The web standard documentation showing universal support on other devices and browsers is here: https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API This is not acceptable. It is time for Apple to stop blocking this important accessibility web standard for commercial reasons - only on iPhone. To whoever is in charge of these decisions in the Safari/Webkit team: Please just enable Fullscreen API for web apps on iPhone as soon as possible.

I am making an app that works on iOS 13 and above I wold like to know how can we open setting directly on a click of a button from our app

Accessibility got broken after updated till XCode 16.1 There is a call to accessibilityLabel - it sets an a11y label for a title of a view. This used to work (pronounced by VoiceOver) with XCode 15.4 + iOS 17.5. Xcode 16.1 + iOS 18.1 + Physical device/ iOS SImulator - with Accessibility Inspector - no a11y label set. Tried Xcode 16.2 beta 3 - the same result - accessibilityLabel does not work - a11y label is not set.

For practice, I have implemented accessibility labels and announcement in a very simple test app (All SwiftUI, all iOS 18). The app is not localized, default language is English. When running this on a German phone, odd things happen in the localization. My accessibility labels are read with an accent, but when they contain a url, the "dots" are read as the German "Punkt" (with an English Accent). When I am providing the same text as accessibility announcement, the same text (which is in English), is read with a German voice. I am also providing a Button with an "arrow.clockwise" image, and VoiceOver reads this, in an English Voice with "Refresh, Button". This is great and was to be expected. However, when the button is disabled, VoiceOver reads "Refresh, grau dargestellt, Button", all in an English Voice. Is this an error? Am I doing it wrong? The video at the link should show the issue https://share.icloud.com/photos/0757FJW2Q3fsA_cdhMX6ls46Q

Is it possible to play certain sounds from a macOS app that remain at full volume when VoiceOver is speaking? Here's some background: I want to play sounds from my app (even when it's not in focus) to notify a VoiceOver user that an action is available (this action can be triggerred even when the app is not in focus; and is comfigurable by the user). I tired using an NSSound for this, but VoiceOver ducks the audio of my sound when it is speaking. Is there some way to avoid audio ducking for certain sounds? Or is there another, perhaps lower level, audio API that i can use to achieve this?

I just downloaded the public release of iOS 18.2. I found a bug when using the English India female Siri voice, it’s pronouncing certain words using the American pronunciation instead of the correct pronunciation that the voice is supposed to have. For example, the Siri voice says the American pronunciation of the word privacy. This is definitely a bug that needs to get resolved as soon as possible. Can you please fix this right away?

我尝试创建一个command line tool 应用，然后创建一个dylib，其核心功能是，调用苹果登录。我安装sign in with apple 的要求，先生成一个bundle ID 然后，在开发者后台注册，同时开启其 sign in whit apple 功能。然后实现ASAuthorizationAppleIDRequest相关逻辑。运行后，控制台报错提示 [siwa] Authorization failed: Error Domain=AKAuthenticationError Code=-7074 "(null)"。相同操作对比创建app应用 是可以拉起苹果授权登录页面。对比了一下，有两点区别： 1、在signing&capabilities里，app应用可以添加sign in with apple 的capability，而command line tool 应用不可以 2、签名的区别，app的签名里会保护描述文件信息（包括bundle id）而command line tool 应用没有。 3、应用的差别，command line tool 应用 和 app应用。 现在不知道是哪个原因导致该报错

We need the pinned messages to be size customizable.

i downloaded ios 18.2 and siri returned to the old ios 17 siri.iIt wont respons.i have to click the button many times to respond and when it does it goes away.also genmoji isnt downloading i have iphone 15 pro max

Getting Robbed in the parking lot for wallet and iPhone. I needed a 2 Button shortcut to Disable Face ID iPhone Unlock. Preferably using the Camera Button and side button held for 2 seconds.

Hello community, We're designing an app that can optionally be controlled by a stylus with a mesh tip. In this case, the mesh tip we're using is 5 mm in diameter. It seems that mesh tip contact detection is unstable in this size, although it works better with a larger diameter. Is it possible to access a setting in iOS that lets you define the minimum contact area needed to detect a contact on the screen? This would enable us to use this 5 mm stylus. Best regards, Edwin

Can’t connect to App Store. iOS 15.8.3, iPhone SE 1st edition - I need to update an App, but I can’t access App Store. Other Apps appear to work normally. AND I can’t connect the phone by cable to the PC. Both things work on my iPhone 8. No idea if the two problems are connected.

xss.txt

Settings Accessibility > VoiceOver > Typing > Typing Feedback Set Character and Words General > Keyboard > Keyboards Add Japanese - Kana Use iOS18.0 ~ iOS18.2 Build with Xcode16.1 ~ 16.2 What happens? When we input "あ" in UITextField with Japanese - Kana Keyboard, it up until now it was feedback as "a". However, it is no feedback now. On UITextView, Typing Feedback working. On iOS17, also working.

We are using inline PhotosPicker introduced with iOS 17.0. The accessbility navigation using touch gestures work fine but the navigation through Keyboard doesn't work properly. The tab/arrow based Keyboard navigation can't move from native app process to inline PhotosUI process or vice versa. This is logged as a high severity bug by our accessibility team. Please look into this. Sample code for repro: https://github.com/saalisumer/AccessibilityIssueInlinePhotoPickerIOS Repro video: https://github.com/saalisumer/AccessibilityIssueInlinePhotoPickerIOS/blob/main/Simulator%20Screen%20Recording%20-%20iPhone%2015%20Pro%20-%202024-12-16%20at%2016.27.48.mp4

After updating my iPhone to ios 18.2 it is unable to connect with my car which has ford sync 3. I have tried all possibilities but no response. can someone help? regards Kumar

Following the official documentation, I'm trying to create a set of three localised Help Books. The Help Books should be available in Spanish, English and Polish. Presently, I'm trying to complete English version. App Structure This is the plugin application consisting of main app and the plugin. The main app structure would looks as follows: Files . <XcodeProject Top> ├── Localizable.xcstrings ├── MyAppExtension │   ├── MyAppExtension.swift │   └── <other swift files>.swift ├──MyApp │ ├── Info.plist │   ├── +Array.swift │   ├── +ButtonStyle.swift │   ├── <other app swift files>.swift ├── Resources     └── MyApp.help └── MyApp.help └── Contents ├── Info.plist └── Resources ├── English.lproj │   ├── ExactMatch.plist │   ├── InfoPlist.strings │   ├── MyApp.helpindex │   ├── MyApp.html │   └── pgs └── shrd MyApp / MyApp.help / Info.plist file Consists the following values: Bundle name: MyApp HPDBookAccessPath: MyApp.html HPDBookTitle: My App Help Default localization: en_gb MyApp / Info.plist file Contains the following entries: Help Book directory name: MyApp.help Help Book Identifier: MyApp Help Build phase The Copy Bundle Resources copies MyApp.help in MyApp/Resources. Questions Is the provided folder structure valid for creating a localised help books Is there anything that is missing from across Info.plist files or is in the wrong places? Why the MyApp -> Help opens the main help menu, not the app help

listbox not announcing selected or not selected option and which place it takes in the listbox Works correctly on macOS safari/chrome/firefox, Works bad on everything iOS18.1.1 I have a video for this behaviour but interface does not really allow the upload