Android开发 - 回调URL不工作...（0_o） [英] Android Dev - Callback URL not working... (0_o)

问题描述

我工作的一个Android应用程序为我的研究，我使用OAuth（路标库）合作，以获得从Web服务，这也是发展过程的一部分，访问用户数据。我能流过的OAuth的共同步骤，我用一个URI（回调到应用程序），并且可以得到的地方，我调用设备浏览器中的步骤，选择验证我的应用程序，下一步应该是要返回给应用重定向浏览器....

I'm working on an android application for my research, and I am working with OAuth (signpost library) to gain access to user data from a web service which is also a part of the development process. I am able to flow through the common steps of OAuth, and I use a Uri (for callback to the app), and can get to the step where I invoke the devices browser, choose to verify my app, and the next step is SUPPOSED to redirect the browser BACK to the application....

而我得到读取类似您没有权限打开一个错误：

Instead I get an error that reads something like "you do not have permission to open:

appSchema：//的appName authorizationSensitiveInfo ......   在后附肢'？'是   oauth_token和oauth_verifier从   服务（我们可以假设所有步骤   直到重定向是   纠正）。

appSchema://appName?authorizationSensitiveInfo..." the appendages after the '?' are the oauth_token and oauth_verifier from the service (we can assume all steps up until the redirection are "correct").

可能出现的问题在于在 appSchema：//的appName 部分。从我的理解，这是重定向URL，它告诉乌里使用手机的浏览器找到我的应用程序，并调用onResume（）方法。在哪里做的值appSchema：//的appName 来自（在清单中定义如果是的话在哪里呢？？）。

Possible problems lie within the appSchema://appName part. from my understanding this is the redirect URL which tells the Uri to use the phone's browser to locate my application and invoke the onResume() method. Where do the values for appSchema://appName come from (defined in manifest? if so where?).

为什么许可问题？我必须为我的URI来访问我的应用程序的权限？我迷路了......如果你需要code片段来帮助我请回复，我并没有包括任何code，因为这更像我只是错过了一个概念......我不是在我机，但现在我可以提供code。如果这将使事情变得更容易理解。真的打我的头在这里...

Why the problem with permission? Must I set permissions for my Uri to access my app? I'm lost...if you need code snippets to help me please reply, I didn't include any code because this is more like a concept I just missed...I'm not at my machine now but I can supply code if that would make things easier to understand. Really beating my head in here...

在RESPONE一个伟大的答案这里是我如何处理我在恢复

protected void onResume() {
    super.onResume();       
    Uri uri = this.getIntent().getData();
    if (uri != null && uri.toString().startsWith(CALLBACK_URL)) {
        Log.d("StepGreenM", uri.toString());
        String verifier = uri.getQueryParameter(OAuth.OAUTH_VERIFIER);
        Log.d("StepGreenM", verifier);
        try {

            provider.retrieveAccessToken(consumer, verifier);
            TOKEN = consumer.getToken();
            REQUEST_SECRET = consumer.getTokenSecret();

            Log.d("StepGreenM", TOKEN);
            Log.d("StepGreenM", REQUEST_SECRET);

        } catch (OAuthMessageSignerException e) {
            e.printStackTrace();
        } catch (OAuthNotAuthorizedException e) {
            e.printStackTrace();
        } catch (OAuthExpectationFailedException e) {
            e.printStackTrace();
        } catch (OAuthCommunicationException e) {
            e.printStackTrace();
        }
    }

    uri = getIntent().getData();
    if (uri != null && CALLBACK_URI.getScheme().equals(uri.getScheme())) {
        String token = settings.getString(HomeScreen.REQUEST_TOKEN, null);
        String secret = settings.getString(HomeScreen.REQUEST_SECRET, null);
        Intent i = new Intent(Intent.ACTION_VIEW); // Intent to go to the action view

        try {
            if(!(token == null || secret == null)) {
                consumer.setTokenWithSecret(token, secret);
            }
            String otoken = uri.getQueryParameter(OAuth.OAUTH_TOKEN);
            String verifier = uri.getQueryParameter(OAuth.OAUTH_VERIFIER);

            // We send out and save the request token, but the secret is not the same as the verifier
            // Apparently, the verifier is decoded to get the secret, which is then compared - crafty
            // This is a sanity check which should never fail - hence the assertion
            Assert.assertEquals(otoken, consumer.getToken());

            // This is the moment of truth - we could throw here
            provider.retrieveAccessToken(consumer, verifier);
            // Now we can retrieve the goodies
            token = consumer.getToken();
            secret = consumer.getTokenSecret();
            //Save it to a settings file
            HomeScreen.saveAuthInformation(settings, token, secret);
            // Clear the request stuff, now that we have the real thing
            HomeScreen.saveRequestInformation(settings, null, null);
            i.putExtra(USER_TOKEN, token);
            i.putExtra(CONSUMER_SECRET, secret);

            //GO TO APPLICATION

        } catch (OAuthMessageSignerException e) {
            e.printStackTrace();
        } catch (OAuthNotAuthorizedException e) {
            e.printStackTrace();
        } catch (OAuthExpectationFailedException e) {
            e.printStackTrace();
        } catch (OAuthCommunicationException e) {
            e.printStackTrace();
        } finally {
            startActivity(i); // we either authenticated and have the extras or not, but are going to the action view
            this.setContentView(R.layout.indivaction);
            finish();
        }
    }
}

不知道真正使这个散架......但就像我说的时候调用此方法它的力量关闭。我知道它使过去的重定向，因为我使用一个httpSniffer来检查邮件，并从服务器上...

Not sure what really makes this fall apart...but like I said it force closes when this method is invoked. I know it makes it past the redirect because I use an httpSniffer to check the messages to and from the server...

推荐答案

为了回调的URI，你需要添加一个意图过滤器类似于以下到你的活动清单，你想用它在正常工作。

In order for the callback uri to work properly you need to add an intent filter similar to the following to your manifest in the activity you want to use it in.

   <intent-filter>          
    <action android:name="android.intent.action.VIEW"/>     
    <category android:name="android.intent.category.DEFAULT"/>
    <category android:name="android.intent.category.BROWSABLE"/>
    <data android:scheme="appSchema" android:host="appName"/> 
   </intent-filter>

现在，如果你的活动正在使用singleInstance / singleTask，你应该使用类似下面的内容：

Now, if your activity is using singleInstance/singleTask, you should use something similar to the following:

@Override
public void onNewIntent(Intent intent)
{
    Uri uri = intent.getData();
    String oauthToken = uri.getQueryParameter("oauth_token");
    String oauthVerifier = uri.getQueryParameter("oauth_verifier");

    //...do what you need with the parameters
}

如果不使用singleTask或singleInstance，你可以做

if not using singleTask or singleInstance, you can do

@Override
public void onResume()
{
    Intent intent = getIntent();
    Uri uri = intent.getData();
    String oauthToken = uri.getQueryParameter("oauth_token");
    String oauthVerifier = uri.getQueryParameter("oauth_verifier");

    //...do what you need with the parameters
}

我认为这应该工作。

I believe this should work.

另外，如果我没有记错，您所提供的回调URL应该包括，所以appSchema：// APPNAME」？

Also, if I'm not mistaken, the callback url you provide should include the ?, so "appSchema://appName?"

这篇关于Android开发 - 回调URL不工作...（0_o）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！