New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scoped Storage targetSdk 29+ without requestLegacyExternalStorage #43
Comments
@viclovsky check this and my ticket, pls |
Need to merge #54 |
@QAutomatron #54 merge fixed your problem? Because I have the same error. |
@anriijmind it's seems fixed for this exact error but our tests still not working due to other errors within |
I can't fix it on 29-30 android API. At 28 it works.
And add same to the manifest in the folder with tests, doesn't work
And adb command doesn't help
|
@anriijmind I don't know all details of what are you doing wrong, but with 2.2.4 version it is working right now ( we have only 29 and 30 sdk devices ) |
@SergKhram How can I change the directory for allure reports? I set in allure.properties path but it concatenates with default folder -> /storage/emulated/0/data/user/0/my_package/allure-results |
debug PropertiesUtils - resultsDirectoryPath |
@SergKhram I've figured out with permission for API 29-30 but in my mind, it better adds some information for documentation. So before tests I always clear data with
and Early I'd found example with granting permissions via @rule but when I tried it was not working because it needed allure adb-server off-cause which I had not started.
|
This did it for me (Orchestration, API 29 emulator) - perhaps you should consider adding this to the README @viclovsky |
Do you have plan to update targetSdk in allure-android and rework file storing?
allure-kotlin/allure-kotlin-android/src/main/kotlin/io/qameta/allure/android/internal/TestUtils.kt
Line 23 in 205ac53
https://developer.android.com/about/versions/11/privacy/storage
https://developer.android.com/training/data-storage/use-cases
as result now we crashed with this:
The text was updated successfully, but these errors were encountered: