Search results for

Apple Maps Guides

151,819 results found

Post

Replies

Boosts

Views

Activity

Reply to Cannot submit apps with Xcode 26.2 RC
The link that Albert posted has updated to include this latest entry: December 12, 2025 App Store Connect update You can now upload apps built with Xcode 26.2 using the SDK for iOS 26.2, iPadOS 26.2, macOS 26.2, tvOS 26.2, visionOS 26. 2, and watchOS 26.2 for the App Store, and for internal and external testing through TestFlight. We were able to upload and submit our app. Conclusions: This is probably a rare situation. However, it demonstrates that Xcode RC builds might not reach the point of having their archived app builds accepted for App Store submissions. If anyone from Apple is reading this, our feedback: We respect your processes and accept that it is often in Apple's and the developers' interests to not convey information that is subject to change. That said, when a pattern is established like almost always accepting Xcode RC built submissions, then expectations will become established amongst the developers. If you multiply the time spent and frustration caused across all the devel
1w
Reply to Altitude for MKAnnotation
As you identified, annotations are specified using a 2D geographic coordinate, represented by CLLocationCoordinate2D. There aren't any APIs that add a third dimension to this information for the system to use in positioning the annotation on the map. If you'd like us to consider adding this functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. — Ed Ford,  DTS Engineer
1w
Reply to CoreVideo + Rosetta still clamps at 60Hz (since macOS 12)
CVDisplayLink, which is already part of CoreVideo, is used by every macOS app. CADisplayLink is iOS. CAMetalDisplayLink is the compositor for Metal apps to avoid needing MTKView, but has a high iOS/macOS requirement. So I would assume CVDisplayLink isn't going away anytime soon unless Apple plans to break every app out there. 0 is a valid setting for the fps, and doesn't mean Apple computes 1/0 and gets some randomly large integer number, and then clamp the 120Hz display to 60Hz. 0 is meant to indicate run at highest framerate of the monitor. This only happens for apps compiled for x64 and run under Rosetta, and not if recompiled for arm64. macOS x64 runs the x64 app at 120Hz too. This has to also clamp any games using GPTK too.
Topic: Graphics & Games SubTopic: Metal Tags:
1w
Logged error/warning in FigCaptureSourceRemote when capturing a photo
I'm using this library: https://github.com/Yummypets/YPImagePicker to capture photos. I've modified it slightly, and I'm using an older version. When testing on my iPhone 16e, ios 26, whenever I take a photo, I get the following two error messages: <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:302 <<<< FigCaptureSourceRemote >>>> Fig assert: err == 0 at bail (FigCaptureSourceRemote.m:569) - (err=-17281) These error messages appear, but as far as I can tell, the photo comes through OK, and I can save the data no problem. I've even removed all my handling code to see if it was something I was doing. I don't really want to ship with these errors showing, but I also have no idea what can be causing this error to appear. chatgpt was not helpful diagnosing this. Does anyone know what can cause this error Is there a way I can see the source code to figure out if there's something I'm doing wrong here? It really seems like this is an internal apple
2
0
621
1w
Reply to NSScreen's maximumExtendedDynamicRangeColorComponentValue does not seem to provide the proper value after sleep/wake on third party HDR displays even when there is EDR content on screen in macOS Tahoe
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Graphics & Games SubTopic: Metal Tags:
1w
NSScreen's maximumExtendedDynamicRangeColorComponentValue does not seem to provide the proper value after sleep/wake on third party HDR displays even when there is EDR content on screen in macOS Tahoe
The maximumExtendedDynamicRangeColorComponentValue should provide some value between 1.0 and maximumPotentialExtendedDynamicRangeColorComponentValue depending on the available EDR headroom if there is any content on-screen that uses EDR. This works fine in most scenarios but in macOS 26 Tahoe (including in 26.2) this seemingly breaks down when a third party external display is in HDR mode and the Mac goes to sleep and wakes up. After wake only a value of 1.0 is provided by the third party external display's NSScreen object, no matter what (although when the SDR peak brightness is being changed using the brightness slider, didChangeScreenParametersNotification is firing and the system should provide a proper updated headroom value). This makes dynamic tone-mapping that adapts to actual screen brightness impossible. Everything works fine in Sequoia. In Tahoe the user needs to turn off HDR, then go through a sleep/wake cycle and turn HDR back on to have this fixed, which is obviously not a sustainable w
1
0
147
1w
Reply to Cannot Update Age Rating
I just found that creating the new version and editing the ratings made the warnings at the top of the screen go away. No Apple employee on here has offered the actual steps, specific information, or answers to any of our questions, so everyone here is just doing trial and error. If what I've done is wrong, then it's Apple's fault in two ways: They didn't explain this process correctly at all; The App Store Connect website removed the warnings when I made those new versions, so Apple's developers wrote it to do that. App Store Connect Engineer said this (it's the accepted answer): You'll be able to update your app's age ratings when you submit a new version of your app. New version, not new binary.
1w
Reply to Cannot Update Age Rating
@darkpaw Interesting. Could you share where you found that it’s not necessary to submit a new version or upload a new binary? I’m asking because if that’s the case, it changes things a lot compared to the usual process. Do you know if this comes from an official Apple source or from another site? If you have a link, that would be great. Thanks!
1w
Reply to 关于 WKWebView 加载本地文件时 localStorage 数据丢失的情况
I am tracking some other issues related to localStorage. Please consider filing a bug report. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Safari & Web SubTopic: General Tags:
1w
Reply to [iOS Safari] Fullscreen API on a non-video element
Hey there @Apple Staff, the many unnecessary insults here are really embarrassing. However, the underlying frustration seems to be a symptom of the desire to have this feature working on iOS. The lack of it feels like a bug due to the comparison with Android. So, how were the testing results for 17.2? When is this going to be rolled out?
Topic: Safari & Web SubTopic: General Tags:
1w
Reply to Cannot Update Age Rating
@mattn Go to App Store Connect. Click Apps to see the screen with all your apps' icons. Click one of them. At the top left, there's a white plus button in a blue circle. Click that. Give a new version number. If you're on 2.0.5, enter 2.0.6. Close that dialog. You have created a new release. Click App Information on the left-hand side. The button by Age Ratings that used to say View will now be Edit. Click Edit. Make your selections and confirm the dialog. That's all you have to do, but you have to do it for all of your apps.You do not have to submit the new version, and you do not have to add a new binary. I can't see that your question needs an answer now since the steps you have to go through to fix this issue are actually quite easy. Apple made this a completely stupid process. Their emails were written horribly, and just created confusion. Well done, Apple... ¯_(ツ)_/¯
1w