Fixed
Status Update
No update yet.
Comments
ha...@google.com
lo...@gmail.com
From my testing, version 8.0.2 also worked fine without uninstalling the app, but version 8.1.0 started with this behaviour. If this is intended, please at least provide an option to configure whether the app should be uninstalled after the tests.
ga...@google.com
zi...@gmail.com
Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.
am...@google.com
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:
al...@truecaller.com
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?
ke...@gmail.com
Looking forward to having this implemented. As has been mentioned automatic threading based on subject is a big no-no for our enterprise. We get automated reports and other documents sent to us by customers and suppliers and they are lumped together in threads making it very difficult for me to let Apps Script process them automatically since labels (i.e. outlook folders) have to be applied to entire threads (even though the messages in these threads often need to be treated differently).
mi...@gmail.com
Please add this function (and message.getlabel too) we need to scan message not only the thread.
sp...@google.com
Will there be any progress on this issue? Threading is great for humans, but if you are scripting, accessing and manipulating individual messages is MUCH more important, especially if it can be done from the normal user interface. Anything you can do to the thread you should be able to do at the message level.
am...@pspdfkit.com
Unassigning
ar...@google.com
Activate advanced google services/gmail api and use the gmail api functions.
I have resolved the same issue :)
I have resolved the same issue :)
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Iguana | 2023.2.1 Canary 7
- Android Gradle Plugin 8.3.0-alpha07
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
go...@gmail.com
Confirmed on my end that it works in Canary 7 + AGP 8.3.0-alpha07.
sk...@gmail.com
Please consider backporting to Hedgehog betas. Without it, we will have to live many months without the workaround.
je...@google.com
This was cherrypicked into H-RC1
lu...@gmail.com
Que?
an...@google.com
The fixes for this issue are now also available in:
- Android Studio Hedgehog | 2023.1.1 RC 1
- Android Gradle Plugin 8.2.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
ig...@monzo.com
Tried those both:
Android Studio Hedgehog | 2023.1.1 RC 1
Android Gradle Plugin 8.2.0-rc01
Unfortunately, the app was still removed after running the test.
I've tried even the latest Iguana nightly. Same results.
Android Studio Hedgehog | 2023.1.1 RC 1
Android Gradle Plugin 8.2.0-rc01
Unfortunately, the app was still removed after running the test.
I've tried even the latest Iguana nightly. Same results.
da...@gmail.com
Checked on Android Studio Hedgehog | 2023.1.1.
The issue is reproduced.
The issue is reproduced.
dm...@gmail.com
I updated Android Gradle Plugin to 8.2.0 and added "android.injected.androidTest.leaveApksInstalledAfterRun=true" to gradle.properties.
It solved the problem!
woho!
thx!
It solved the problem!
woho!
thx!
sh...@gmail.com
Same here.
Updated AGP to 8.2
Added "android.injected.androidTest.leaveApksInstalledAfterRun=true" to gradle.properties
Now the app is not uninstalled after running my Unit testing.
Thanks
Updated AGP to 8.2
Added "android.injected.androidTest.leaveApksInstalledAfterRun=true" to gradle.properties
Now the app is not uninstalled after running my Unit testing.
Thanks
sh...@gmail.com
mg...@gmail.com
If I understand correctly, don't instrumented tests have at least 2 APKs? One for the app, and one for the test runner? Can we configure AGP to uninstall the test runner but not the app?
Description
1. Describe the bug or issue that you're seeing.
AGP 8.1.0 uninstalls app after running instrumented tests - 7.4.2 does not
3. If you know what they are, write the steps to reproduce:
Install a debug variant of your app onto a device.
Run instrumented tests targeted that app.
In AGP < 8.x, the app was kept on the device (expected behavior).
In AGP >= 8.x, the app is uninstalled.
Build: AI-223.8836.35.2231.10406996, 202306290837
AI-223.8836.35.2231.10406996, JRE 17.0.6+0-17.0.6b829.9-10027231x64 JetBrains s.r.o., OS Mac OS X(aarch64) v13.5, screens 3456.0x2234.0, 2560.0x1440.0, 2560.0x1440.0
AS: Giraffe | 2022.3.1
Kotlin plugin: 223-1.8.0-release-345-AS8836.35.2231.10406996
Android Gradle Plugin: 8.1.0
Gradle: 8.1
Gradle JDK: JetBrains Runtime version 17.0.6
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
```