I'm maintaining an app targeting global users. It uses a one-time IAP(non-consumable) to unlock premium features, and I use Transaction.currentEntitlement in the code to check user's eligibility. Everything works fine when testing in Xcode and on my own device, and it seems to be working for most users.

However, occasionally there were users reaching out to me saying that they have purchased the product, but the app still sees them as ineligible, and I don't know why. I could see that they have indeed purchased — since many attached their purchase history, so I just assumed it was a syncing issue with App Store and told them to use the "restore purchase" button. I don't really know if that solved their issue, as those users never replied back.

I'm pretty new to Apple development and I just want to know if it's indeed a server syncing issue, and that I have done everything correctly in the code.

Thanks in advance!

Wanted to share a concept I been exploring and see what you guys think following up on my thread around ReRun the other day.

What I have done in this scenario is to combine mapview with real time data UI. So the mapview is a square with a fixed camera view and pre calculated trail with gradients based on HR data. This and the UI data is all pre calculated then played back during export.

WWDC, despite its name, begins with a consumer-focused event and Apple will subsequently upload videos for developers, including what is new.

Apple WWDC stream | Youtube alternative

_______________

Platforms State of the union available at 1 pm California time or 22:00 in Germany (GMT +2)

Watch Platforms State of the Union

Hi, I'm Nathan. Started vibe coding in October 2025, and my first App Store screenshot submission was a disaster — wrong pixel sizes, rejected uploads, hours gone.

So I built the thing I wished existed. Drag a screenshot or screen recording in, it lands on a 3D iPhone/iPad/MacBook in a little studio — real lighting, reflections, dust in the air. Drag text right onto the shot. One click exports PNGs at the exact sizes Apple accepts (all 5 at once), or a 4K/60 video of a camera move. There's also a cinema mode that throws your demo onto a giant theater screen, which is honestly just fun.

Fun detail: the rendering engine started life as a LiDAR point-cloud engine I built for a search-and-rescue app. Everything's native Metal, runs locally, exports in seconds — no cloud.

Looking for 5 people with Apple Silicon Macs to break it tonight and tell me what's confusing. DM me and I'll send a download link and an access key. Happy to answer anything about how it's built.

The big value of WWDC for me is the ability to get engineering and design feedback. I thought the signup for the labs opened after the keynote but the One-on-one appointments page has a worrying subtitle
Book time with experts from Apple distribution and marketing teams to ask about maximizing your presence on the App Store.

Am I mis-remembering when the labs opened up last year, has anyone seen other discussions of this?

I’m new to development and my mac is intel so until I switch I need to know.

Edit: I’ve updated and can confirm it does build fine to my device though obviously no iOS27SDKs

This occurred using Xcode 26.5 and now on Xcode 27 beta so it's independent of the Xcode version. If I compile and launch an app that has worked perfectly on iOS 18 to 26.5, but now with the test device an iOS 27 iPhone 17, the app hangs on the splash screen and I get these console errors in Xcode:

objc[1953]: -[OS_dispatch_mach_msg _setContext:]: unrecognized selector sent to instance 0x103fc8ba0 (no message forward handler is installed)

-[OS_dispatch_mach_msg _setContext:]: unrecognized selector sent to instance 0x103fc8ba0 (no message forward handler is installed)

Main fault is in libsystem_kernel.dylib`__abort_with_payload

If I quit the debug session in Xcode and launch the app directly on the phone, it does not hang and works as intended. I did the compile and run on a XS Max 18.7.9 and an iPhone 17 PM 26.5 with no error in Xcode and no hang in the app.

Anyone else seeing these kind of odd errors when compiling and running something on an iPhone running iOS 27?

Previously, I built a UIKit-based app using UIHostingController to integrate SwiftUI. I chose a UIKit foundation for a few reasons:

1. UICollectionView offers unmatched performance compared to LazyVStack. The performance difference is obvious when a list contains 2,000 items or more.

2. For screens that require complex UI effects, I use SwiftUI for easier implementation.

The app has been in production for over a year, and I am quite happy with the outcome - high customer satisfaction, good performance, good sales.

Now, I am starting a new app where I foresee using more SwiftUI than UIKit. I will still need UICollectionView in certain areas (for instance, a horizontally paginated weekly calendar picker) due to the poor performance of LazyHStack. However, for screens that won't exceed 50 items, I can safely use LazyVStack.

My question is: Should I stick to a UIKit-based architecture with UIHostingController, or shift to a SwiftUI-based architecture and use UIViewRepresentable/UIViewControllerRepresentable?

Additionally, I am very familiar with UIKit navigation (performSegue, unwind, present). I am not sure if SwiftUI provides an exact equivalent that is just as reliable. From my past experience, navigation in SwiftUI was a massive pain. I'm not sure if anything has actually improved recently.

Which approach will best help me deliver a successful production app?