Android Question WebView-problem with Pushbullet oauth-client

Discussion in 'Android Questions' started by DonManfred, Feb 15, 2015.

  1. DonManfred

    DonManfred Expert Licensed User

    I´m writing a Pushbullet library/class together with @udg
    Pushbullet allows to use the sdk for another account using oauth.
    The user will be forwarded to pushbullet-site using a webview. The user log into into his account and gave access or decline the use and then he get forwarded to a return-url and token should be o this url too.
    I can catch it then in urloverride event.

    But at the last step the user dont get forwarded to the return url. Instead a error message appears on pushbulletsite (in webview) saying something like:

    A setting Pushbullet requires to work is disabled in your browser (Local Storage). Please contact us at ...

    I already send a mail to them asking whats wrong but waiting for answer.

    Maybe someone here has an idea what´s going wrong here. Maybe i just need to set something special in webview setting somehow?

    I would really appreciate if someone could give an advice here :)

     
    Last edited: Feb 15, 2015
  2. warwound

    warwound Expert Licensed User

    DonManfred likes this.
  3. DonManfred

    DonManfred Expert Licensed User

    I´m not sure. Maybe

    Can i change this setting with webview extras (or wve2)?

    Edit:
    Code:
    Activity.LoadLayout("oauth")
        we.Initialize(www)
        
    Dim ws As WebSettings = we.GetSettings
        ws.SetDOMStorageEnabled(
    True)
    now i can go one step further... Seems to work.
    But now it stuck when i click on Approve

    Anyway: THANK YOU very much, @warwound !! Your hint was perfect it seems.
     
    Last edited: Feb 15, 2015
  4. DonManfred

    DonManfred Expert Licensed User

    Edit. It works... In my tests i changed the returnurl. That was my fault. Set back the one i created to use for this and now the approvement works.
    Code:
    OverrideUrl(http://pushbullet.basic4android.de/?state#access_token=xxxxxxxxxxxxx)
    Now i can go one step further and try to use this token as described in sdk....

    THANKS AGAIN @warwound ! :)
     
  5. merlin2049er

    merlin2049er Well-Known Member Licensed User

    Great, looking forward to seeing this!
     
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice