A note about App_Resources

Issue #40

Author: EddyVerbruggen

README.md

@@ -33,14 +33,15 @@ _Architectural overview of the solution - you don't need to worry about all of t
 </details>
 
 ### What can (and will) be AppSync'ed?
-- Anything inside your `/app` folder.
+- Anything inside your `/app` folder (but not the `App_Resources` folder.
 - Anything inside your `/node_modules` folder.
 
 > 💁‍♂️ Note that we don't actually use those folders, but the `app` folder in `platforms/ios/<appname>/app` and `platforms/android/app/src/main/assets/app`, the benefit of which is we don't "care" if you use Webpack or Uglify or whatever tools you use to minify or scramble your app's assets.
 
 ### What can't (and won't):
 - NativeScript platform updates. Example: bumping `tns-android` from version 2.5.1 to 2.5.2.
 - Plugins updates that also require a different version of a native library it depends on.
+- Contents of the `App_Resources` folder, because those are part of the native binary as well.
 
 So as long as you don't change versions of dependencies and tns platforms in your `package.json` you
 can push happily. And if you do bump a version of a dependency make sure there are no changed platform libraries.
@@ -551,4 +552,4 @@ If at any time you want to start or stop using a proxy, simply logout, and then
 </details>
 
 ## Troubleshooting
-- Got build errors related to the __nativescript-zip__ plugin? Please check out [the solution in this issue](https://github.com/EddyVerbruggen/nativescript-app-sync/issues/34#issuecomment-526860302).
+- Got build errors related to the __nativescript-zip__ plugin? Please check out [the solution in this issue](https://github.com/EddyVerbruggen/nativescript-app-sync/issues/34#issuecomment-526860302).