Hi. I've started do work with Azure "Mobile Services" this year and I had a good experience with it. But now that I would work with it seriously, I was informed that I should use "Mobile Apps" instead. So, my problems began... The main problem is this moment is the absense of the "Try it out" button on the services page. It was a very useful resource on Mobile Services, where I could verify and test the published services. It's not available even in my workstation, acessing the"localhost" started with my Visual Studio 2013 Ultimate. I've searched for a solution around but I couldn't find a solution. And I wasn't able to find a resouce where I could use in the same way. Is it a commom situation with everyone developing Mobile Apps?

Greetings,

Danbalby.

I have a node.js mobile service which I 'git cloned' to my local workstation. I did 'npm install request --save' and a git commit. Now I'm getting errors when I deploy with 'git push'. I see ENOTSUP errors, so does that mean that npm request-promise is not supported?

Here are the exact steps I performed.

1. git clone [azure mobile service git url]
2. cd [working directory]/service
3. npm install [module name] --save
4. git commit -am "Add npm request module" && git push

My package.json file is:

{"name": "myazureapp","version": "1.0.0","description": "myazureapp - hosted on Windows Azure Mobile Services","main": "server.js","engines": {"node": ">= 0.8.19"
  },"dependencies": {"azure": "^0.10.6","basic-logger": "^0.4.4","bignumber": "^1.1.0","bing": "^0.1.0","braintree": "^1.35.1","facebook-node": "0.0.3","geobing": "^0.1.3","mobileservice-config": "^1.0.0","moment": "^2.11.2","node-uuid": "^1.4.7","paypal-adaptive": "^0.4.2","paypal-ec": "^0.2.7","paypal-ipn": "^3.0.0","q": "^1.4.1","request": "2.9.152","request-promise": "^2.0.0","sendgrid": "^2.0.0","sprintf": "^0.1.5","underscore": "^1.8.3","xml2js": "^0.4.16"
  },"devDependencies": {},"scripts": {},"author": "unknown","licenses": [],"keywords": []
}

And here is what 'git push' reveals:

me@iMac:~/coding/git/mymobileapp/service$ git commit -am "Add npm modules" && git push
[master ee243be] Add npm modules
 1 file changed, 3 insertions(+), 3 deletions(-)
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 386 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: Updating branch 'master'.
remote: Updating submodules.
remote: Preparing deployment for commit id 'ee243bea61'.
remote: Running custom deployment command...
remote: Running deployment command...
remote: Handling Basic Web Site deployment.
remote: KuduSync.NET from: 'D:\home\site\repository\service' to: 'D:\home\site\wwwroot\App_Data\config\scripts'
remote: Copying file: 'package.json'
remote: Looking for app.js/server.js under site root.
remote: Missing server.js/app.js files, web.config is not generated
remote: Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0.
remote: Selected node.js version 5.6.0. Use package.json file to choose a different version.
remote: Selected npm version 3.6.0
remote: Updating iisnode.yml at D:\home\site\wwwroot\App_Data\config\scripts\iisnode.yml
remote: npm WARN package.json mymobileapp@1.0.0 No repository field.
remote: npm WARN package.json mymobileapp@1.0.0 No README data
remote: npm WARN package.json basic-logger@0.4.4 No repository field.
remote: npm http GET https://registry.npmjs.org/request-promise
remote: npm http GET https://registry.npmjs.org/request
remote: npm http 304 https://registry.npmjs.org/request-promise
remote: npm http 304 https://registry.npmjs.org/request
remote: npm http GET https://registry.npmjs.org/request-promise/-/request-promise-2.0.0.tgz
remote: npm http GET https://registry.npmjs.org/request/-/request-2.9.152.tgz
remote: npm http 200 https://registry.npmjs.org/request-promise/-/request-promise-2.0.0.tgz
remote: npm http 200 https://registry.npmjs.org/request/-/request-2.9.152.tgz
remote: npm http GET https://registry.npmjs.org/lodash
remote: npm http GET https://registry.npmjs.org/bluebird
remote: npm http 304 https://registry.npmjs.org/bluebird
remote: npm http 304 https://registry.npmjs.org/lodash
remote: npm http GET https://registry.npmjs.org/aws-sign2
remote: npm http GET https://registry.npmjs.org/aws4
remote: npm http GET https://registry.npmjs.org/caseless
remote: npm http GET https://registry.npmjs.org/combined-stream
remote: npm http GET https://registry.npmjs.org/form-data
remote: npm http GET https://registry.npmjs.org/bl
remote: npm http GET https://registry.npmjs.org/extend
remote: npm http GET https://registry.npmjs.org/forever-agent
remote: npm http GET https://registry.npmjs.org/har-validator
remote: npm http GET https://registry.npmjs.org/http-signature
remote: npm http GET https://registry.npmjs.org/is-typedarray
remote: npm http GET https://registry.npmjs.org/isstream
remote: npm http GET https://registry.npmjs.org/json-stringify-safe
remote: npm http GET https://registry.npmjs.org/hawk
remote: npm http GET https://registry.npmjs.org/mime-types
remote: npm http GET https://registry.npmjs.org/oauth-sign
remote: npm http GET https://registry.npmjs.org/stringstream
remote: npm http GET https://registry.npmjs.org/qs
remote: npm http GET https://registry.npmjs.org/tough-cookie
remote: npm http GET https://registry.npmjs.org/tunnel-agent
remote: npm http 304 https://registry.npmjs.org/aws-sign2
remote: npm http 304 https://registry.npmjs.org/aws4
remote: npm http 304 https://registry.npmjs.org/caseless
remote: npm http 304 https://registry.npmjs.org/combined-stream
remote: npm http 304 https://registry.npmjs.org/bl
remote: npm http 304 https://registry.npmjs.org/har-validator
remote: npm http 304 https://registry.npmjs.org/form-data
remote: npm http 304 https://registry.npmjs.org/extend
remote: npm http 304 https://registry.npmjs.org/is-typedarray
remote: npm http 304 https://registry.npmjs.org/forever-agent
remote: npm http 304 https://registry.npmjs.org/http-signature
remote: npm http 304 https://registry.npmjs.org/isstream
remote: npm http 304 https://registry.npmjs.org/oauth-sign
remote: npm http 304 https://registry.npmjs.org/json-stringify-safe
remote: npm http 304 https://registry.npmjs.org/hawk
remote: npm http 304 https://registry.npmjs.org/tough-cookie
remote: npm http 304 https://registry.npmjs.org/mime-types
remote: npm http 304 https://registry.npmjs.org/stringstream
remote: npm http 304 https://registry.npmjs.org/tunnel-agent
remote: npm http 304 https://registry.npmjs.org/qs
remote: npm http GET https://registry.npmjs.org/delayed-stream
remote: npm http 304 https://registry.npmjs.org/delayed-stream
remote: npm http GET https://registry.npmjs.org/mime-db
remote: npm http GET https://registry.npmjs.org/async
remote: npm http 304 https://registry.npmjs.org/mime-db
remote: npm http 304 https://registry.npmjs.org/async
remote: npm http GET https://registry.npmjs.org/readable-stream
remote: npm http GET https://registry.npmjs.org/lru-cache
remote: npm http 304 https://registry.npmjs.org/lru-cache
remote: npm http 304 https://registry.npmjs.org/readable-stream
remote: npm http GET https://registry.npmjs.org/assert-plus
remote: npm http GET https://registry.npmjs.org/jsprim
remote: npm http GET https://registry.npmjs.org/sshpk
remote: npm http 304 https://registry.npmjs.org/assert-plus
remote: npm http 304 https://registry.npmjs.org/sshpk
remote: npm http 304 https://registry.npmjs.org/jsprim
remote: npm http GET https://registry.npmjs.org/pinkie-promise
remote: npm http GET https://registry.npmjs.org/chalk
remote: npm http GET https://registry.npmjs.org/commander
remote: npm http GET https://registry.npmjs.org/is-my-json-valid
remote: npm http GET https://registry.npmjs.org/verror
remote: npm http GET https://registry.npmjs.org/extsprintf
remote: npm http GET https://registry.npmjs.org/json-schema
remote: npm http 304 https://registry.npmjs.org/pinkie-promise
remote: npm http 304 https://registry.npmjs.org/commander
remote: npm http 304 https://registry.npmjs.org/chalk
remote: npm http 304 https://registry.npmjs.org/is-my-json-valid
remote: npm http 304 https://registry.npmjs.org/verror
remote: npm http 304 https://registry.npmjs.org/extsprintf
remote: npm http 304 https://registry.npmjs.org/json-schema
remote: npm http GET https://registry.npmjs.org/pinkie
remote: npm http GET https://registry.npmjs.org/cryptiles
remote: npm http GET https://registry.npmjs.org/sntp
remote: npm http GET https://registry.npmjs.org/has-ansi
remote: npm http GET https://registry.npmjs.org/strip-ansi
remote: npm http GET https://registry.npmjs.org/supports-color
remote: npm http GET https://registry.npmjs.org/boom
remote: npm http GET https://registry.npmjs.org/hoek
remote: npm http GET https://registry.npmjs.org/ansi-styles
remote: npm http GET https://registry.npmjs.org/escape-string-regexp
remote: npm http GET https://registry.npmjs.org/isarray
remote: npm http GET https://registry.npmjs.org/process-nextick-args
remote: npm http GET https://registry.npmjs.org/string_decoder
remote: npm http GET https://registry.npmjs.org/util-deprecate
remote: npm http GET https://registry.npmjs.org/core-util-is
remote: npm http GET https://registry.npmjs.org/inherits
remote: npm http 304 https://registry.npmjs.org/pinkie
remote: npm http 304 https://registry.npmjs.org/cryptiles
remote: npm http 304 https://registry.npmjs.org/has-ansi
remote: npm http 304 https://registry.npmjs.org/sntp
remote: npm http 304 https://registry.npmjs.org/ansi-styles
remote: npm http 304 https://registry.npmjs.org/boom
remote: npm http 304 https://registry.npmjs.org/strip-ansi
remote: npm http 304 https://registry.npmjs.org/supports-color
remote: npm http 304 https://registry.npmjs.org/hoek
remote: npm http 304 https://registry.npmjs.org/process-nextick-args
remote: npm http 304 https://registry.npmjs.org/escape-string-regexp
remote: npm http 304 https://registry.npmjs.org/isarray
remote: npm http 304 https://registry.npmjs.org/util-deprecate
remote: npm http 304 https://registry.npmjs.org/string_decoder
remote: npm http 304 https://registry.npmjs.org/inherits
remote: npm http 304 https://registry.npmjs.org/core-util-is
remote: npm http GET https://registry.npmjs.org/graceful-readlink
remote: npm http 304 https://registry.npmjs.org/graceful-readlink
remote: npm http GET https://registry.npmjs.org/ansi-regex
remote: npm http 304 https://registry.npmjs.org/ansi-regex
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-conv.1' }
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-sign.1' }
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-verify.1']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-verify.1' }
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-conv']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-conv' }
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-sign']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-sign' }
remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-verify']
remote:   errno: -4049,
remote:   code: 'ENOTSUP',
remote:   syscall: 'scandir',
remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-verify' }
remote: npm ERR! error rolling back Error: EPERM: operation not permitted, rmdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules\json-schema'
remote: npm ERR! error rolling back     at Error (native)
remote: npm ERR! error rolling back  json-schema@0.2.2 { [Error: EPERM: operation not permitted, rmdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules\json-schema']
remote: npm ERR! error rolling back   errno: -4048,
remote: npm ERR! error rolling back   code: 'EPERM',
remote: npm ERR! error rolling back   syscall: 'rmdir',
remote: npm ERR! error rolling back   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\jsprim\\node_modules\\json-schema' }
remote: npm http GET https://registry.npmjs.org/generate-function
remote: npm http GET https://registry.npmjs.org/generate-object-property
remote: npm http GET https://registry.npmjs.org/jsonpointer
remote: npm http GET https://registry.npmjs.org/xtend
remote: npm ERR! error rolling back Error: EPERM: operation not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules'
remote: npm ERR! error rolling back     at Error (native)
remote: npm ERR! error rolling back  jsprim@1.2.2 { [Error: EPERM: operation not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules']
remote: npm ERR! error rolling back   errno: -4048,
remote: npm ERR! error rolling back   code: 'EPERM',
remote: npm ERR! error rolling back   syscall: 'unlink',
remote: npm ERR! error rolling back   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\jsprim\\node_modules' }
remote: npm http 304 https://registry.npmjs.org/generate-function
remote: npm http 304 https://registry.npmjs.org/generate-object-property
remote: npm http 304 https://registry.npmjs.org/xtend
remote: npm http 304 https://registry.npmjs.org/jsonpointer
remote: npm ERR! Error: ENOENT: no such file or directory, chmod 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE'
remote: npm ERR!     at Error (native)
remote: npm ERR! If you need help, you may report this *entire* log,
remote: npm ERR! including the npm and node versions, at:
remote: npm ERR!     <http: github.com="" issues="" npm="">
remote:
remote: npm ERR! System Windows_NT 6.2.9200
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts
remote: npm ERR! node -v v5.6.0
remote: npm ERR! npm -v 1.4.9
remote: npm ERR! path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE
remote: npm ERR! syscall chmod
remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE
remote: npm ERR! fstream_type File
remote: npm ERR! fstream_class FileWriter
remote: npm ERR! fstream_finish_call chmod
remote: npm ERR! code ENOENT
remote: npm ERR! errno -4058
remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\1.4.9\node_modules\npm\node_modules\fstream\lib\writer.js:305:19
remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:15)
remote: npm ERR! Error: ENOENT: no such file or directory, lstat 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js'
remote: npm ERR!     at Error (native)
remote: npm ERR! If you need help, you may report this *entire* log,
remote: npm ERR! including the npm and node versions, at:
remote: npm ERR!     <http: github.com="" issues="" npm="">
remote:
remote: npm ERR! System Windows_NT 6.2.9200
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts
remote: npm ERR! node -v v5.6.0
remote: npm ERR! npm -v 1.4.9
remote: npm ERR! path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js
remote: npm ERR! syscall lstat
remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js
remote: npm ERR! fstream_type File
remote: npm ERR! fstream_class FileWriter
remote: npm ERR! code ENOENT
remote: npm ERR! errno -4058
remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\1.4.9\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:15)
remote: npm ERR! error rolling back Error: EPERM: operation not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator'
remote: npm ERR! error rolling back     at Error (native)
remote: npm ERR! error rolling back  har-validator@2.0.6 { [Error: EPERM: operation not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator']
remote: npm ERR! error rolling back   errno: -4048,
remote: npm ERR! error rolling back   code: 'EPERM',
remote: npm ERR! error rolling back   syscall: 'unlink',
remote: npm ERR! error rolling back   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\har-validator' }
remote: npm ERR! EEXIST: file already exists, mkdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\lodash\object'
remote: File exists: D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\lodash\object
remote: Move it away, and try again.
remote:
remote: npm ERR! System Windows_NT 6.2.9200
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts
remote: npm ERR! node -v v5.6.0
remote: npm ERR! npm -v 1.4.9
remote: npm ERR! path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\lodash\object
remote: npm ERR! syscall mkdir
remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\lodash\object\transform.js
remote: npm ERR! fstream_type File
remote: npm ERR! fstream_class FileWriter
remote: npm ERR! code EEXIST
remote: npm ERR! errno -4075
remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\1.4.9\node_modules\npm\node_modules\fstream\lib\writer.js:171:23
remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\1.4.9\node_modules\npm\node_modules\mkdirp\index.js:37:53
remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:15)
remote: npm ERR! Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1'
remote: npm ERR!     at Error (native)
remote: npm ERR! If you need help, you may report this *entire* log,
remote: npm ERR! including the npm and node versions, at:
remote: An error has occurred during web site deployment.
remote: npm ERR!     <http: github.com="" issues="" npm="">
remote:
remote: npm ERR! System Windows_NT 6.2.9200
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts
remote: npm ERR! node -v v5.6.0
remote: npm ERR! npm -v 1.4.9
remote: npm ERR! path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1
remote: npm ERR! syscall scandir
remote: npm ERR! code ENOTSUP
remote: npm ERR! errno -4049
remote: npm ERR!
remote: npm ERR! Additional logging details can be found in:
remote: npm ERR!     D:\home\site\wwwroot\App_Data\config\scripts\npm-debug.log
remote: npm ERR! not ok code 0
remote:
remote: Error - Changes committed to remote repository but deployment to website failed.
To https://mymobileapp.scm.azure-mobile.net/mymobileapp.git
   05525e5..ee243be  master -> master</http:></http:></http:>

Hi, We have a mobile app in iPhone(IOS), Android and Windows phones. We can publish data to that app(to all 3 platforms) and can send or schedule push notification any time who are installed our app using windows service. Now We would like use Azure service to send/ schedule push notifications. How can I store my app users apple token/gcm token/windows phone channel uri's and  6 more columns in one table in azure and is there any service/methods to achieve this and send push notifications to all platforms.

Any suggetion would be appreciated.

Thanks

Malli

I used the next code I watch on a tutorial, I am working with iOS (swift) and when I call the next custom function:

exports.post = function(request, response, next) {
var mssql = request.services.mssql;
mssql.query("update todoitem " + "set complete=1, completeDate=GETDATE() " + "where complete=0", {
        success: function(results) {
            response.send(200, "{ message: 'Hello, world!' }");
        }
    });
 }; 

I got: 

Optional(Error Domain=com.Microsoft.MicrosoftAzureMobile.ErrorDomain Code=-1302 "Cannot read property 'mssql' of undefined" UserInfo={com.Microsoft.MicrosoftAzureMobile.ErrorResponseKey=<NSHTTPURLResponse: 0x7fa25af3d830> { URL: https://lazarillo.azurewebsites.net/api/markalldone } { status code: 500, headers {

    "Content-Length" = 53;

    "Content-Type" = "application/json; charset=utf-8";

    Date = "Tue, 16 Feb 2016 15:37:01 GMT";

    Etag = "W/\"35-1gvX8VWObWphbnIhlDSrHw\"";

    Server = "Microsoft-IIS/8.0";

    "X-Powered-By" = "Express, ASP.NET";

} }, NSLocalizedDescription=Cannot read property 'mssql' of undefined, com.Microsoft.MicrosoftAzureMobile.ErrorRequestKey=<NSMutableURLRequest: 0x7fa25ad0c530> { URL: https://lazarillo.azurewebsites.net/api/markalldone }})

Hi,

I used to make REST call to my mobile service by adding my FB token in the request header (X-ZUMO-AUTH) along with the application key(X-ZUMO-APPLICATION). This has been working for quite awhile now.

As I'm trying to migrate to using App service, all my clients no longer able to make any calls to the server because they no longer authorized. I've setup the authentication using Facebook on my App Service settings and it seems everything's fine except all calls from client no longer works.

Is there a new way for client to make calls? I can't seem to find anything on MSDN except for the old method

thanks

I am trying to set up a Azure Mobile Service for an Android app. I started with the quick start samples that are given in Azure. I have created a database and server connection, hosted a Node.js back end, and setup the database with the tables I am trying to access successfully. I have followed the various tutorials that Microsoft has on the subject and I am still having trouble connecting to my database. After running my app a dialog box shows up with the message "Push operation has failed. See the PushResult for details". Here are the code snippets which I believe are required to access the database.

Initialization:

  //Mobile Service Client reference
    private MobileServiceClient client;

    //Mobile Service sync table used to access data
    private IMobileServiceSyncTable<EmployeeItem> employeeSyncTable;
    private IMobileServiceSyncTable<EventItem> eventSyncTable;
    private IMobileServiceSyncTable<RecipientListItem> recipientListSyncTable;

    //Adapter to map the items list to the view
    private EmployeeItemAdapter employeeItemAdapter;
    private EventItemAdapter eventItemAdapter;
    private RecipientListItemAdapter recipientListItemAdapter;


    const string applicationURL = @"myurl(this is correct)";
    const string localDbFilename = "localstore.db";

    protected override async void OnCreate(Bundle bundle)
    {
        base.OnCreate(bundle);

        // Set our view from the "main" layout resource
        SetContentView(Resource.Layout.Login);

        CurrentPlatform.Init();

        // Create the Mobile Service Client instance, using the provided
        // Mobile Service URL
        client = new MobileServiceClient(applicationURL, new NativeMessageHandler());
        await InitLocalStoreAsync();

        // Get the Mobile Service sync table instance to use
        employeeSyncTable = client.GetSyncTable<EmployeeItem>();
        eventSyncTable = client.GetSyncTable<EventItem>();
        recipientListSyncTable = client.GetSyncTable<RecipientListItem>();

        // Create an adapter to bind the items with the view
        employeeItemAdapter = new EmployeeItemAdapter(this, Resource.Layout.Employee);
        eventItemAdapter = new EventItemAdapter(this, Resource.Layout.Event);
        recipientListItemAdapter = new RecipientListItemAdapter(this, Resource.Layout.RecipientList);

        //using this to test my connection
        await employeeSyncTable.InsertAsync(makeSampleEmployeeItem());
        // Load the items from the Mobile Service
        OnRefreshItemsSelected();//calls SyncAsync() and RefreshItemsFromTableAsync() which updates views.

    }

From SyncAsync:

    await client.SyncContext.PushAsync();
            await employeeSyncTable.PullAsync("allEmployeeItems", employeeSyncTable.CreateQuery());
            await eventSyncTable.PullAsync("allEventItems", eventSyncTable.CreateQuery());
            await recipientListSyncTable.PullAsync("allRecipientListItems", recipientListSyncTable.CreateQuery());

Table Type Definition:

public class EmployeeItem
{
    public string Id { get; set; }

    [JsonProperty(PropertyName = "Name")]
    public string Name { get; set; }

    [JsonProperty(PropertyName = "Email")]
    public string Email { get; set; }

    [JsonProperty(PropertyName = "EmployeeID")]
    public int EmployeeID { get; set; }

    [JsonProperty(PropertyName = "Department")]
    public string Department { get; set; }

    [JsonProperty(PropertyName = "PrivledgeLevel")]
    public string PrivledgeLevel { get; set; }
}

I'm not sure what happened with my Mobile App, but whenever I call PullAsync I get an exception.

When I debug on the server side, the endpoint is not being hit at all, my breakpoint is never activated.

<!DOCTYPE html><html><head><title>An asynchronous module or handler completed while an asynchronous operation was still pending.</title><meta name="viewport" content="width=device-width" /><style>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
         @media screen and (max-width: 639px) {
          pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }
         }
         @media screen and (max-width: 479px) {
          pre { width: 280px; }
         }</style></head><body bgcolor="white"><span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1><h2> <i>An asynchronous module or handler completed while an asynchronous operation was still pending.</i> </h2></span><font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif "><b> Description: </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.<br><br><b> Exception Details: </b>System.InvalidOperationException: An asynchronous module or handler completed while an asynchronous operation was still pending.<br><br><b>Source Error:</b> <br><br><table width=100% bgcolor="#ffffcc"><tr><td><code>

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.</code></td></tr></table><br><b>Stack Trace:</b> <br><br><table width=100% bgcolor="#ffffcc"><tr><td><code><pre>

[InvalidOperationException: An asynchronous module or handler completed while an asynchronous operation was still pending.]
</pre></code></td></tr></table><br><hr width=100% size=1 color=silver><b>Version Information:</b>&nbsp;Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1055.0</font></body></html><!--
[InvalidOperationException]: An asynchronous module or handler completed while an asynchronous operation was still pending.
--><!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using &lt;customErrors mode="Off"/&gt;. Consider using &lt;customErrors mode="On"/&gt; or &lt;customErrors mode="RemoteOnly"/&gt; in production environments.-->

the next function is not working, I think is a syntax problem because console.log("inserted"); never appears.

var item = { 
                     password : postValues.password,
                     email : postValues.email,                     
 }; 

var accounts = currentRequest.azureMobile.tables('accounts');

accounts.insert(item).then(function(data){

                            console.log("inserted");

 });

Hello!

I'm using Mobile App with UWP application.

I have received an exception on pulling data:

"An invalid API version was specified in the request, this request needs to specify a ZUMO-API-VERSION of 2.0.0"

Has solve it after adding on portal in my mobile app settings

It works only when I purge table and fill it with:

await App.MobileService.SyncContext.PushAsync();
await demoTable.PurgeAsync();
await demoTable.PullAsync(null, demoTable.CreateQuery());

But when I try to update it this way:

await demoTable.PullAsync("mydemotableRonin", demoTable.Where(u => u.surname=="Ronin"));

Hi,

I've tried to replace LiveSDK with OneDriveSDK, but an unauthorized error message is returned.

My Code:

var oneDriveClient = OneDriveClientExtensions.GetUniversalClient(scopes);
var session = await oneDriveClient.AuthenticateAsync();
await mobileService.LoginWithMicrosoftAccountAsync(session.AccessToken);

With LiveSDK the following Code works:

LiveAuthClient liveIdClient = new LiveAuthClient(azureUrl);
LiveLoginResult result = await liveIdClient.LoginAsync(scopes);
LiveConnectClient client = new LiveConnectClient(result.Session);
MobileServiceUser loginResult = await mobileService.LoginWithMicrosoftAccountAsync(result.Session.AuthenticationToken);

Is it possible to use Mobile Services and OneDriveSDK without LiveSDK?

Regards

Bernd

I am trying to use a new database (which is actually old database with some column data type changes and some additional columns) with existing azure mobile service. I created the database in local instance of SQL server and deployed it to SQL Azure, to the same DB server where older server is. But when I tried to access the tables in Data tab, it firs told me that - user is not able to access the database under the current security context. After adding the user to the DB, now I see followinColumn information was not loaded for the following tableg error

Any ideas?

Hi,

I am using the samples .NET backend + Xamarin.Forms for the offline sync. However, when I do PullAsync I got error on the server side 400 Bad Request. After I remotely debug Azure, I found that the request of the pull is something like:

https://xxx.azurewebsites.net/... ge datetimeoffset'1970-01-01T00:00:00.0000000%2B00:00')&$orderby=__updatedAt&$skip=0&$top=50&__includeDeleted=true&__systemproperties=__updatedAt%2C__version%2C__deleted&$select=Text,Complete,Id,Version,CreatedAt,UpdatedAt,Deleted, Message='Content-type='application/json; charset=utf-8', content-length=unknown'

And it seems that __updatedAt is not correctly mapped to UpdateAt in the SQL table (using EntityData)... The Models and DTO are the same of the sample.

Any ideas? I have installed all the latest compatible Nuget packages and I am testing on Android with Xamarin.Forms.

Best,

Min

Under "sign in options" is the following text on this blog

a client can obtain a token using a provider SDK and exchange it for a session token. Simply submit an HTTP POST to the same endpoint with the provider token in a JSON body under the key “access_token” (or “authenticationToken” for Microsoft Account). This is the preferred solution for mobile applications if a provider SDK is available on the platform, and it also works for many web and API applications.

Question

How do I exchange a token for a session token?

Hi guys, 

It's my first time working with Azure and I was just trying to make a demo Android app(the TodoItem Demo).

I followed every step in the official tutorial(the one below) but it seemed that the auto generated code wasn't working. (and the code I wrote myself failed too)

https://azure.microsoft.com/en-us/documentation/articles/mobile-services-android-get-started/

I always got "Error while processing request" when the app starts or when I hit the "add" button

Actually the same error occurs when either of the following methods is called:

mToDoTable.where().field("complete").
        eq(val(false)).execute().get();
or 
mToDoTable.insert(item).get();

I wonder  if anybody here had experienced the same problem.  Any solutions? 

Drone captures Aerial images in different formats like TIFF, JPEG and Raw format in every 2 seconds.

I need to connect Drone device with Azure IOT suite to get media like captured images and videos. Also need to capture geo- cordinates like latitude, longitude and radius from Drone device.

Can we use Azure IOT suite for above requirement? Please suggest something.

Its urgent.

Thanks,

Hema

hema

Hello!

I follow the tutorial to create a new Azure Mobile App and would like test push notifications.

But there is no entry for Push in my Mobile Apps Service?

Can anyone help me to solve this?

Thanks

From @5robesons_aj via Twitter

"I created an Azure Mobile Service Scheduler function a couple years ago and now need to edit the script.  How can I get to it?

When I upgraded to the new portal, my mobile service with the script was migrated. Now I don't see it in the classic portal.

Thanks - My job migrated and still runs daily.  Now I need to edit but see no way to get to the script to edit it."

https://twitter.com/5robesons_aj/status/702289533904224257

Thanks,

@AzureSupport

I created a new App Services Mobile App, and I notice I am being prompted to log in after only a few hours.
After using a helper method I found online to check if a token is expired, I am seeing that my cached tokens are expiring only a few hours or so after login.

I did not have this problem with my 3 previous Azure Mobile Services apps, or with my most recent Azure App Service web app.

Is this something new in Mobile Apps?

How can I provide users with a fluid login experience so that they almost never have to sign in after the initial login?

Hello, Im trying to migrate my existing applications in Parse.com but im getting a lot of troubles when running my code in Azure system.

I followed the steps mentioned in this blog post :

https://azure.microsoft.com/en-us/blog/azure-welcomes-parse-developers/

But now i cant make my own code work, getting some uncaught exeptions when tryin to run it.

My Index.js text taked from the example app from parse-server

Now this is the wwwroot structure:

Cant understand why im getting this error:

Im looking for an alternative to migrate my Parse Apps, this is my first time using Azure, hope i can make it work.

Thanks for the attetion.