correct me if I am not understanding something
have something to do with
figure it out
1 out 5 devieces
might be a clue
Thanks all, we are treating this with high pri and will get back to everyone later today.
IF YOU DONOT CONSUME MAP ANDROID (ON STOCK ANDROID OR FIREOS) YOU CAN STOP READING NOW.
If you don't useRuby/JRuby at Amazon, you can disregard this message.
As Dr Smith left he said that the inquiry was something of a red herring. 熏青鱼,转移注意力的话
史密斯博士离开时说这次调查只是为掩人耳目。
A blank line after the local variable declaration will improve readability
Dangling space at EOL
This should indent 8 spaces for line continuation.
Can you guard this with a debug constant to avoid the log?
This seems more like a warning.
Is this a warning or expected case? It looks expected. If expected, info level might make more sense.
WS after if
More debug constant.
Verified this is fixed with the posted steps and a few permutations of the repro steps. Closing.
Suchfailure only happened several times, can be recovered soon
There’s no sign that these devices are rooted orcorrupted
Based on above information, we tend to believeit’s an intermediary failure during Goodreads OTA, but system logs when failurehappens would be necessary to root cause while currently no new crash isobserved since
Goodreads OTA was paused
Reproduceit locally with GMS installed in data partition (we don’t have a theory butworth trying given 15/20 failure devices have GMS installed).
While it is not necessary to root to install Google Play Services,I have found that rooting devices is highly correlated with installing Google'scomponents. It is easy to find turnkey recipes for putting Google Play ontoFire devices that including installing a custom recovery and rooting. If a userroots the device, they are very likely to modify the device further, likeinstalling other launchers, and uninstalling apps that they don't use, and thisgives us lots of crash noise when other components that remain trigger launchesof an app that is no longer there (e.g. by sending it an intent). I suspectthat the high crash count cases are devices where Goodreads has been removedlike this. The only way to tell for sure that this is the case is by capturinga bugreport in such a device, but if the device is so hacked up that it nolonger responds to log pull requests, modifying a device similarly andverifying that you get the a similar log signature may be your only option.
is not a blocker – I would moveit down to critical. Thoughts?
So our release is stillhalted until we get a confirmation on the root-cause. I would recommend weleave the bug as a Blocker until then.
I would likethe monitoring to be done by App team as they periodically look at thedashboard. Make sense?
The patch build looks good to me, once the below concerns are addressed I can give the CR a "ship it".