Dear Apple App Review Team This forum isn’t the way to communicate with App Review. You need to do that directly within App Store Connect.

Is there any plan to [do something]? Nobody here can answer that. Check out item 3 in Quinn’s Top Fourteen DevForums Tips. But also note WWDC is coming up soon where they do discuss The (Near) Future™.

That functionality was marked as deprecated some time ago (in both the SDK headers and the documentation) and eventually was removed in iOS 16.4. See this thread for further discussion.

I'm 74 years old. My35 year-old son and I are developing a game Well that’s the coolest thing I’ve encountered today! I understood that I would need to supply 1x, 2x, and 3x versions Actually no modern device uses 1x density, so you really need only 2x and 3x versions. Here’s a handy chart: https://www.ios-resolution.com Wouldn't any device accessing the 3x versions of the graphics all have blurry elements? Yep, the device will render exactly what you give it, if not resizing the image further or applying any other transformation. So you definitely want your image assets to look as good as possible at design time. created all the elements at that largest size, naming it the 3x version, so that subsequent 2x and 1x versions would be reductions Downscaling is probably better than upscaling, but for best results you may want to draw the artwork by hand for each density. The same image at each density will be roughly the same physical size on all devices, but the 3x density lets you provide richer detail. Or look into supplying vector assets, if that meets your needs.

but the link is going nowhere for me. What exactly does that mean? Is there an error message? Does it go to a blank page? Do you get prompted to log in to your  account?

to display the carrier names of the active services on the phone. The real question is: why are you doing that? Is this an app whose whole purpose is to just list the carriers? Can the user act on this information in some way? If you were writing a clear purpose string for a hypothetical authorization prompt for accessing this information, exactly what would it say?

Yes, this is a common thing. You can (for example) get the Major League Baseball app and change the icon from the MLB logo to the Cardinals logo. See setAlternateIconName to get started.

Is it possible to "force" Xcode update from 14.2 to 14.3 ? If there’s some workaround to get 14.3 to run on Monterey, it’s not supported by Apple. The right approach is to upgrade your macOS to Ventura. Of course the feasibility of doing that for any particular developer is a separate issue.

Debugging with that version of iPadOS requires Xcode 14.3.

I have only verion 1.029. Does apple truncate it and consider 1.029 as 1.29 ? Yes, exactly. The individual segments in a version string are treated as integers and leading zeroes are meaningless. A two-segment version string may look like a decimal fraction but it’s not.

I am receiving the error - Couldn't parse lesssonData.json as array fatalError("Couldnt parse \(filename) as \(T.self):\n\(error)”) Is the output from fatalError() missing the actual content of the error variable that you are trying to print as a 2nd line? If so, try removing the line break (\n). Or just put a breakpoint there and examine error directly. You need to see exactly what error is being thrown in order to debug the problem.

is it requiered to upgrade the last number of version ? The new release version does need to be greater than the old one, but you aren’t specifically required to bump the last segment. Valid new versions would include 1.2.2, 1.3, 1.11, 2.0, or even 99.44. But for a “hotfix” the customary one to use would be 1.2.2. Going forward, you may find it easier to bump the 2nd segment for any “new things”, which would be 1.3 in this case. Then you can always add a 3rd segment just for bug fix releases.

Are you referring to the various styles of location permission alert on iOS? You supply (at build time) the message that gets displayed in the middle. As for how best to write that message, check out this video tech talk: Write clear purpose strings.

The carrier name is being received as -- whereas the code was being received as 65535. That is the new expected behavior on iOS 16.4 and later, because privacy. See this thread for more.

It’s going to be the same answer as last time.