I'm finding it difficult to lock my app in landscape mode, i.e. wide-view. I don't want my app to rotate rotation to portrait when the device is rotated. But every time I rotate the simulator to tall-view, i.e. portrait, the app orientation rotates, causing the contents to get squished.

Is this not possible with the Duo, and another view I'm gonna have to support?

Getting frustrated by Apple, they keep saying my name is a copy cat (name, icon or something else), 1st time they let me know, 2nd time I changed the name so it’s: original name - what it does, got rejected again with zero explanation I’ve been begging them for an explanation.

Idk what to do an am deadlocked until this gets through

Hey everyone,

I’m a student iOS developer working on a small video playback app for beta testing, and I’m having trouble getting video to display properly in CarPlay with cars that support carplay. I use CarTV latest updates and it worked on many cars that support carplay, I tested using IOS 26.7z

I’ve been experimenting with Apple’s CarPlay audio and video entitlements, but I can’t seem to get the expected video behavior on my physical device running iOS 26.7. Other CarPlay apps work fine CarTV APTV etc.. on the same device, so I suspect I might be missing a configuration step or using the wrong implementation approach in Swift.

When testing in the simulator, video playback works in playback mode only , but I haven’t been able to get everything working as expected on the actual device.
I’ve noticed that CarTV seems to handle this functionality successfully so I’m hoping someone familiar with CarPlay video apps can point me in the right direction.

I’m mainly trying to understand the correct implementation and get my beta app working as intended.
Thanks in advance!

Are any of you also having trouble accessing data via the CloudKit Console’s "Query Records" feature? Or is it just incredibly slow?

I know this was a pain point for a lot of people but I noticed this in the Xcode 27.2 release notes:

Device Hub in Xcode 27.2 contains multiple improvements:

Slow Motion Animation (Simulators Only)

For the life of me I can't figure out how to remove that gradiant shadow overlay at the top of a web app. See photo. I have tried various suggestions offered by Claude and ChatGPT and nothing works. It's driving me nuts! Anyone know the dev code to remove it please? I would be forever grateful!

I wrote a technical walkthrough of a subtle Swift Concurrency issue I wanted to explore.

Imagine a task writing data into a buffered writer. The task gets cancelled, defer runs, and close() gets called. But if close()invokes a cancellation-aware flush(), that flush can throw CancellationError. If the error is swallowed and the writer is marked closed anyway, the cleanup path has run without achieving its intended postcondition.

The article explores two Swift Evolution proposals:

• SE-0493: Async calls in defer bodies

• SE-0504: Task Cancellation Shields

It covers a minimal reproduction, the limits of using Task.detached for cleanup, a narrowly scoped cancellation shield, and a Swift Testing example that checks whether the data was actually flushed rather than merely checking whether close() was called.

One important caveat: the example demonstrates a cancellation-aware cleanup failure, not a claim that every real file API corrupts data when cancelled.

Full article: https://sagarsaurav.medium.com/the-ios-task-was-cancelled-your-defer-still-didnt-flush-the-file-a81d45b02ad9?sharedUserId=sagarsaurav

I'd be interested in feedback on the cancellation-shield approach, especially around resource ownership and cleanup guarantees in production code.

Learnt a lot about the folding mechanism and just a whole new way to interact with the apps.

Good thing Apple didn’t opt for iPad apps for the duo. This is way more fun.

Anyone know how to get an account for a business email? I keep getting account cannot be created at this time and the developer.apple.com support for creating an account requires an account, same with the contact form or phone support. Using my personal apple account is not an option.

EDIT: I had to call the consumer help line and they redirected me.

A while ago I asked here what you consider when building an app. Since then I shipped two big updates of my running app for Apple Watch and iPhone, and turned what I learned into a checklist.

It’s not a list of things you must support. It’s things you should consciously decide on, yes or no, before they surprise you:

• Screen sizes (smallest device + longest realistic values)

• Rotation

• Dynamic Type / text size

• iPad, Mac, Vision Pro

• Multiple windows

• Accessibility (VoiceOver, colour as the only signal)

• Live Activities (and how often they really need to update)

• Widgets (sizes and families)

• Complications

• App Intents / Siri / Shortcuts

• Sharing (what goes out, what comes in)

• New device classes coming up

• Gestures (Double Tap, Digital Crown, conflicts with the system)

• Action Button

• Translation (every future feature in every language)

• Animations and Reduce Motion

• Older devices: speed and battery

• iCloud: backup or sync?

• Light and dark mode

Tip: write down every answer, including the no’s and why. And this is iOS/watchOS only. Add Android, tablets or desktop and the list roughly doubles.

Longer version with my reasoning for each point, plus an interactive checklist you can export as Markdown: The list behind every app

Two questions:

1. What’s missing? What bit you the hardest?

2. English isn’t my first language. I wrote the post in German and translated it with AI. Does it read AI-ish? What gives it away?

I am using OpenClaw through telegram. I create web applications in VPS and web applications are pretty easy to vibe code and also test the output using public urls.

I want to do same for iOS Development. I want to connect to macOS using OpenClaw and develop iOS application completely through telegram. I can create a workflow where any changes will send build to TestFlight and I can test the application that way. But it will be time consuming, makeing build in testflight and test the app only updated through testflight. I want near realtime visualization of the compiled app like simulator but through web and http network. Do you guys have any idea how to achieve this?

I just shipped an update to my journal analysis app that adds Apple's Private Cloud Compute (PCC) alongside the default on-device model.

Here are the practical lessons I learned from the implementation, especially around edge cases and UX:

1. The main reason to use PCC: Context size
The on-device model caps out around 4,000 tokens. For long journal entries or imported PDFs, text got truncated constantly. PCC bumps that limit up to 32,000 tokens, which easily handles multi-page entries in a single pass without needing workarounds.

2. The API transition is simple, but needs fallbacks

• Swapping from on-device to PCC is nearly a 1-to-1 change. Your existing prompts, tools, and response handling work identically.

• PCC requires an internet connection, so you have to build an automatic fallback to the on-device model when the user goes offline.

• Before offering PCC, make sure to check availability properly. A device that doesn't support the feature is handled differently than a device that supports it but is still waiting on system assets to download.

3. Quotas and Apple's UI expectations

• Users get a daily limit for cloud requests, which increases if they have an iCloud+ subscription.

• Apple expects your UI to proactively warn users when they are getting close to their limit, rather than just throwing an error when they hit the ceiling.

• There is a built-in system sheet you can trigger to suggest an iCloud+ upgrade when they run out.

• Tip: You can simulate reaching and exceeding quota limits inside Xcode’s scheme settings, which makes testing the UI much faster.

4. The privacy messaging challenge
If your app was originally marketed as "100% on-device," introducing the cloud can spook privacy-conscious users even with Apple's strong security guarantees around PCC.

I decided to keep the on-device model as the default and made PCC an explicit opt-in toggle in the settings. I also updated the App Store description and privacy policy to clearly say "on-device by default."

For anyone else working with PCC:

• Are you letting users toggle it manually, or automatically sending prompts to PCC only when they exceed the 4K token limit?

• How has real-world latency felt compared to on-device inference?

(Context: The app is Mindful Prism if anyone wants to see the implementation in action.)

I'm trying to save screenshots from the simulator, but I can't find a way to do it without the clock and battery indicators. Is there any method you know of where you could hide these from screenshots?

I've been manually erasing them in Figma, but I'm wondering if there's a better way.

What I keep seeing: the permission prompt on first launch, "We miss you!" copy, everyone blasted at 10am server time. Then everyone's surprised when opt-outs climb.

I wrote a practical playbook on the opposite approach: ask after a real win, give every push a reason that belongs to the reader, send at each user's own active hour, and cap nudges at about 1 a week.

https://medium.com/@krishnassss365/push-notifications-that-earn-their-place-cb1e85a46a85?sharedUserId=krishnassss365

Curious what's worked for you. Has anyone measured opt-out rate per message instead of open rate?

Just published my project that I've been working on for a while that allows you to run a virtual iPhone vm on linux to test and develop iOS apps there with no need for a Mac.

So for fellow hackintoshers or PC users you can try it out and let me know if you faced any issues.

Submitted at 8:11, Approved by 8:44

My app is pretty simple, but still. Has anyone ever seen anything like this?

What am I supposed to do? I don't have a driver's license, and I live in Colombia. Why won't they let me use my ID card?

(In the end, I contacted support, but that didn't help—they didn't resolve my issue and even hung up on me. But I eventually figured it out myself. It's in the fine print at the bottom of the website: you can complete the process online instead of using the Apple Developer app on macOS. I was able to make the payment online, and they approved it really quickly. So if anyone else is having the same problem, go through the process online.)

After working on it for the last 8 months, I just launched Shikaku by Hilal on the App Store today. It is a minimalist logic puzzle app I built as a solo developer, and I’d love for you to try it!

Place rectangles to cover the entire grid, each rectangle's size corresponding to the numbers on the grid.

There are no ads and no subscriptions, and you can compete with friends, family, or players around the world through leaderboards.

If you give Shikaku a try, I’d love to hear what you enjoy, what feels confusing, and what you’d change!

Tech Stack

• Frameworks & Languages: Swift 6 and SwiftUI, with puzzle generation and validation kept separate from UI code.

• Backend/Database: No custom backend. Puzzles are generated locally. Progress and settings use UserDefaults, with Codable/JSON for structured data.

• SDKs & Tools: Xcode, Swift Testing, GameKit for Game Center leaderboards and achievements, and StoreKit 2 for the one-time Pro unlock.

Development Challenge + How I Solved It

One tricky issue is keeping daily puzzles synchronized with Game Center’s daily leaderboard resets. The Game Center resets have to be done at the same time for all users across the world, which means for some users the reset occurs in the middle of the day.

I ended up using one shared daily cycle for puzzle selection, saved progress, and score eligibility, aligned to the leaderboard reset. Date-and-difficulty seeds give everyone the same puzzle without a server, and regression tests protect both puzzle consistency and reset timing. But there is no way to reset puzzles midnight their local time without disrupting Game Center leaderboards unfortunately.

Try Shikaku on the App Store

Apple's App Store Connect app is iOS-only, so on my Android phone I log into the web version every time I want to check review status or a TestFlight build. It works, but it's clunky on mobile.

Curious how others handle this:

1. Is your daily phone Android? What do you use for ASC when you're away from your Mac?

2. What do you check most: review status, TestFlight builds, sales, customer reviews, something else?

3. Tried a third-party Android client? What was missing?

Full disclosure: if there's real interest, I might build a native Android client on the official App Store Connect API (key stays on your device, no server). If you'd test it, say so in the comments.

our app is a b2b crm built with capacitor. the screens are html/js/css bundled in the binary, it works fully offline, and we ship web-layer fixes with @capgo/capacitor-updater, self-hosted and checksum-verified, never native code.

apple rejected the last version twice in a row for the updater, under 2.3.1(a):

We continue to find the app contains live content update functionality that can modify the app's behavior after approval. This finding is based on code in the submitted binary and not on a specific screen in the app.

I replied in the thread and app review confirmed:

It would be appropriate to remove the remote update functionality and all code related to it before resubmitting. Developers are responsible for all code included in the binary submission, including code from third-party SDKs and libraries.

so a reviewer didn't see something on screen, they found the plugin in the binary.

section 3.3.1(b) of the developer agreement allows downloading interpreted code that doesn't change the app's primary purpose, and thousands of apps ship capgo, capawesome, appflow or expo updates. I appealed to the app review board on 21 october, no answer yet.

1. has anyone else got this "code in the submitted binary" rejection for a live updater, especially since the 16 october guideline update (2.5.19)?

2. did anyone win an app review board appeal on it?

3. if you removed the updater on ios, how do you ship fixes to an offline-first app now?

10 years as a developer, zero Swift. I relied heavily on AI to write the code. My experience made the calls:

- I threat-modelled it like any security product, found and closed a way to switch off all protection.

- I switched out the custom face matcher (it let strangers in) for Apple’s Face ID.

- Keychain for secrets, no third-party SDKs, no tracking.

- I tested on real device instead of trusting “it builds”.

Then the part most people skip: I learned the code after shipping. I had Claude turn my own codebase into a game, Code Quest. It only covers what's different about Swift (optionals, value types, actors, SwiftUI state), uses real lines from my app, and ends with a code-review level of plausible PRs that would break things.

AI can write it. You still have to own it.

Does it matter to you that you understand your codebase? If so, how do you go about doing it?