Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit efa3acdd authored by vadimt's avatar vadimt
Browse files

Making LauncherProvider think that clear-db request comes from Launcher 

If it comes from the test process, the request won't be honored.

Bug: 159728364
Change-Id: I90029c1198634f1f1e94f61ba8ab9b41609d9ad5
parent b1e003c1

ext_tests/src/com/android/launcher3/testing/DebugTestInformationHandler.java

+11 −5
Original line number Diff line number Diff line
@@ -23,6 +23,7 @@ import static com.android.launcher3.util.Executors.MAIN_EXECUTOR; 
import android.content.Context;

import android.graphics.Bitmap;

import android.graphics.Color;

import android.os.Binder;

import android.os.Bundle;

import android.os.Debug;

import android.system.Os;
@@ -171,11 +172,16 @@ public class DebugTestInformationHandler extends TestInformationHandler { 
            }



            case TestProtocol.REQUEST_CLEAR_DATA: {

                final long identity = Binder.clearCallingIdentity();

                try {

                    LauncherSettings.Settings.call(mContext.getContentResolver(),

                            LauncherSettings.Settings.METHOD_CREATE_EMPTY_DB);

                    MAIN_EXECUTOR.submit(() ->

                            LauncherAppState.getInstance(mContext).getModel().forceReload());

                    return response;

                } finally {

                    Binder.restoreCallingIdentity(identity);

                }

            }



            default: