locked
userId is returned as undefined RRS feed

  • Question

  • Hi,

    In our company we are using Azure Mobile Services for our products. For the past couple of hours we are getting the userId as 'undefined' for all our operations. It was working before that and we are passing the X-ZUMO-AUTH header correctly. Can someone please say what might be the issue ?

    Thursday, March 28, 2013 10:07 AM

Answers

  • We apologize for any issues this has caused. We have deployed a fix but it will take several hours to propagate to every Mobile Service.

    However, you can force your service to take the fix by using the Azure Command Line Tools:

    1. Install the Azure Command Line Tools (for Windows, Mac, or Linux): http://www.windowsazure.com/en-us/develop/nodejs/how-to-guides/command-line-tools/#Download
    2. Associate your account: http://www.windowsazure.com/en-us/develop/nodejs/how-to-guides/command-line-tools/#Account
    3. Run 'azure mobile list' to see your list of Mobile Services
    4. To deploy the update and restart your service, run 'azure mobile restart <MobileServiceName>' to restart a specific Mobile Service. This will only take a few seconds.
      Note that this command *may* report that it failed even though the restart succeeded.
    5. Check your service to verify that the issue is resolved.

    We'll be monitoring this thread to help you through any other issues, should they arise. Once again, we apologize for any inconvenience and we're working to prevent scenarios like this in the future.


    Brett Samblanet -- Windows Azure Mobile Services

    • Proposed as answer by Brett Samblanet Thursday, March 28, 2013 4:08 PM
    • Marked as answer by Gotopal Inc Monday, June 24, 2013 11:47 AM
    Thursday, March 28, 2013 3:19 PM

All replies

  • We're seeing this too - as of a couple of hours ago.

    Nick Randolph ~ Built to Roam

    Thursday, March 28, 2013 10:39 AM
  • Hi Nick and Gotopal,

    Are you still having problems?

    What regions are your Mobile Services in?  - Go to the Dashboard section for your Mobile Service and look on the right side.  My service is in East US and I am not having issues.

    Are you able to successfully log in even if the UserID is not there?

    -Jeff


    Jeff Sanders (MSFT)

    Thursday, March 28, 2013 1:07 PM
  • PS, what providers are you using (MicrosoftAccount, Facebook...)

    Jeff Sanders (MSFT)

    Thursday, March 28, 2013 1:10 PM
  • Update.  There is a known issue in our backend with the userID being returned.  This should be fixed soon.  Thanks for reporting this!


    Jeff Sanders (MSFT)

    Thursday, March 28, 2013 1:25 PM
  • Hey guys,

    What's the ETA for this fix?

    Thursday, March 28, 2013 1:58 PM
  • We apologize for any issues this has caused. We have deployed a fix but it will take several hours to propagate to every Mobile Service.

    However, you can force your service to take the fix by using the Azure Command Line Tools:

    1. Install the Azure Command Line Tools (for Windows, Mac, or Linux): http://www.windowsazure.com/en-us/develop/nodejs/how-to-guides/command-line-tools/#Download
    2. Associate your account: http://www.windowsazure.com/en-us/develop/nodejs/how-to-guides/command-line-tools/#Account
    3. Run 'azure mobile list' to see your list of Mobile Services
    4. To deploy the update and restart your service, run 'azure mobile restart <MobileServiceName>' to restart a specific Mobile Service. This will only take a few seconds.
      Note that this command *may* report that it failed even though the restart succeeded.
    5. Check your service to verify that the issue is resolved.

    We'll be monitoring this thread to help you through any other issues, should they arise. Once again, we apologize for any inconvenience and we're working to prevent scenarios like this in the future.


    Brett Samblanet -- Windows Azure Mobile Services

    • Proposed as answer by Brett Samblanet Thursday, March 28, 2013 4:08 PM
    • Marked as answer by Gotopal Inc Monday, June 24, 2013 11:47 AM
    Thursday, March 28, 2013 3:19 PM