The Fallback application is an emulator-only application.
It contains an activity that accepts a lot of intents with a very low priority.
When an intent is fired and no other application accepts it, then the
Fallback activity receives it to display the "not implemented"
message.
Of course, this only works with intents defined by the platform. If
you send an intent that you created, you will get a crash.
We figured this would help differentiate errors and cases where a
default application is not bundled with the emulator.
For instance clicking Settings in the menu of the HOME application
will show this instead of crashing because it's just a matter of the
Settings app not being bundled with the emulator.
Xav
On Sun, Sep 28, 2008 at 11:25 AM, friedger <[EMAIL PROTECTED]> wrote:
>
> There is something like com.android.fallback.Fallback
>
> If I click on google reader in the browser and select All items I get
> a customized error message ("Unsupported action") instead of an
> ActivityNotFoundException or so.
>
> This customized error message is trigger by the following intent:
> Intent { action=android.intent.action.VIEW
> categories={android.intent.category.BROWSABLE}
> data=mailto:[EMAIL PROTECTED] comp={com.android.fallback/
> com.android.fallback.Fallback} }
>
> Does anybody know anything about Fallback?
>
> Could this be related to the feature reqeuest for a "fallback" intent
> (http://code.google.com/p/android/issues/detail?id=910)?
>
> Cheers,
> Friedger
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
