What is "oauth:"  Is that a standard scheme?  What you are doing here looks
broken, if some other app happens to handle "oauth:" then the user will need
to pick which to launch.  And if this isn't a standard scheme, you shouldn't
be making up schemes for your app.  They are a global namespace.  And this
is a good example of why making up schemes cause a problem -- you could very
easily have a conflict with another application using the same name.

Anyway, the browser currently is not intended to be used in the way you are
trying to, and I would strongly recommend against doing this.  First because
it is unlikely you will be able to get this to work completely correctly,
second because there is a very good chance that your app will break on
different devices since what you are doing here is not defined in any kind
of SDK API.

On Wed, Aug 5, 2009 at 3:05 AM, Carl H. <[email protected]> wrote:

>
> Hello,
>
> I am trying to have the browser part of my task. The reason being is
> that I am awaiting a callback from the browser before continuing. For
> instance I have the following in my manifest:
>
>                <activity android:name=".activities.OAuthActivity"
>                        android:permission="android.permission.INTERNET"
>                        android:launchMode="singleTop"
>                        android:noHistory="true">
>                        <intent-filter>
>                                <action
> android:name="android.intent.action.VIEW" />
>                                <category
> android:name="android.intent.category.BROWSABLE" />
>                                <category
> android:name="android.intent.category.DEFAULT" />
>                                <data android:scheme="oauth" />
>                        </intent-filter>
>                        <intent-filter>
>                                <action
> android:name="android.intent.action.INSERT" />
>                                <category
> android:name="android.intent.category.DEFAULT" />
>                                <data
> android:mimeType="vnd.android.cursor.dir/vnd.novoda.oauth" /
> >
>                        </intent-filter>
>                </activity>
>
> Now, in order to activate my app, I need the user to navigate to a
> certain page and press activate. This will redirect to "oauth:///"
> which will be catched by my activity. However this will be in a new
> Task (new task id). I guess it till be the task id of the browser. One
> solution would be to use "singleTask" as launch mode but then I can
> not be part of a full task...
>
> It seems that the browser can not really accept any flags regarding
> tasks and so forth. Any comments on the above?
>
> Thanks
> Carl
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>


-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to