Can't help with the private distribution issue, but for the Login button, the reviewer is likely pressing it and getting no response. If your servers don't respond for IP addresses outside of the US, then your app should at least respond with an alert telling the user that they cannot login because they are not within the US. It's a user experience thing. No one likes an app that doesn't do anything when you press a button. For the iPad testing, they are completely entitled to test your app on an iPad. Apps have had to work properly on an iPad for years, even iPhone apps. It will launch on an iPad and display in the centre of the screen, and there's a button to scale it up. You need to test that your app can be launched on an iPad, and that it is functional. That should fix two of your issues.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. When posting your question there, make sure to explain which version of iOS you're using and what model of AirPods they are.

I can clear something up for you. I last received the analytics email on 4th June. I accepted the new agreement on 10th June, so you not having accepted it until today can't be related. There has to be something else going on. I think someone at Apple needs to figure out what's gone wrong.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

As explained in your other post - and, please don't raise multiple posts for the same thing; it just clutters the forums: You're in the wrong place. Contact the developer of an app directly if you want a TestFlight code. It's pretty obvious.

A few things: We're not your brothers, and it's quite sexist of you to ignore female developers. What redeem code? Do you realise that if you want a redeem code for a specific app on TestFlight you should contact the developer of that app directly, and not fire out a message to all the random developers on these Developer Forums? You're in the wrong place.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

Your post makes zero sense. What are you talking about?

If you don't currently know how to code in Swift and SwiftUI then you can either employ someone to do this for you, or just knuckle down and learn for yourself. It's not that difficult. Apple has tons of sample code that you can start using. Have you even tried? If not, then please do so! No one here is going to know how much it would cost to work with someone to implement your ideas, so it's pointless to ask us here. This isn't really the place to ask such a wide-ranging question. We're just developers writing apps for Apple's platforms, and we don't talk about money and costs on these forums. This isn't the place for that kind of thing.

Not entirely sure what your issue is here. You say something crashes, but you don't explain what the crash is, so it's not possible to see whether you're doing something wrong or if there is a genuine issue in Apple's code. You haven't provided any code whatsoever, so I really can't give you any help at all. Can you provide some code that explains your issue properly?

Blue chat bubbles are part of the design language for the Messages app, and besides that, they have the effect of showing you that a message is an iMessage not an SMS, so they're instantly recognisable as an Apple iMessage and it's unlikely that Apple will change this. You could suggest that all received messages could be whatever colour you choose, say black background with white text, but that loses the differentiation between the message types. However, you could suggest to Apple that you should be able to change the colours based on the type of message, e.g. you might want orange with black text for an SMS, and purple with white text for an iMessage, thus keeping the differentiation. It could be not only for aesthetic purposes but also because of a visual requirement, and perhaps they'l allow such customisations. Colour blindness is already covered in Accessibility settings, but it doesn't allow the changing of the bubbles as you'd like. You can make suggestions here: https://feedbackassistant.apple.com/

I see: iOS 18.5 (18.5 - 22F77) - com.apple.CoreSimulator.SimRuntime.iOS-18-5 so that's why mine works fine. I wonder if you can copy that file from somewhere else and put it into where it's supposed to be? Bit of a hack, but according to the internet people were doing this to fix this specific error. Personally, I would remove the runtimes via Xcode, uninstall Xcode, remove the Developer folder in Finder (take any necessary backups), reboot, reinstall Xcode 16.4, reinstall iOS 18.5 and try again. It's a lot, but it should leave it all fresh.

I think you want to use something like SMAppService. Are you saying you don't ever want a UI, or that no UI will be displayed when the app launches? So you'll still have some sort of Preferences UI somewhere? Then yes, use SwiftUI and Swift. Investigate SMAppService.

Can you provide your code for one of the tips that's appearing as a full sheet instead of a popover? Maybe there's something you're doing or not doing in your code?