locked
Push notifications in the Mobile tutorial RRS feed

  • Question

  • Hello, I’m trying to test push notifications in the Mobile tutorial and I’m receiving an error that I’m un-able to find an answer for, here’s the error:

    The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. (Exception from HRESULT: 0x803E011A)

    I have followed the instructions several time and still I get this error.

    Thanks in advance


    Service is the rent we pay for the space we take up on earth!


    • Edited by M. Howard Friday, May 17, 2013 10:26 PM
    Friday, May 17, 2013 10:26 PM

Answers

  • Hello Jeff, I was finally able to get my project working! The problem was I had 2 diff client id's and I was referring to the wrong one.

    The other problem was I was confusing :"https://appdev.microsoft.com"  with "https://manage.dev.live.com" when I was trying to get the correct client id's.

    Thanks for all your help.


    Service is the rent we pay for the space we take up on earth!

    • Marked as answer by M. Howard Tuesday, June 18, 2013 10:23 PM
    Tuesday, June 18, 2013 2:46 PM

All replies

  • Hi M,

    Where are you getting this error?

    Which tutorial are you following?

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Monday, May 20, 2013 3:38 PM
  • Hello, I'm using the Win8 tutorial and I'm getting the error here:

     private async void AcquirePushChannel()
            {
                try
                {
                    CurrentChannel =
                        await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
                }
                catch (Exception e)
                {
                    string err = e.ToString();
                }
            }

    Thanks for your help!


    Service is the rent we pay for the space we take up on earth!

    Monday, May 20, 2013 3:48 PM
  • I have seen this when you are not using the package SID when you register the application with the store:

    http://www.windowsazure.com/en-us/develop/mobile/tutorials/get-started-with-push-dotnet/#register

    Or the client secret has been changed.

    The app that you register through Visual Studio is tied to the Push notification through the manifest and the SID so make sure the app you are working on is associated with the correct app in the dashboard as well.

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Monday, May 20, 2013 3:54 PM
  • Does the name of my VS project name have to match the name in the Store?

    Service is the rent we pay for the space we take up on earth!

    Monday, May 20, 2013 4:30 PM
  • No but it has to be associated per the tutorial.

    Try a new project from scratch to familiarize yourself with the process, then you should be able to find the step(s) you are missing in your case.

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Tuesday, May 21, 2013 2:20 PM
  • Hello, very very very very frustrating process! I have tried several apps and now I can't even create the SID from the Push Notification Service I click on the link in the Advanced section and it says:

    https://appdev.microsoft.com/StorePortals

    We can't show you that page

    Our server is having a problem. We're working to fix it as soon as we can, so try again in a few minutes. 

    Can I please get someone to help me get going its been almost 2 weeks....

    


    Service is the rent we pay for the space we take up on earth!

    Sunday, May 26, 2013 3:43 AM
  • That page should be fixed now.  Can you confirm you can hit it now?  It also seems like maybe you are not setting the SID and Client id correctly in the PUSH, tab.  Pay close attention to the order (it is opposite from your dev.windows.com dashboard.

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)




    Tuesday, May 28, 2013 3:45 PM
  • Ok well I can generate the Package SID and Client Secret now, but I'm still getting the original error:

    System.Exception was unhandled by user code
      HResult=-2143420134
      Message=The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. (Exception from HRESULT: 0x803E011A)
      Source=mscorlib
      StackTrace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at timone.App.<AcquirePushChannel>d


    Service is the rent we pay for the space we take up on earth!

    Friday, May 31, 2013 4:16 AM
  • The error you are getting really sounds like you have not associated your application with an app in your dashboard.  Would you be willing to email your project to me?  In addition the problem you are having is not with Mobile Services itself but with acquiring the push channel.  That is supported by the Windows Store team and you can get help by creating a support case or posting to this forum:http://social.msdn.microsoft.com/Forums/en-us/winappswithcsharp/threads

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)


    Friday, May 31, 2013 12:31 PM
  • Hello Jeff, well I was able to track down the first problem. I noticed that I was unable to log into the Win Store and update my apps. I tried my proj on another system and I was able to get by the original Channel error. So I rebuilt my system and now I can get by that error on my main sys.

    The problem now is an authentication error: The Microsoft Account authentication request failed with HTTP status code 400.

    I have rebuilt the app, regenerated a new Client key but still no joy!

    I must say this is a fragile process...

    Any help would be appreciated,

    Thanks


    Service is the rent we pay for the space we take up on earth!

    Tuesday, June 4, 2013 6:28 AM
  • Hi M,

    What is the exact error you are getting.  400 is not an authentication error.  It is a Not found error.

    What are the authentication settings our your table operations (there will be four)?

    Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Tuesday, June 4, 2013 11:52 AM
  • The error that's being thrown happens in the Auth method, see below:


    Service is the rent we pay for the space we take up on earth!

    Tuesday, June 4, 2013 2:23 PM
  • On my table they are set to Only Authenticated Users.

    Service is the rent we pay for the space we take up on earth!

    Tuesday, June 4, 2013 2:41 PM
  • Did you follow the Auth tutorial step my step and set up the Microsoft Identity information?

    Are you able to get to the Microsoft OAuth screen if try via the browser using your Mobile Service URL?

    Example https://YOURMOBILESERVICE.azure-mobile.net/login/microsoftaccount

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Tuesday, June 4, 2013 3:05 PM
  • I just tried and nothing gets returned in the json string?

    Service is the rent we pay for the space we take up on earth!

    Tuesday, June 4, 2013 3:48 PM
  • That is actually correct behavior (if you did not get any 400 or 404 errors).  If you attach Fiddler you would see that the JWT token is returned on the redirect just before the done page.  The problem lies somewhere in your code.

    What happens if you download a new project from your mobile service dashboard and then apply the code changes in in the Auth tutorial?

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Tuesday, June 4, 2013 3:55 PM
  • Ok I tried that, still no change...

    Service is the rent we pay for the space we take up on earth!

    Tuesday, June 4, 2013 5:02 PM
  • Can you share a simple repro of the problem with you service on SkyDrive or somewhere?

    The server is responding correctly according to the WebBrowser test so it must be an issue with your client code or environment.

    -Jeff


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Tuesday, June 4, 2013 5:27 PM
  • Hello Jeff, I was finally able to get my project working! The problem was I had 2 diff client id's and I was referring to the wrong one.

    The other problem was I was confusing :"https://appdev.microsoft.com"  with "https://manage.dev.live.com" when I was trying to get the correct client id's.

    Thanks for all your help.


    Service is the rent we pay for the space we take up on earth!

    • Marked as answer by M. Howard Tuesday, June 18, 2013 10:23 PM
    Tuesday, June 18, 2013 2:46 PM