There are millions of apps on the App Store. Unless you go viral or are featured by Apple you have little to no chance of getting any downloads. I've had apps on the App Store since day one - literally the day the App Store went live - and I barely get any app downloads anymore. I spend hours each day tweaking, improving, adding features, fixing bugs, and handling the new ways of doing things in each iOS release, and I still get barely any downloads. A month ago I added Apple Ads with a high cost so they're guaranteed to be displayed, and not a single person has downloaded my apps through those ads. I've contacted the various Mac- and iOS-related blogs and websites to see if they'll do a write-up on my apps, and they just ignore everything. If you find the magic way of getting people to locate your apps you could probably make more money selling that info than making an app. Too many apps, too few people willing to pay anything, and a terrible search feature in the App Store add up to no downloads. I can search for the app name of one of my apps and it will appear about 100 places down. It should be the first item listed. I'm searching for the app's exact name. The App Store has become a flea market: lots of stalls, lots of trash.

I've tried this on macOS 15.7.3 Sequoia with Xcode 26.1.1 (17B100). It works fine. The button taps work perfectly in Preview, in the Simulator, and on-device (iPhone 17 Pro Max with iOS 26.2).

You've managed to put some of the code into code blocks, but not all of it. When you submit your post, you know you can look at it, see that it's not formatted correctly, edit the post, and correct it, right? Okay, well, I'll have a look and see if I can help.

Can't do much with the code as provided. Please reply with the code within the code block. Use the formatting tools to do this, or just type three backticks (`) in a row at the start and end of your code. And please ensure all relevant code is present. Example: import SwiftUI struct ContentView: View { var body: some View { ... } }

Have you tried contacting Logitech?

We will prove our innocence with our lives That's a wildly unnecessary title for your post. We will be filing complaints against Apple’s inexplicable account suspension both on the developer forums and in the media. We will fight this inequality with all we have, and stand for fairness and justice. You are unlikely to get very far by bad-mouthing Apple in the media. You will get further if you calmly ask Apple why they're suspending your account. Your first step is to ask on these forums, or to contact Apple Developer relations via the "Tell us how we can help" on this page. While it's sad that someone suffered a heart attack, having an account suspended is highly unlikely to have caused it, and I'd say raising it in a complaint to Apple is unlikely to help. Stay calm, ask the right questions, get the right information, and make sure you have all your information correct.

@Lsunset Those look like internal warnings that Apple needs to fix, not you. You should raise feedback at: https://feedbackassistant.apple.com/ then post the FB number here.

You might be better off contacting Apple directly rather than posting on the forums if this happens again. No one on the forums can fix this, unless an Apple employee comes across your post and investigates it - and they don't investigate everything. If you're paying Apple for the service and the service isn't working, there must be some contact details you can use?

You raised the same issue in January 2025. What was the solution back then?

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".

@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... ¯_(ツ)_/¯

The App Store Connect Engineer's reply in August '25 links to this page, which clearly shows that App Information > Rating is not editable, and thus requires a new version of an app to be submitted. Why? Why do we have to submit a new version of our apps - I have seven on the App Store - just to add new ratings? (Changing existing ones, maybe, okay, but these are new ratings.) Does the App Review team actually check each and every app update to confirm that they adhere to the exact ratings you select? Really? This sort of obstacle really drives me nuts. There's no reason it needs to be this difficult.

So, just to confirm: Apple sent an email to developers with the subject: "Final reminder: Answer the updated age ratings questions". That email says: "We’re reaching out because you have not provided responses to the updated age ratings questions in the App Information section of your app in App Store Connect. If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect." Right, so if we don't submit these new age ratings we cannot submit new app updates after January 31st 2026, but in order for us to change those age ratings we have to submit new versions of our apps? Am I really being told to build and archive a new version of each of my apps just to update the age ratings? This is what I currently see on one of my apps: so this is great... And, just to make it even more complex than it needs to be, the email also says this: "Please also note that the Texas SB2420 legislation goes into effect January 1, 2026. Under this law, making an age rating change to apps distributed in Texas would be considered a significant change. If you update your age rating after this date, you may need to trigger the significant change consent process." Which means that even if you don't need to submit a new version of your app because you haven't made any changes, doing so after January 1st 2026 will require you to "trigger" some other process? All this just to change the age ratings on our apps that are already on the App Store? Why not just let us change the age ratings and confirm that they apply to the version currently on the App Store?!

You can raise suggestions at: https://feedbackassistant.apple.com/ The Developer Forums aren't the place for suggestions.

@protodimbo Have you tried adding let _ = Self._printChanges() to the body of your view? Each time the view is drawn that'll print out what caused it.