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.

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?

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?

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.

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.

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

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.

See propreties state (link) and authorization (link) in class CBManager.

Take a look at iOS Background Execution Limits.

We use the CTCarrier mobileCountryCode to route emergency calls based on the users location But note CTCarrier never guaranteed to give the real location in the first place. It was always the user’s home service provider, not the network they are actually on if roaming outside their home area. Core Location would be the right way to determine actual location, both before the CTCarrier deprecation and now.

I updated but it didn't fix macOS: Big Sur 11.7.7 Xcode: 13.2.1 The question isn’t entirely clear. Did you update to Xcode 14.1 or later? As the error message says, Xcode 13.2.1 can’t build for the App Store any more.

Now a question back at you is: why do you want this information? Is there a location capability your app requires beyond what Core Location already provides? And here’s a 7th and more recent item for your list: https://developer.apple.com/forums/thread/691886 From that discussion, note that “satellite count” may not even be meaningful in all cases where location data is available. Core Location does the hard work of abstracting away all the complex technology that goes into determining your location, to give you a simple “you are here (in this circle)” result which all that most apps need.

Your JSON file contains a single Menu object, but your code is trying to decode it as an array. The type to decode should be Menu.self rather than [Menu].self. Then maybe check if your menu property should still be an array of Menu that probably only ever has one element, or just a single Menu. Or if the JSON could actually contain multiple Menu objects, then the server should always include the array brackets even when there happens to be only one.

That’s great news!

Start here: TN3111 - iOS Wi-Fi API overview.