Home/ Questions/Q 8709245
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T04:19:16+00:00

For my application there is one tab host with 5 different activities for 5

  • 0

For my application there is one tab host with 5 different activities for 5 tabs. One of those is actually an activity group, which contain 4 child activities, and users can go back and fro for these child activities.

Now one of the child activities is used to post tweet. The OAUTH thing is fine. However I find that the callback cannot actually point back to the activity but the parent activity group or even the tab activity. I am not sure where does it points to but the outcome is that when the user authorize my twitter app, and return to the android app, the activity will be started all over and called onCreate instead of onResume or onNewIntent. This causes an infinity loop , asking the user to authenicate again and again. I have tried to add android:launch:singleInstance but this does not help.

If I do not start the activity as a child but a new activity, everything is fine.I can get back to onNewIntent and successfully post tweets. So I am quite sure the cause is activity group or tab activity.

I am actually not very familiar of how intent filter works under tab / activity group, can anyone explain the case for me?

Manifest.xml 

<activity android:name="TwitterAct" android:launchMode="singleInstance">
        <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="myapp" android:host="twitteract" />       
        </intent-filter>
</activity>

TwitterAct

private final String CALLBACKURL = "myapp://twitteract";

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This works for me: render the oauth web page in a WebView you control rather than launching out to the browser app.

    The oauth web page, when it calls its callback, will actually be replacing itself in the webview, where your WebViewClient can catch that expected URL, process the results, and finish() the webview (removing it from the activity stack).

    In other words, your manifest entries can go away. Your callback can be any URL, so long as you recognize it in the WebViewClient you create.

    • 0