getsentry
Use NXGetLocalArchInfo again to report device architecture
With https://github.com/getsentry/sentry-cocoa/issues/635, a user reported that Apple marked NXGetLocalArchInfo as a private API. This stopped him from releasing his app. FirebaseCrashlytics had a similar issue with https://github.com/firebase/firebase-ios-sdk/issues/6128. We merged a PR to remove the usage of NXGetLocalArchInfo https://github.com/getsentry/sentry-cocoa/pull/651. Firebase didn't take any action and they reported that they didn't receive any reports since September, see https://github.com/firebase/firebase-ios-sdk/issues/6128#issuecomment-758200172.
Maybe we can undo our PR https://github.com/getsentry/sentry-cocoa/pull/651 to report the architecture for the device again.
For reference: #652
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Crashlytics still uses it here https://github.com/firebase/firebase-ios-sdk/blob/bdac2b87f6d6e604deae914a970a75136b3a62b5/Crashlytics/Shared/FIRCLSMachO/FIRCLSMachO.m#L250. Make sure it's actually used on iOS.
Also, check KSCrash. Do this to make sure that readding the usage of NXGetLocalArchInfo doesn't prevent users from submitting their apps to the App Store.
KSCrash does have its own routine using sysctl, here it is in the Sentry fork: https://github.com/getsentry/sentry-cocoa/blob/60455bdb4572a4c1e4b604cc1735a3195730939f/Sources/SentryCrash/Recording/Monitors/SentryCrashMonitor_System.m#L275-L310
I also was just working on this same problem for profiling purposes, which is how I stumbled on this related set of issues. See this draft PR: https://github.com/getsentry/sentry-cocoa/pull/2205
