Sounds like hang detection is active and doing its job. See this link for more. Can someone tell if it is possible to get rid of it and how ? Hang detection is a helpful feature so it’s best to leave it enabled. Then the “right way” to get rid of the warning is to update the app using the advice on that linked page, to eliminate the hang that is getting reported.

Search in the More page there: https://developer.apple.com/download/all/?q=Additional%20Tools

See this thread for an answer. Having said that, also consider whether any network session APIs may meet your needs, such as allowsConstrainedNetworkAccess (link) and allowsExpensiveNetworkAccess (link).

it “closes” itself and returns to the originally intended app. Unfortunately that’s not a thing on iOS. Calling exit() is equivalent to just crashing, which always dumps the user back at the home screen.

See this thread for details on why /usr/lib looks a little thin these days. On my machine with Xcode 15.3 installed, the library is found here: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libpthread.tbd And with Command Line Tools installed, also found here: /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/usr/lib/libpthread.tbd Note those are .tbd files, not .dylib any more.

This library is included. Maybe there is some incorrect path setting for it in your old project? Can you link a fresh test app using pthreads successfully?

Do you mean the JSON decoding is throwing an error and landing in this catch block? } catch { print("could not parse json data") } If so, you should print out the actual error that is being thrown. What does it say?

we are a Carrier company [...but...] we currently don't have direct point of contact with Apple That’s the first problem you need to solve. As mentioned in the post you linked, there’s nothing available to discuss in this forum (public APIs) that would help.

I need to immediately know when the iPhone is unlocked. Why? Can you detail what app functionality depends on this? There’s no specific notification for unlocking, but take a look at app delegate method applicationProtectedDataDidBecomeAvailable(_:) (link) and corresponding notification protectedDataDidBecomeAvailableNotification (link). I am a newbie in iOS/APP development. Welcome! You’ll find that Apple APIs tend not to just give you random information about the system (“is the device locked?”) but instead support more specific use cases like the delegate and notification given above: “can I access protected data right now?” It should work even if my app is not running. There are various events that can wake or launch your app (see LaunchOptionsKey at link) but unlocking isn’t one of them.

Does choosing the alternate app icon in app settings not count as "within the app" ? By “general app settings” do you mean your app’s settings bundle that the user accesses via the system Settings app? Or just a page titled General that is inside your app itself? If in the settings bundle, then how do you actually change the icon? That wouldn’t give you any context from which to call UIApplication.setAlternateIconName() when the user makes a change. Or are you calling setAlternateIconName() at some point after the app launches/resumes after visiting your bundle in system Settings? I guess that could work, but probably doesn’t match their expectation that the icon-changed confirmation alert pops up immediately after the user performs a gesture to trigger the change.

There is only one privacy policy URL per app. But of course you are free to make the target page include further redirection to your multiple privacy policy pages, or whatever you want.

This gets asked a lot. (Search the forum.) Here’s one of the best answers I’ve seen so far: link. I think it’s usually more useful to rethink the requirement to prevent capture in the first place. Why is this particular data ok to view in the app but not ok to view later? Is it not the user’s data for them to handle as they wish?

This is also spelling out in our end user agreement as well Unfortunately, sounds like maybe your license and app requirements got developed without considering App Store policies up front. If so, there’s no good solution aside from just making the changes needed to pass review. It also seems you ask for gender. Why do you need ? Indeed, be very careful there. I can’t even imagine what a “peer to peer sharing app” needs with gender. If it’s just for cosmetic purposes, such as choosing pronouns for addressing users in messages that you generate... well, be very, very careful. Or just don’t go there.

Are you asking for their specific birth date? It may be acceptable to just ask: Are you at least 18 years old?

They finally (a few years ago) put it all in GitHub, so you can forget about that terrible old web page: https://opensource.apple.com https://opensource.apple.com/releases/ Libm doesn’t seem to be listed under any of the OS release repos, but has its own repo: https://github.com/apple-oss-distributions/Libm