I tried to install adblock today, and I got a popup saying something like "The adblock extension could not be installed bec..." Two problems here: 1) the notification doesn't wrap to the next line, so I never did find out why it could not be installed. 2) clicking on the notification should take me to a longer, more detailed explanation of what the "because" is; instead, it takes me to the addons page with no further explanation of what the failure was. Given how many people are going to try to install non-ported addons, fixing this is a major problem, IMHO, so marking major.
luis, can you provide a screenshot? flagging for triage
A quick google suggests that taking a screenshot requires either rooting or installing an SDK, neither of which I'm likely to have time to do soon. If someone wants to lend me their phone I'll be happy to take a literal picture of the screen. Steps to reproduce here are pretty easy: 1) go to amo 2) click on "popular" 3) click on ABP (tell it to install anyway, which I think is new?) 4) wait 5) get android notification saying "[b]Add-ons[/b] Adblock Plus could not be installed bec[fade] [timestamp]" 6) click on the notification, expecting details of why ABP could not be installed, get punted directly to the in-application addons search.
Talked about this the other day. We have limited space in the notification, and so ideally I think we want to marquee/ticker-text if it is too long. Android TextViews support this, but if the internet is to be believed they have to be focused to do the scrolling. Scrolling the text ourself seems a bit like overkill. Showing failed add-on installations in the add-on manager isn't something we really want to do either... Bug 615897 will cause this text to show as the ticker text. Alternatively, bug 619518 could let us use toaster notifications for this instead. Maybe one of those is enough to mitigate this problem?