Carol Yang [:cyang] Reporter
	Description • 10 years ago

For testing purposes, I removed costcontrol app at runtime by doing:

 adb shell rm -r /system/b2g/webapps/costcontrol.gaiamobile.org
 adb reboot

After the device reboots, the device never boots into homescreen.

This is only an issue on master gaia. When doing the same thing on v2.0 gaia, the device will boot into homescreen.

	bhavana bajaj [:bajaj]
	Comment 1 • 10 years ago

carol, can you confirm you still hit this on latest 2.1? Thanks!

	Carol Yang [:cyang] Reporter
	Comment 2 • 10 years ago

(In reply to bhavana bajaj [:bajaj] from comment #1)
> carol, can you confirm you still hit this on latest 2.1? Thanks!

Hi Bhavana,

Yes, I still see this. The gaia/gecko versions I have for refs/heads/mozilla/master are:

gaia: 04ea7e1a4034a50d4a7a4f5b95a04a2ed8313908
gecko: c60b44a7b137ed1ebb3444efebb089d755424d54

	Carol Yang [:cyang] Reporter
	Comment 3 • 10 years ago

Note that I stumbled upon this because I was still having problems similar with bug 1033095. By removing the costcontrol app, I no longer saw the AbortError issue.

	Kevin Grandon :kgrandon
	Comment 4 • 10 years ago

This is not a supported feature - we can't just go into adb shell and start removing arbitrary directories and hope for things to work. 

The proper way to do this would be either a build time config or a call to mozApps.mgmt.uninstall().

My recommendation here is to use a build time config here, but we can alternatively do it with a marionette script or similar.

	Anshul
	Comment 5 • 10 years ago

(In reply to Kevin Grandon :kgrandon from comment #4)
> This is not a supported feature - we can't just go into adb shell and start
> removing arbitrary directories and hope for things to work. 
> 
> The proper way to do this would be either a build time config or a call to
> mozApps.mgmt.uninstall().
> 
> My recommendation here is to use a build time config here, but we can
> alternatively do it with a marionette script or similar.
Kevin, we understand your frustration, however the only reason we are removing this app is because Mozilla is not owning to fix the issues with the cost control app to begin with. Since the app is only affecting our internal testing, we would only like to remove the app during the test and not compile out at build time as the builds used for testing is the same build that goes out to customers.

Since removing the app was working on 2.0 we are expecting it to work on 2.1. Perhaps our expectations are not inline with yours. Carol and I will look at other alternatives.

	Kevin Grandon :kgrandon
	Comment 6 • 10 years ago

Do you have access to marionette on the device? We can write a simple script to execute_script() and uninstall the application if so.

Here is a script we use from marionetteJS and I think something similar should work from python: https://github.com/mozilla-b2g/gaia/blob/master/apps/system/test/marionette/lib/app_install.js#L99

	Anshul
	Comment 7 • 10 years ago

Kevin, since this was working fine in 2.0 I consider this a regression. We actually have a patch with a two line change that resolves the issue. Would you like to look at the patch, may be that will change your mind?