Bill Noel

My feedback

  1. 32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Notification Hubs  ·  Flag idea as inappropriate…  ·  Admin →
    Bill Noel commented  · 
    Bill Noel commented  · 

    Frankly, this will be very important. The push notification solutions in Flutter are pretty weak at the moment, with no background support and so on. We've moved from Xamarin Forms to Flutter for performance reasons and the groundswell of support is pretty astonishing.

    There is a recent OSS package that is supposed to help with this: https://github.com/nextbss/flutter-push-notification

    Not sure if it's a keeper, I haven't tried to work with it yet.

    In my case I had this whole thing working in XF. If the app was in the foreground, it caught the notification and decided what to do. If it wasn't running, then the background application could launch it or just drop something into the notification center.

    It seemed to work pretty well. My understanding of the Flutter messaging is that it *all* runs through FCM, even on iOS devices.

    I much prefer ANH and the direct to device approach, but there's very little documentation on how to do it properly for Flutter.

    If you need help with this, I can try to work with it. TIA

    FWIW - I am in the middle of this right now.

    Bill Noel supported this idea  · 
  2. 53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Notification Hubs  ·  Flag idea as inappropriate…  ·  Admin →
    Bill Noel supported this idea  · 
  3. 96 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Bill Noel commented  · 

    If you're set up to use email for the login AND you access that the first email in the EMAILS claim that comes back is probably their login name, then you can extract it on the client side.

    And that's silly.

    To do it right, there needs to be an actual claim that contains the login name. This would work for all scenarios.

    I had to make a workaround for this - I access the graph during login. It works, but it adds an extra 500ms to each login and I have to do it server side if I want a solution that can choose either user name or email.

    I know it's not planned, but it should be.

    Bill Noel supported this idea  · 

Feedback and Knowledge Base