Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

For #9830: Do not request/use WRITE_EXTERNAL_STORAGE on Android 11 and above #10686

Merged
merged 2 commits into from
Aug 16, 2021

Conversation

czlucius
Copy link
Contributor

@czlucius czlucius commented Jul 23, 2021

Pull Request checklist

  • Quality: This PR builds and passes detekt/ktlint checks (A pre-push hook is recommended)
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry or does not need one
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features

After merge

  • Milestone: Make sure issues closed by this pull request are added to the milestone of the version currently in development.
  • Breaking Changes: If this is a breaking change, please push a draft PR on Reference Browser to address the breaking issues.

@czlucius czlucius changed the title For issue #9830: Do not request/use WRITE_EXTERNAL_STORAGE on Android 11 and above For #9830: Do not request/use WRITE_EXTERNAL_STORAGE on Android 11 and above Jul 23, 2021
@czlucius
Copy link
Contributor Author

Here is the issue for this PR: #9830

@Amejia481 Amejia481 added the 🕵️‍♀️ needs review PRs that need to be reviewed label Jul 23, 2021
@Amejia481 Amejia481 closed this Jul 23, 2021
@Amejia481 Amejia481 reopened this Jul 23, 2021
@Amejia481 Amejia481 closed this Aug 9, 2021
@Amejia481 Amejia481 reopened this Aug 9, 2021
@Amejia481
Copy link
Contributor

Tests were not running because of this issue #10776 as d2aa609 landed they should run now :)

@Amejia481 Amejia481 force-pushed the fix-issue-9830 branch 2 times, most recently from eede703 to 09fbc5e Compare August 9, 2021 22:17
@Amejia481
Copy link
Contributor

I updated the tests a bit as we can do it as normal JVM tests, I also waiting for #10778 to be addressed as we are not able run tests for this PR until is fixed.

@Amejia481 Amejia481 closed this Aug 10, 2021
@Amejia481 Amejia481 reopened this Aug 10, 2021
@Amejia481 Amejia481 closed this Aug 11, 2021
@Amejia481 Amejia481 reopened this Aug 11, 2021
@mergify
Copy link
Contributor

mergify bot commented Aug 12, 2021

This pull request has conflicts when rebasing. Could you fix it @czlucius? 🙏

@czlucius
Copy link
Contributor Author

czlucius commented Aug 12, 2021

I updated the tests a bit as we can do it as normal JVM tests, I also waiting for #10778 to be addressed as we are not able run tests for this PR until is fixed.

It seems like the tests are working already.

@Amejia481
Copy link
Contributor

Not really :(,
The release engineering team has closed multiple issues but still they are not running. The source of the issue is that your fork repo is renamed mozilla-android-components instead of the default name android-components, I'm not sure if it will be easier to just rename your fork repo and open a new PR. What do you think?

@Amejia481
Copy link
Contributor

Now tests are running 🙌🏽

@Amejia481
Copy link
Contributor

Amejia481 commented Aug 12, 2021

Now we just need to address, this import lint



task 2021-08-12T17:28:14.050Z] > Task :ktlint
[task 2021-08-12T17:28:14.050Z] WARNING: An illegal reflective access operation has occurred
[task 2021-08-12T17:28:14.050Z] WARNING: Illegal reflective access by org.jetbrains.kotlin.com.intellij.util.ReflectionUtil (file:/builds/worker/fetches/android-gradle-dependencies/central/org/jetbrains/kotlin/kotlin-compiler-embeddable/1.4.31/kotlin-compiler-embeddable-1.4.31.jar) to method java.util.ResourceBundle.setParent(java.util.ResourceBundle)
[task 2021-08-12T17:28:14.050Z] WARNING: Please consider reporting this to the maintainers of org.jetbrains.kotlin.com.intellij.util.ReflectionUtil
[task 2021-08-12T17:28:14.050Z] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
[task 2021-08-12T17:28:14.050Z] WARNING: All illegal access operations will be denied in a future release
[task 2021-08-12T17:28:15.947Z] /builds/worker/checkouts/src/components/feature/downloads/src/test/java/mozilla/components/feature/downloads/manager/AndroidDownloadManagerTest.kt:7:1: Imports must be ordered in lexicographic order without any empty lines in-between with "java", "javax", "kotlin" and aliases in the end
[task 2021-08-12T17:28:15.947Z] /builds/worker/checkouts/src/components/feature/downloads/src/test/java/mozilla/components/feature/downloads/manager/FetchDownloadManagerTest.kt:7:1: Imports must be ordered in lexicographic order without any empty lines in-between with "java", "javax", "kotlin" and aliases in the end
[task 2021-08-12T17:28:16.251Z] /builds/worker/checkouts/src/components/feature/downloads/src/main/java/mozilla/components/feature/downloads/manager/AndroidDownloadManager.kt:7:1: Imports must be ordered in lexicographic order without any empty lines in-between with "java", "javax", "kotlin" and aliases in the end


…ownloading files on devices with Android 10 and above
@Amejia481
Copy link
Contributor

As scoped storage is available in Android 10, we don't need to require it on Android 10 and above

@Amejia481
Copy link
Contributor

I did some manual testing and everything looks good 👍🏽 .
I'll wait until Monday to land this patch, as we avoid landing features over the weekend.

@czlucius
Copy link
Contributor Author

Not really :(,
The release engineering team has closed multiple issues but still they are not running. The source of the issue is that your fork repo is renamed mozilla-android-components instead of the default name android-components, I'm not sure if it will be easier to just rename your fork repo and open a new PR. What do you think?

I can rename it back if necessary

@czlucius
Copy link
Contributor Author

I did some manual testing and everything looks good 👍🏽 .
I'll wait until Monday to land this patch, as we avoid landing features over the weekend.

Thanks

@czlucius
Copy link
Contributor Author

Do the list fixes to the code still need to be made?

@Amejia481 Amejia481 self-requested a review August 16, 2021 13:16
@Amejia481
Copy link
Contributor

Do the list fixes to the code still need to be made?

Thanks for asking, they are already addressed. The patch is on is way to be merged :)

@Amejia481 Amejia481 added 🛬 needs landing PRs that are ready to land and removed 🕵️‍♀️ needs review PRs that need to be reviewed labels Aug 16, 2021
@Amejia481
Copy link
Contributor

Amejia481 commented Aug 16, 2021

Thanks @czlucius for all your effort 🥇 !

@czlucius
Copy link
Contributor Author

Do the list fixes to the code still need to be made?

Sorry, I made a typo. I meant "lint" fixes

@Amejia481
Copy link
Contributor

Do the list fixes to the code still need to be made?

Sorry, I made a typo. I meant "lint" fixes

No worries, they are also addressed :)

@mergify mergify bot merged commit 2639ed8 into mozilla-mobile:main Aug 16, 2021
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
🛬 needs landing PRs that are ready to land
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants