Fenix: FNX2-15219 ⁃ [Bug] Failed to query installed add-ons

Created on 8 Jul 2020 · 38Comments · Source: mozilla-mobile/fenix

Steps to reproduce

After last nightly update i am getting an error in addon page. Failed to query add-ons

Expected behavior

It should show the add ons

Actual behavior

Failed to query add ons

Device information

Android device: ? A10
Fenix version: ? latest nightly

Screenshot UNITO-UNDERSCORE!20200709-025104!

WebExtensions engverified 🐞 bug

Source

sheikh-azharuddin

👍6 👀1

Most helpful comment

Removing QA needed, I can reproduce on my device and see the problem. We're getting an error when querying installed extensions via GeckoView:

2020-07-09 10:10:40.691 18012-18012/? E/mozac-webextensions: Failed to query installed extensions
    java.lang.Exception: Unexpected error: TypeError: can't access property "hasPermission", extension is undefined
        at org.mozilla.geckoview.CallbackResult.sendError(CallbackResult.java:2)
        at org.mozilla.gecko.EventDispatcher$JavaCallbackDelegate$1.run(EventDispatcher.java:3)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:214)
        at android.app.ActivityThread.main(ActivityThread.java:7356)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

We'll track down the cause.

csadilek on 9 Jul 2020

👍6

All 38 comments

@cadeyrn

sheikh-azharuddin on 9 Jul 2020

@sheikh-azharuddin Please do not mention me for no reason. I have nothing to do with the issue and can't help.

cadeyrn on 9 Jul 2020

Developers listen to you.... Thats why i mentioned you
One more thing you have nothing to do why do you care to reply on every thread/issue

sheikh-azharuddin on 9 Jul 2020

👎7

Developers listen to you.... Thats why i mentioned you

They listen to me as they listen to every other user. And as every other user I can only share my opinions, I can't influence any decision or accelerate the fixing of a bug. If there is a bug, they will fix it. But I can't even reproduce the issue.

One more thing you have nothing to do why do you care to reply on every thread/issue

Not even close…

I have nothing to do with _this_ issue. And the only reason I commented here is that you mentioned me. So I had to clarify (again) that I can't do anything for you. I am user, not a developer of this product. Of course I comment on other issues when I have an opinion about something. But I can't have an opinion about something that does not affect me.

cadeyrn on 9 Jul 2020

👍6 👎1

@sheikh-azharuddin I can reproduce the bug on latest nightly certainly. But it's not right to assume that developers are ignoring or not responding to the issue, your bug report don't even passed a day to say this. And not every bug report is personally send to the developers phone, and they don't always have to work and plus also have life outside github and coding. You can see if you have subscribed to the repo that the work is completely halted so they having life outside the work doing their daily routine.
Yes this is a big issue and the developer working on add-on or QA will notice the issue and prioritise work accordingly. So the best thing would be wait for a response 😊 before tagging any members.

Scripterr on 9 Jul 2020

👍5

I understand that... But see from my viewpoint... This add on thing is a critical issue.. Yes there are other issues like browser crash when opening from custom tab which is manageable but this thing cannot be... The reason I tagged because this bug came in yesterday's build but they didn't fix and today one more version was released with same bug.... So wondering do developers really go through the basic features after build is complete...

sheikh-azharuddin on 9 Jul 2020

👎2 👍2

I can reproduce this also...

LittleAngelwings on 9 Jul 2020

👍1

[copied from [12420](https://github.com/mozilla-mobile/fenix/issues/12420#issuecomment-656050481)]

I can reproduce on the same Nightly version (200709), device is a Xperia Z2 on Android 6.0.1. My add-ons are still working but I cannot access them. It still worked on yesterday's Nightly (200708) so the regression range should be in this period.

hwinnemoe on 9 Jul 2020

👍3

@hwinnemoe no worries take your time... Atleast someone from Dev team acknowledged that is enough for me... And acknowledged means soon to be fixed 😉
It was not working on 8th Jul 6pm GMT build... I have raised the case before today's build...

sheikh-azharuddin on 9 Jul 2020

Please don't forget that nighly builds can be unstable, if such errors are a blocker for you, you should install beta or release versions alongside nighly and use them as primary browser to be safe.

Dunexus on 9 Jul 2020

👍4

👋 I'm trying to figured out what it the pattern to reproduce the issue. So far what I have found in common on people that are able to reproduce it's running Android 6.0.1 on Sony Xperia devices, does anyone is able to reproduce with other OS version or devices? Thanks in advance.

Amejia481 on 9 Jul 2020

I see it on Android 10.

lnicola on 9 Jul 2020

👍4

Thanks @lnicola

Amejia481 on 9 Jul 2020

Are there any logs I could check (e.g. adb logcat)?

lnicola on 9 Jul 2020

If you could post the logs from when the issue is happening it would be pretty helpful.

Amejia481 on 9 Jul 2020

Removing QA needed, I can reproduce on my device and see the problem. We're getting an error when querying installed extensions via GeckoView:

2020-07-09 10:10:40.691 18012-18012/? E/mozac-webextensions: Failed to query installed extensions
    java.lang.Exception: Unexpected error: TypeError: can't access property "hasPermission", extension is undefined
        at org.mozilla.geckoview.CallbackResult.sendError(CallbackResult.java:2)
        at org.mozilla.gecko.EventDispatcher$JavaCallbackDelegate$1.run(EventDispatcher.java:3)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:214)
        at android.app.ActivityThread.main(ActivityThread.java:7356)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

We'll track down the cause.

csadilek on 9 Jul 2020

👍6

Indeed, reproducible on the latest Firefox Nightly 200709 from 7/9 using a Gogle Pixel 3a (Android 10)

► Video
20200709-172218

AndiAJ on 9 Jul 2020

👍2

GV bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1651697

csadilek on 9 Jul 2020

👍3

FYI... I have this issue on Samsung Galaxy Tab A6 SM-T580 with Android 8.1.0 and also on my phone Huawei P Smart (2018) with Android 9.1.0.

LittleAngelwings on 9 Jul 2020

This is fixed now in latest build...👍

On a side note custom tab crash on clicking open in browser also fixed... The intermittent laggy issue seems fixed in this build

sheikh-azharuddin on 9 Jul 2020

Unfortunately, there's a caching issue involved here so this can re-appear in Nightly until https://bugzilla.mozilla.org/show_bug.cgi?id=1651697 is fixed. We're working on it.

csadilek on 10 Jul 2020

👍4

Just chiming in, can recreate everty time on my Moto G5+ with Android 8.1. Just started with the latest version:

Nightly 200709 06:10 (Build #21910618)
AC: 50.0.20200708130551, 8ce4bdb18
GV: 80.0a1-20200707094747
AS: 61.0.7

This effectively kills my Nightly because I had NoScript installed and now I can't whitelist new sites because I can't access the setting to allow or disable.

quadriflax on 10 Jul 2020

👍2

Just chiming in, can recreate everty time on my Moto G5+ with Android 8.1. Just started with the latest version:

Nightly 200709 06:10 (Build #21910618)
AC: 50.0.20200708130551, 8ce4bdb18
GV: 80.0a1-20200707094747
AS: 61.0.7

Use the latest version and check once. It is fixed.
200709 18:00
https://firefox-ci-tc.services.mozilla.com/tasks/index/project.mobile.fenix.v2.production/latest.

sheikh-azharuddin on 10 Jul 2020

👍1

Issue popped up again in today's build
Nightly 200710 06:01 (Build #21920613)

sheikh-azharuddin on 10 Jul 2020

👍1

Same issue again on Nightly 200710
Device: Oneplus 7 (Android 10)

paritosh9199 on 10 Jul 2020

No problems with this nightly via Play Store

Nightly 200711 06:00 (Build #21930608)
AC: 50.0.20200710130140, b54541be1
GV: 80.0a1-20200709093347
AS: 61.0.7

LittleAngelwings on 11 Jul 2020

OK, on the latest build from FirefoxCI the issue is back

Nightly 200711 18:01 (Build #21931809)
AC: 50.0.20200710130140, b54541be1
GV: 80.0a1-20200709093347
AS: 61.0.7

LittleAngelwings on 12 Jul 2020

👍1

There was no fix yet and as said in a previous comment: "there's a caching issue involved" - that's (probably) why it sometimes happens and sometimes not.

cadeyrn on 12 Jul 2020

👍1

Similar to @quadriflax, this disallows me from whitelisting sites since I had NoScript installed, so Nightly is unusable for me for most new sites.

Pixel 3a, Android 10
Nightly 200716 16:22 (Build #21980630)
AC: 50.0.20200712190143, 22f032ca7
GV: 80.0a1-20200711092223
AS: 61.0.7

TEWatson on 16 Jul 2020

👍1

This is fixed for me now

andreicristianpetcu on 18 Jul 2020

strange. I updated and it's broken again.

andreicristianpetcu on 18 Jul 2020

This is fixed for me now

strange. I updated and it's broken again.

Read above. There is a bug where this can happen on and off. It's not fixed yet. What works now may break again then work, then break, etc, until they fix this bug.

quadriflax on 18 Jul 2020

👍2

https://bugzilla.mozilla.org/show_bug.cgi?id=1651838 has landed in Nightly, so the immediate trigger for this bug has been fixed.

@agi90 Can this bug be closed now? If QA wants to verify the fix, the STR are at https://bugzilla.mozilla.org/show_bug.cgi?id=1651838#c2

Rob--W on 21 Jul 2020

@Rob--W the fix will land in the next Fenix Nightly (tomorrow morning EST). Then we can ask QA to verify :).

csadilek on 21 Jul 2020

👍1

Ok, a new version is currently rolling out that has the fix: Nightly 200721 13:47.

csadilek on 21 Jul 2020

❤1

Hi @csadilek , I've just re-checked this matter using the following devices:
• Google Pixel 3a (Android 10)
• OnePlus A3 (Android 6.0.1)

✔️ Performed the following updates and everything seems to be working properly

Nightly 200721 GV: 80.0a1-20200720094507
⇓
Nightly 200722 GV: 80.0a1-20200721094241
⇓
Nightly 200723 GV: 80.0a1-20200722094100
⇓
Nightly 200724 GV: 80.0a1-20200722094100
⇓
Nightly 200725 GV: 80.0a1-20200723095657
⇓
Nightly 200726 GV: 80.0a1-20200724093206
⇓
Nightly 200727 GV: 80.0a1-20200724093206
⇓
Nightly 200728 GV: 80.0a1-20200724093206