BrowserActivity有泄漏窗口

Question

我有一个使用GCM推送通知的应用程序。当我把通知推送到我正在测试的手机(HTC Desire C、三星mini等)上时，它工作得很好。通知是修复了错误的应用程序的url。

通常情况下，推送被接收，一旦点击，浏览器打开并开始下载。下载完成后，用户可以点击通知图中的通知，应用程序就会安装/升级。

问题是当我试图在摩托罗拉defy mini XT320上运行这个。它可以接收推送，但浏览器在关闭之前打开了一秒钟左右，并且没有开始下载。

有人知道为什么吗?下面是我如何生成通知和错误。当浏览器打开时，我可以看到一个对话框突然弹出。我知道错误可能与此有关，因为这是一个泄漏的窗口错误。这个对话框不是我创建的，它是Android浏览器活动的一部分。

提前感谢。

 private static void generateNotification(Context context, String message) {
        int icon = R.drawable.ic_launcher;
        long when = System.currentTimeMillis();
        NotificationManager notificationManager = (NotificationManager)
                context.getSystemService(Context.NOTIFICATION_SERVICE);
        Notification notification = new Notification(icon, message, when);
        String title = context.getString(R.string.app_name);

        //Intent notificationIntent = new Intent(context, EntryActivity.class);
        Intent notificationIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(message));

        // set intent so it does not start a new activity
        notificationIntent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP |
                Intent.FLAG_ACTIVITY_SINGLE_TOP);
        PendingIntent intent =
                PendingIntent.getActivity(context, 0, notificationIntent, 0);
        notification.setLatestEventInfo(context, title, message, intent);
        notification.flags |= Notification.FLAG_AUTO_CANCEL;
        // Play default notification sound
        notification.defaults |= Notification.DEFAULT_SOUND;
        // Vibrate if vibrate is enabled
        notification.defaults |= Notification.DEFAULT_VIBRATE;
        notificationManager.notify(0, notification);     
    }

.

05-31 15:39:01.940: V/InputMethodManager(1310): focusOut: android.widget.EditText@408d6ca0 mServedView=android.widget.EditText@408d6ca0 winFocus=false
05-31 15:39:02.170: V/InputMethodManager(1310): focusOut: android.webkit.WebView@408bb1a0 mServedView=android.widget.EditText@408d6ca0 winFocus=false
05-31 15:39:02.180: V/browser(1310): BrowserActivity.onDestroy: this=com.android.browser.BrowserActivity@407ec730
05-31 15:39:02.290: E/WindowManager(1310): Activity com.android.browser.BrowserActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@408da548 that was originally added here
05-31 15:39:02.290: E/WindowManager(1310): android.view.WindowLeaked: Activity com.android.browser.BrowserActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@408da548 that was originally added here
05-31 15:39:02.290: E/WindowManager(1310):  at android.view.ViewRoot.<init>(ViewRoot.java:259)
05-31 15:39:02.290: E/WindowManager(1310):  at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:148)
05-31 15:39:02.290: E/WindowManager(1310):  at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:91)
05-31 15:39:02.290: E/WindowManager(1310):  at android.view.Window$LocalWindowManager.addView(Window.java:424)
05-31 15:39:02.290: E/WindowManager(1310):  at android.app.Dialog.show(Dialog.java:241)
05-31 15:39:02.290: E/WindowManager(1310):  at android.app.AlertDialog$Builder.show(AlertDialog.java:802)
05-31 15:39:02.290: E/WindowManager(1310):  at com.android.browser.BrowserActivity.onDownloadStart(BrowserActivity.java:3492)
05-31 15:39:02.290: E/WindowManager(1310):  at com.android.browser.Tab$4.onDownloadStart(Tab.java:1349)
05-31 15:39:02.290: E/WindowManager(1310):  at android.webkit.CallbackProxy.handleMessage(CallbackProxy.java:388)
05-31 15:39:02.290: E/WindowManager(1310):  at android.os.Handler.dispatchMessage(Handler.java:99)
05-31 15:39:02.290: E/WindowManager(1310):  at android.os.Looper.loop(Looper.java:130)
05-31 15:39:02.290: E/WindowManager(1310):  at android.app.ActivityThread.main(ActivityThread.java:3689)
05-31 15:39:02.290: E/WindowManager(1310):  at java.lang.reflect.Method.invokeNative(Native Method)
05-31 15:39:02.290: E/WindowManager(1310):  at java.lang.reflect.Method.invoke(Method.java:507)
05-31 15:39:02.290: E/WindowManager(1310):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:875)
05-31 15:39:02.290: E/WindowManager(1310):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:633)
05-31 15:39:02.290: E/WindowManager(1310):  at dalvik.system.NativeStart.main(Native Method)

[edit1]

 @Override
    protected void onMessage(Context context, Intent intent) {
        Log.i(TAG, "Received message");
        String message = intent.getExtras().getString("price");
        Log.e(TAG, "message from gcm = " + message);

        Uri Download_Uri = Uri.parse(message);
        DownloadManager.Request r = new DownloadManager.Request(Download_Uri);
     // This put the download in the same Download dir the browser uses
     r.setDestinationInExternalPublicDir(Environment.DIRECTORY_DOWNLOADS, "RR3UPGRADE");

     // Notify user when download is completed
     // (Seems to be available since Honeycomb only)
    // r.setNotificationVisibility(DownloadManager.Request.VISIBILITY_VISIBLE_NOTIFY_COMPLETED);
     // Start download
     DownloadManager dm = (DownloadManager) getSystemService(DOWNLOAD_SERVICE);
     dm.enqueue(r);
        displayMessage(context, message);
        // notifies user
        generateNotification(context, message);
    }

.

06-04 11:38:05.624: I/ActivityManager(207): Starting: Intent { act=android.intent.action.VIEW dat=content://downloads/all_downloads/63 typ=application/vnd.android.package-archive flg=0x10000001 cmp=com.android.packageinstaller/.PackageInstallerActivity } from pid 421
06-04 11:38:05.664: W/PackageParser(1203): Skipping dir: /all_downloads/63
06-04 11:38:05.664: W/PackageInstaller(1203): Parse error when parsing manifest. Discontinuing installation

Answer 1

不是摩托罗拉Defy Mini XT320浏览器问题的确切解决方案(这实际上可能是一个正常的操作，从某种意义上说，摩托罗拉可能已经决定在浏览器中限制下载可疑文件，并且检查，扩展名为。apk的文件可能非常危险)，但您实际上可以直接请求下载管理器下载您的文件。

参见https://stackoverflow.com/a/9033224/1893766获取示例代码。

Answer 2

我已经找到了下载管理器不能正常工作的原因，但仍然不确定原因。

// Start download
     DownloadManager dm = (DownloadManager) getSystemService(DOWNLOAD_SERVICE);
     dm.enqueue(r);
        displayMessage(context, message);
        // notifies user
        generateNotification(context, message);

.

在上面的代码中，当我启动下载管理器时，对displayMessage()和generateNotification()的后续调用似乎会干扰下载。当我注释掉随后的代码时，下载管理器似乎工作得很好。就像我说的，不知道为什么。