-
-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NXGetLocalArchInfo is marked as private API #635
Comments
Thanks, @vox-humana for reporting this. FirebaseCrashlytics has a similar issue: firebase/firebase-ios-sdk#6128 . |
Thanks for the quick fix 🥳 |
@vox-humana do you by any chance already have a response from the App Store Review team? |
@philipphofmann Apple has reached us once via feedback assistant to confirm the case, but after that unfortunately no news. |
Thanks for the update @vox-humana. So they confirmed the case. Does this sound like they are going to fix it? |
@philipphofmann According to my personal statistics Apple never confirms bugs and gives developers any hope 😅 The same happens this time. They've just asked whether we could confirm this issue and that was all. |
Unfortunately, I can't quickly check whether it is still an issue just by building and uploading binary with this symbol because we have quite strict process for publishing builds (don't have direct access to signing certificates). |
I wasn't expecting they would tell you they fix it 😁, but worth a shot. Thanks, a lot for the update @vox-humana. |
@vox-humana do you have maybe any updates if |
@philipphofmann Because we are using the library without this symbol I can't verify the issue anymore. Also, we didn't get any reply from Apple. |
Platform:
Swift:
sentry-cocoa installed with:
Version of sentry-cocoa:
5.1.0
Seems like Apple marked
NXGetLocalArchInfo
, which used in the library to get arch name, as private API. Since the end of the previous week we are getting this message when we are uploading our mac binaries to App Store Connect:Thus, we cannot release our builds anymore. Even though I believe this an issue on Apple side because this method seems quite public to me, I think we should probably consider using a different method. Will try to reach App Store Review team while and will post an update here.
The text was updated successfully, but these errors were encountered: