-
Notifications
You must be signed in to change notification settings - Fork 159
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
Using this library causes iOS app to be rejected from App Store #28
Comments
Thanks for your feedback. Do you need these APIs which start with |
I'm personally currently using |
You can modify your codes to solve it as a temporary solution. path: -(void)initSetting{
setting = @{};
} Now you can upload a new app to AppStore safely. Of course, I'll provide a final solution for all people in the next few days. |
Funny, I just got rejected also for that ... :< Thanks for the workaround |
V1.4.0 is available. Add new API for this issues: You should call
|
@c19354837 Hi, I'm using this library (
I checked the latest source code and the code does conceal the usage of the private APIs. Do you think this could potentially lead to a ban on the app if I upgrade the library? |
You have to upgrade to >= 1.4.0. And I get an issues #55 about App Store. |
What about concealing the usage of private APIs as communicated by Apple team? Do you think it'd be an issue? Regarding the issue with BT permission, I did get that as a reason for rejection for an earlier build. When I added a string for permission, it got solved. |
I did not receive any issues about the rejection from App Store since 1.4.0, so I think it works. If you still get a rejection after upgrade to latest version, please let me know. |
V1.7.0 is available. These annoying codes are removing by preprocessor macros. See #58. |
@c19354837 It looks like a good fix. We're using a fork in which I removed those lines right now. We'll make another release in under a week and will let you know how it goes. Thanks. |
@c19354837 When I run |
The package `react-native-system-setting` was the only one I found which offered a method to check if a device's location services were enabled (required for Android Bluetooth to work in API 23+). However, that library maintainer also has a track record of choosing implementations which violate Apple's policies, resulting in threats of termination of Apple Developer Accounts. [1][2] I don't need any of the other functionality in that library, and I really don't want to expose myself to that author's implementation whims. As such, I found it prudent to take this opportunity to learn how to build a Native Module for React Native applications (at least for Android). I largely followed the official guide [3], and the only hiccups I had resulted from Android Studio selectively auto-saving files, causing confusing, but temporary compilation errors. [1] c19354837/react-native-system-setting#28 [2] c19354837/react-native-system-setting#58 [3] https://reactnative.dev/docs/native-modules-android
I attempted to submit an app to the iOS App Store using
react-native-system-setting
and received this scary rejection:The only place in my app that uses the "prefs:root=" non-public URL scheme is in
react-native-system-setting
, specifically inreact-native-system-setting/ios/RTCSystemSetting.m
starting at line 55:This package is fantastic, but this problem must be addressed, or users of this package simply can't submit to the iOS App Store.
The text was updated successfully, but these errors were encountered: