Assigned
Status Update
Comments
ra...@google.com <ra...@google.com> #2
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
mi...@batmaid.com <mi...@batmaid.com> #3
Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.
ra...@google.com <ra...@google.com> #4
As an additional alternative, it should be possible to specify a label in the options for GmailApp.sendEmail().
A work-around is proposed in StackOverflow:http://stackoverflow.com/a/18727687/1677912
A work-around is proposed in StackOverflow:
sh...@citi.com <sh...@citi.com> #5
Are there any news on adding the ability to archive and add a label to specific emails (not threads)? From a corporate shared mailbox perspective auto threading emails by subject is a serious issue (eg. we recive two emails from the same person with same subject but with different description).
Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?
Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?
Description
- Steps to reproduce the problem (including sample code if appropriate)
This happens in prod only and 100% in background
- What happened.
Firebase crashes in prod are getting reported from the chromium-TrichromeWebviewGoogle.
Logs :
main (runnable):tid=1 systid=12197
at android.hardware.input.InputManagerGlobal.registerInputDeviceListener(InputManagerGlobal.java:394)
at android.hardware.input.InputManager.registerInputDeviceListener(InputManager.java:493)
at org.chromium.ui.events.devices.InputDeviceObserver.addObserver(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:24)
at J.N._J_J(Native method)
at org.chromium.android_webview.AwContents.<init>(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:441)
at com.android.webview.chromium.l.run(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:147)
at WV.sZ.b(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:20)
at WV.rZ.run(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:3)
at org.chromium.base.task.PostTask.d(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:12)
at WV.sZ.a(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:23)
at com.android.webview.chromium.WebViewChromiumFactoryProvider.a(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:3)
at com.android.webview.chromium.WebViewChromium.init(chromium-TrichromeWebViewGoogle6432.aab-stable-683416333:328)
at android.webkit.WebView.<init>(WebView.java:447)
at android.webkit.WebView.<init>(WebView.java:367)
at android.webkit.WebView.<init>(WebView.java:349)
at android.webkit.WebView.<init>(WebView.java:336)
at android.webkit.WebView.<init>(WebView.java:326)
at com.adobe.marketing.mobile.GriffonWebViewSocket$1$1.run(unavailable:14)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at android.app.ActivityThread.main(ActivityThread.java:8919)
at java.lang.reflect.Method.invoke(Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
- What you think the correct behavior should be.
Should not see the ANRs in prod. We have adobe sdk added and logs show that the web view is used from the adobe sdk. But even then trichrome web view should handle the main thread gracefully instead of causing ANR.
- Is this a security related issue? No
Happening in all android versions and in background for all