Android平台Strava API OAuth2配置及回调URL无效调用咨询

Hey there! Let's work through this callback URL problem you're hitting with Strava's API and Scribe on Android. I've tackled similar OAuth2 setup headaches before, so here are the key areas to check:

1. Validate Strava Developer Dashboard Callback Match #

• First things first: Double-check that the callback URL entered in your Strava Developer Dashboard (under your app's settings) is an exact, character-for-character match with what's in your code. Even a missing slash, wrong scheme, or extra space will break the callback flow.
• For Android, common callback formats are your.app.package.name://callback or a custom scheme like strava-oauth://callback—make sure this string is identical in both places.

2. Audit Your Scribe Service Implementation #

• In MainActivity's onCreate(), confirm you're passing the correct callback URL when initializing the OAuthService:

  OAuthService service = new ServiceBuilder()
      .apiKey(CLIENT_ID)
      .apiSecret(CLIENT_SECRET)
      .callback(YOUR_EXACT_CALLBACK_URL) // Must match Strava dashboard!
      .build(StravaOAuth2Api.instance());
  

• In your StravaOAuth20ServiceImpl, verify the token and revocation endpoints are using Strava's official URLs:
  • Token endpoint: https://www.strava.com/oauth/token
  • Revocation endpoint: https://www.strava.com/oauth/deauthorize
    Typos here can silently break the flow even if the callback itself is correct.

3. Fix Android Manifest Intent Filter #

• Android won't route the callback back to your app unless you add an intent filter to your AndroidManifest.xml. Here's a working example tailored to custom scheme callbacks:

  <activity android:name=".MainActivity">
      <intent-filter>
          <action android:name="android.intent.action.VIEW" />
          <category android:name="android.intent.category.DEFAULT" />
          <category android:name="android.intent.category.BROWSABLE" />
          <!-- Replace with your callback's scheme and host -->
          <data
              android:scheme="your.app.package.name"
              android:host="callback" />
      </intent-filter>
  </activity>
  

• If you're using a unique custom scheme (not your package name), ensure it's distinct to avoid conflicts with other apps.

4. Handle the Callback Intent in Your Activity #

• You need to capture the callback intent in MainActivity to extract the authorization code. Override onNewIntent() (if using launchMode="singleTop") or check the intent in onCreate():

  @Override
  protected void onNewIntent(Intent intent) {
      super.onNewIntent(intent);
      Uri callbackUri = intent.getData();
      if (callbackUri != null && callbackUri.getScheme().equals(YOUR_CALLBACK_SCHEME)) {
          String authCode = callbackUri.getQueryParameter("code");
          // Exchange code for access token with Scribe
          Verifier verifier = new Verifier(authCode);
          Token accessToken = service.getAccessToken(null, verifier);
      }
  }
  

• If your activity isn't using singleTop, the callback intent will be delivered to onCreate() when the app is reopened.

5. Test with a Simplified Callback URL #

• If you're still stuck, try a stripped-down callback like com.your.app://strava-test (update both the dashboard and your code). Sometimes complex URLs with special characters or long paths can cause unexpected failures that are hard to spot.

6. Avoid HTTPS/HTTP Mix-Ups #

• Strava requires mobile app callbacks to use a custom scheme (not http or https). Web apps use https, but for Android, stick to your app-specific scheme—using http will get your callback rejected outright.

If none of these steps fix the issue, sharing snippets of your StravaOAuth2Api class or manifest setup could help narrow things down further!

内容的提问来源于stack exchange，提问作者Niels Vanwingh