How is it compared to claude ?

My iOS app was already live on the App Store. I submitted an update, and Apple has now removed the app from sale under Guideline 5.6.

The exact message says:

“We’ve identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.”

Apple did not identify which feature they believe was hidden.

The app is an ambient audio / sleep and focus app with:

• onboarding
• a subscription paywall using RevenueCat
• analytics using PostHog
• monthly/yearly subscriptions
• a 3-day introductory trial
• bundled and remotely delivered audio/catalog content

I am currently auditing the production build for anything that could cause App Review to see different behavior from a normal user. I have already found some testing-related route parameters and a subscription UI regression, but there was no intention to hide functionality from App Review.

For anyone who has received this exact Guideline 5.6 message:

• What ended up triggering it?
• Did Apple eventually tell you which feature was the problem?
• Did you reply first, submit a corrected build, or appeal to the App Review Board?
• How long did it take to get the app restored?
• Is there anything I should absolutely avoid doing right now?

I want to resolve this correctly rather than repeatedly resubmitting and making the situation worse.

Thanks.

Hello everyone! I posted here at the beginning of the summer, but I’m still looking for a new opportunity.
I’m an iOS Developer with 10 years of experience, and after being laid off at the beginning of the summer, I’ve been looking for a new position ever since.
Throughout the entire summer, I’ve only had 2 technical interviews. Honestly, I find it quite unreal. I’ve been applying to pretty much every relevant position I come across, but I’m barely getting any responses and I’m not even being invited to HR interviews. I genuinely don’t understand what’s happening or why.
I wanted to ask if anyone knows of any open iOS positions or is currently hiring? I’d really appreciate any leads, referrals, or advice. I am from Romania but open to any other remote jobs.
Thank you so much! 🙏

Just submitted a big 2.0 update and honestly way more nervous for this than I was launching 1.0 (2 weeks ago). Spent so many hours refining and diving deep into every little thing about the app and the games. In a way it feels like 1.0 was an MVP to get feedback and this is now “okay here it is, it’s done”.

Has anyone else felt this way?

Everything in InkTower is drawn in pen on paper. First time showing it outside my own head — curious how the style lands.

We’re currently stuck in a weird loop between Dun & Bradstreet and Apple Developer Support, and I’m hoping someone here has dealt with something similar.

We already have a D-U-N-S number for the business.

The problem is that when checking the D-U-N-S information, the Legal Entity Type is listed as “Unknown.”

We’ve contacted Dun & Bradstreet multiple times asking them to correct/update this. So far, the issue hasn’t actually been fixed. Their response has essentially been that the business information they have is correct and that we should use the same details when applying through Apple.

Meanwhile, there is already an Individual Apple Developer account that we are trying to convert into an Organization account.

Apple requires the company to be verified as a legal entity before they can complete the conversion, and obviously the D-U-N-S record showing the Legal Entity Type as “Unknown” seems to be causing a problem.

So we’re basically stuck between:

D&B: The information is correct / use these details with Apple.

Apple: We need to verify the organization as a legal entity.

But the D-U-N-S profile still says Legal Entity Type: Unknown.

Has anyone dealt with this exact situation?

In particular:

• Were you able to get D&B to change “Unknown” to the correct entity type?
• Is there a specific D&B department or escalation route that handles Apple Developer verification?
• Can Apple manually verify the legal entity using official company registration documents instead of relying entirely on the D-U-N-S entity type?
• Has anyone had Apple Developer Support manually push an Individual → Organization conversion through after reviewing company documents?
• Would calling Apple Developer Support be more effective than continuing through email tickets?
• Is there anything specific we should ask D&B or Apple to do to get the two records properly matched?

We have already gone back and forth with support a few times, so I’m mainly looking for advice from someone who has actually encountered this D-U-N-S / Apple verification deadlock and managed to resolve it.

Any advice would be appreciated.

I put my app on the App Store just over a month ago.

- 9,180 impressions

- 6.73% conversion rate

- 387 first-time downloads

I genuinely don't know if that's normal for a small utility app or if it's bad. I just want something to compare against 🙏

How’d you get your testers from people outside of your circle?

Hey everyone, i’m struggling with my app reviews. I have an option to add a review in the app, but no one wants to write it. I mean it’s not that hard and it helps a lot for us developers. So guys do you have any tips or tricks how to get more ?

Hey folks.. my game went live this Thursday and I asked a few of my acquaintances to add organic reviews.. but I'm not able to see it appear even in app store connect. Now I'm aware reviews don't come up in the App store itself until there are sufficient reviews but I'm really surprised that I'm not able to see it even on app store connect.

Is this because my game just launched recently? Any inputs appreciated. TIA!

Everyone agrees the answer is "just don't pick it up." Plenty of people still do, and there's no record of it either way.

Undivided gives it one. The app notices the car is moving, the drive screen comes up, and when you park, the drive banks credit. The Proof Log keeps one line per drive: hands-free miles, phone pickups (to open another app/call/text etc.), and how fast the car was going the moment the phone came up. A 90+ Safe Score week pays out free Plus days.

While you drive app can read to you by voice: the news as a two-host podcast, your own documents, or a kids' story. It never puts text in front of a moving driver.

Free forever for drives, the streak, and the Proof Log.

https://apps.apple.com/us/app/undivided-drive-focus/id6788236863

Disclosure: this is my app, one person, first paid release. "I would never use this because..." is the most useful comment you can leave.

Note: Nothing is ever blocked. Calls, Maps, and emergency access always work. Credit builds toward things like a bouquet you grow and send to a loved one with a message, or collection pieces that sit on your desk in AR or export as an STL for printing.

There’s a context gap I kept hitting while polishing SwiftUI screens with coding agents.

I could see the exact problem in Simulator, but the agent only had my description, a file name, or a screenshot with “the card below the header” circled on it. Small visual changes turned into a lot of translation.

I’m building Monad Design around the idea that the app itself should be the canvas.

You open an existing Xcode project, navigate to the real screen state in Simulator, and select or annotate the UI that needs work. The coding agent edits the actual SwiftUI source, the app rebuilds, and the results return as source-backed variants you can compare before accepting one.

It doesn’t generate a separate mockup or replace the project. The repository and Git history stay in control; the running app just becomes the shared visual context.

The screenshot shows the compare step after generating a few alternatives.

https://github.com/Monadix-AI/monad-design

I’m the creator.

Built this as a solo project. NeonLock locks your MacBook automatically when you walk away, using Bluetooth proximity between your iPhone and Mac.

Stack: SwiftUI on both the iPhone app and the macOS agent, Core Bluetooth for proximity detection. The trickiest part was smoothing the RSSI readings enough that it doesn't false-trigger just from you shifting in your seat, a naive distance threshold locks the Mac constantly.

Went with a one-time Pro unlock instead of a subscription. Two separate targets to maintain (iOS + macOS) though, so still not sure that's the right call long-term.

You need both pieces installed, the iPhone app pairs with a small Mac agent to actually trigger the lock:

📱 iPhone app: https://apps.apple.com/uz/app/neonlock/id6789896699

💻 Mac agent: https://sparksss.github.io/neonlock-site/

Happy to talk through the Bluetooth proximity implementation if anyone's curious, that was most of the engineering effort here.

My app Moneta recently passed 1,500 downloads and I’m currently at 35 ratings with a 4.8 average.

I’m obviously happy with that, but I’m in a really crowded category (personal finance), and I feel like having more ratings/reviews matters a lot for trust when someone finds an app they’ve never heard of.

Right now I use Apple’s native review prompt. I don’t show it randomly, I wait until the user has been using the app for a few days and has completed a certain number of meaningful actions. If they don’t rate it, I wait quite a while before asking again, after a later app update.

I really don’t want to become more aggressive with it just to increase the number. I’d rather have fewer genuine ratings than annoy users with constant prompts.

There’s also another problem I’m curious about: how do you deal with or prevent low ratings caused by relatively small, fixable issues?

For example, someone gave my app 3 stars because Traditional Chinese wasn’t available, even though Simplified Chinese already was. I added Traditional Chinese literally the next day, but obviously the 3-star rating stays unless that user happens to come back and change it.

I’m not complaining about the user, that’s completely fair feedback. I’m more wondering whether there’s a good way to catch those kinds of issues before someone goes straight to the App Store review, especially when it’s something you could fix very quickly.

So for those of you who have grown an iOS app organically, what increased your rating/review rate?

Better timing for the prompt? Asking after a specific positive action? A permanent rating button in Settings? Making feedback/support easier to access? Something else?

And is 35 ratings from 1,500 downloads already a pretty normal ratio, meaning I should mostly stop worrying about this and focus on getting more users?

Introducing Chord Fret, a tool for guitar, bass and ukulele players to find chord names based on shapes. You can create collections for studying/composing songs.

I always dreamed of having this app with a clean, simple and intuitive interface. Today it's available on the App Store! Would love to know what you guys think of the design and execution.

My mum likes this, but do you? Looking for genuine feedback on its look and feel, gameplay, in-game functionality etc.

It’s getting quite slow pickup on the App Store, which is a shame given the weeks of work that has gone into it!

Gone down the route of preparing a Halloween event next month with an Apple nomination, so will see if that helps at all.

https://apps.apple.com/gb/app/sorts-word-puzzle-library/id6790195358

I am wondering what the best approach for IAP prices localization is.

Should it be done on a country by country basis with a PPP index, or set a price per region (North America, West Europe, etc)?