1185444 - Can't install add-ons on Android M preview 2 (Nightly)

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: Add-on Manager, defect)

Description

[Sebastian Kaspari (:sebastian; :pocmo)]

Using a phone with Android M Preview 2 installed, I can't install add-ons. I tried installing from AMO and manually from SD card. No dialog / doorhanger to confirm the installation or toast "Downloading add-on" appears.

Screencast: http://youtu.be/apMQe8VgKGY

Only Nightly (42) seems to be affected. Add-ons can be installed on Aurora and Beta.

Comment 1

[:Margaret Leibovic]

Is there anything in the log? Could this be a problem with our prompt or doorhanger code?

I was worried that this might be related to signed add-ons, but that would affect 41 as well.

Comment 2

[Sebastian Kaspari (:sebastian; :pocmo)]

I looked briefly at the log and didn't see anything. I'll re-test later today and upload the log.

Comment 3

[Sebastian Kaspari (:sebastian; :pocmo)]

While debugging another crash (Navigating to Air Mozilla crashed Nightly every time) I cleared all data from Nightly and now everything is working as expected again.

Comment 4

[Sebastian Kaspari (:sebastian; :pocmo)]

WONTFIX. Will re-open if I'll ever run into this again.

Comment 5

[Sebastian Kaspari (:sebastian; :pocmo)]

And now it is happening again. I feel like it's somehow triggered by Android M's auto backup: bug 1185920. But I don't know why it's breaking yet.

Comment 6

[Mark Finkle (:mfinkle) (use needinfo?)]

We should investigate what's breaking this, just so we know the root cause. The simple fix, we hope, is toe block backup/restore of the add-ons related files in bug 1185920.

Comment 7

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Mark Finkle (:mfinkle) from comment #6)
> We should investigate what's breaking this, just so we know the root cause.
> The simple fix, we hope, is toe block backup/restore of the add-ons related
> files in bug 1185920.

I mean bug 1190375

Comment 8

[Sebastian Kaspari (:sebastian; :pocmo)]

I haven't been able to reproduce this for quite some time (and never on Preview 3 so far) - same with bug 1185923.

Could have been some "temporary" broken state from implementing support for restricted profiles (We had a bug that on an Android M device all restrictions were always enforced) together with auto backup.