kandi X-RAY | url-join Summary
kandi X-RAY | url-join Summary
Join all arguments together and normalize the resulting url.
Top functions reviewed by kandi - BETA
- Normalize a protocol string .
url-join Key Features
url-join Examples and Code Snippets
Trending Discussions on url-join
npm install causes a E402 error on many packages.
The problem will come eveyrtime I try it, but the package that caused the failure message tends to change. When checking the log however many of the packages seem to hit a 402 error.
I've tried swapping node versions, trying 8, 10 and 11. All return the same issue
Log file gives output like the following...
ANSWERAnswered 2019-Jul-25 at 22:40
What this is telling you is that the server that you're fetching from has some kind of limitation for which they expect you to pay to relieve.
Based on the stack trace, it looks like you're fetching from
https://pkgs.dev.azure.com/edgeworx/_packaging/dev/npm/registry/. It could be that you need to authorize the connection before you can access the registry with Azure. Or, you could just configure your NPM to use the public repos.
I have two apps in different accounts, rejected under the topic
2.3.1 - Performance, after upgrading to the React Native 0.59.3. Nothing was changed in this apps, except the RN upgrade.
But, both of apps are not using obfuscated code, selector mangling, or features meant to subvert the App Review process. Both are apps thats change it's contents naturally based on the API data, like many others apps like Facebook, Twitter, Instagram, etc.
Both are simples apps created with
react-native init and published more than 1 year ago for Android and iOS. We are not using codepush, test A/B or others technique to change app behaviour in runtime.
Anyone suffering with the same rejection or have any tips to solve this problem?
Apple rejection message:
Guideline 2.3.1 - Performance
We discovered that your app contains obfuscated code, selector mangling, or features meant to subvert the App Review process by changing this app's concept after approval to the App Store.
The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.
- Review the Performance section of the App Store Review Guidelines.
- Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program.
- Once your app is fully compliant, resubmit your app for review.
Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the Terms & Conditions of the Apple Developer Program to learn more about our policies regarding termination.
If you believe your app is compliant with the App Store Review Guidelines, you may submit an appeal. Alternatively, you may provide additional details about your app by replying directly to this message.
ANSWERAnswered 2019-Apr-24 at 05:18
My app also got rejected. However after replying in the resolution centre I have said that I do not use code obfuscating and I have asked for details about the reason for rejection. And just like that, I've got a notification that my app is in review and like 10 seconds later my app was approved and released :-)
To me this seems like either a bug on Apple side, or it was triggered by one of the popular frameworks, like AFNetworking, Realm, etc (where they use NSStringFromSelector, NSStringFromClass etc) but since it was large scale and everyone was explaining the usage in the same way the apps gets approved almost automatically (but you have to reply in the resolution centre in order to trigger the second review process). Hope this helps.
No vulnerabilities reported
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page