Skip to content
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

Fix #5195: Fix RestrictedApi Errors #5348

Merged
merged 31 commits into from
Apr 2, 2024
Merged

Conversation

XichengSpencer
Copy link
Collaborator

Explanation

Fixes #5195 In the Android/Lint errors, all I can see are just NewApi Errors, which related methods are only available on API 26 and our current min API is 19.
Correct me if I am wrong, as discussed with Ben in a meeting, most errors test-related file can be fixed by adding require api annotation, and for all the changed files I think they are test related so I added annotation. I did some investigation java.util.Time replacement method and it requires to install third-party dependency, which I think adds too much complexity so I proceed with the annotation way. And for the color matcher one, I cannot find the replacement method.

Essential Checklist

  • [z] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
  • Any changes to scripts/assets files have their rationale included in the PR explanation.
  • The PR follows the style guide.
  • The PR does not contain any unnecessary code changes from Android Studio (reference).
  • The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
  • The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

  • Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
  • For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
  • Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
  • For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included
  • Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

Screenshot 2024-02-21 092439

XichengSpencer and others added 27 commits July 4, 2023 01:01
…tchIsOn() as discussed

, fix enable download access logic
,improve testAddProfileActivity_configChange_inputShortPin_create_pinLengthError() but still flaky
…ate function that served for MathExpressionParserViewModel.kt
There is no good replacement method for them in lower API level
Copy link

oppiabot bot commented Mar 4, 2024

Hi @XichengSpencer, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

@oppiabot oppiabot bot added the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 4, 2024
@oppiabot oppiabot bot removed the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 4, 2024
Copy link

oppiabot bot commented Mar 11, 2024

Hi @XichengSpencer, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

@oppiabot oppiabot bot added the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 11, 2024
Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @XichengSpencer! Please revert the unneeded changes an re-assign.

@oppiabot oppiabot bot removed the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 15, 2024
Copy link

oppiabot bot commented Mar 22, 2024

Hi @XichengSpencer, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

@oppiabot oppiabot bot added the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 22, 2024
@oppiabot oppiabot bot removed the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Mar 26, 2024
@adhiamboperes
Copy link
Collaborator

@XichengSpencer, please reassign if this is ready for a review.

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @XichengSpencer! This LGTM.

@adhiamboperes adhiamboperes merged commit f0e9ac9 into oppia:develop Apr 2, 2024
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

InvalidPackage + NewApi + FragmentLiveDataObserve + RestrictedApi
2 participants