1291746 - Startup Crash in java.lang.IllegalArgumentException: Could not convert String id to PanelType at org.mozilla.gecko.home.HomeConfig$PanelType.fromId(HomeConfig.java)

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Marcia Knous [:marcia]]

This bug was filed from the Socorro interface and is 
report bp-e20f2e36-ece8-4900-bed9-818cb2160803.
=============================================================

New crash showing up in early Firefox 48 Fennec data: http://bit.ly/2axSppa 

zh-CN locale is noted frequently in the comments.

Comment 1

[Marcia Knous [:marcia]]

ni on a few folks for ideas.

Comment 2

[Sylvestre Ledru [:Sylvestre]]

Sorry, stefan, not stephan :)

Comment 3

[Kevin Brosnan [Ex-Mozilla]]

https://crash-stats.mozilla.com/signature/?date=%3C2016-08-03T17%3A39%3A46&date=%3E%3D2016-07-27T17%3A39%3A46&product=FennecAndroid&version=48.0&signature=java.lang.IllegalArgumentException%3A%20Could%20not%20convert%20String%20id%20to%20PanelType%20at%20org.mozilla.gecko.home.HomeConfig%24PanelType.fromId%28HomeConfig.java%29&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=useragent_locale&_sort=-date&page=1

All crashers are zh-CN this is the Mozilla China build.

Comment 4

[Kevin Brosnan [Ex-Mozilla]]

DongShengXue has fixed problems with the Chinese apk before.

Comment 5

[DongShengXue]

Sure, I have fixed it. The reason is we have added a custom panel on the old version from 40 to 47, and removed the panel on the version 48, if users have installed some custom panel addon like 'my panel', when they update browser to 48, the panel that we had added will be not found in panelTypes, so the gecko throw the exception.

Comment 6

[Sebastian Kaspari (:sebastian; :pocmo)]

There are still crashes for this stack trace showing up: Is this really fixed?

Comment 7

[DongShengXue]

(In reply to Sebastian Kaspari (:sebastian) from comment #6)
> There are still crashes for this stack trace showing up: Is this really
> fixed?

Yes, we fixed it,but users need to update from buildId:20160727164219 to buildId:20160809120352.

Comment 8

[Sebastian Kaspari (:sebastian; :pocmo)]

Okay, I'll close this bug.