Skip to main content

Posts

Showing posts from March, 2015

Xamarin release build error: obj\Release\android\AndroidManifest.xml(0,0): Error: Error parsing XML: unknown encoding

ERROR: \Release\android\AndroidManifest.xml(0,0): Error: Error parsing XML: unknown encoding ( ) CAUSE: Android Application  Version Name  is not in right format (encoding="utf-8") , so it is using a default with  <?xml version="1.0" encoding="Windows-1252"?> FIX: In the project options set android application - versionName to 3 digit version like "1.0.0",  not "1" or  "1.0"  Ex: android:versionName="1.0.0" After this change the code will compile and you can see this following line in the obj\Release\android\AndroidManifest.xml(0,0) <?xml version="1.0" encoding="utf-8"?>

NPM install Errors: '../build/Release/bson' 'MODULE_NOT_FOUND' js-bson: Failed to load c++ bson extension, node-gyp.js rebuild, ENOENT

 ISSUE: Node.js modules build errors NPM install Errors:  '../build/Release/bson' 'MODULE_NOT_FOUND'  js-bson: Failed to load c++ bson extension, node-gyp.js rebuild, ENOENT CAUSE: Even  if python path is set in the Windows' environment variable and in the path, node-gyp is not picking the python path . If you type 'python' from any directory it might work. But node-gyp will still through these errors.  It is confusing as in CLI python works if you call python.exe, but node-gyp doesn't find it, so you decide to try on every thing else you can find online. - If there is a C++ error , node-gyp rely on visual studio's C++ compiler to build. You might need to set Visual C++ path or version in the CLI command.  - long directory or path name issue in Windows: Windows only can handle 260 charecters in a given path name (oooooooooops. This is not an easy fix for windows as the core OS is built on top of this limitation.) . You have to make it sim...