-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
deprecation: compileSdk 33 issues #12364
Comments
@david-allison I would like to work on Activity.onBackPressed deprecation. |
@priyanshuborole great - unless someone has said they are working on something - no need to ask permission, just state (with authority! go for it!) that you are working on such and such. Good luck, and thanks |
@david-allison I was working on Intent.getParcelableExtra but when I am trying to update the method it gives an error and not recognizing the API level 33 intent removing the @Supress also throws an error while building up the application. |
Look up the method: https://developer.android.com/reference/android/content/Intent#getParcelableExtra(java.lang.String,%20java.lang.Class%3CT%3E) is recommended instead.
|
I found https://stackoverflow.com/questions/73019160/android-getparcelableextra-deprecated/73311814#73311814 which explains the usability of getPracelableExtra in API >=33 |
@david-allison Working on Parcel.readSparseArray |
Hey, I was working on Bundle.getParcelable. I'm not sure which class should be mentioned here Also if I add a class, it says Call requires API level 33, should I surround it with |
It's a Uri: Line 85 in 3f464f6
See our compat infrastructure for how to handle this. There's already a thread on Discord where I've walked someone through this |
#12410 adds this infra, and should be a good starting point |
Hey! are you still working on it? |
Yes I am working on it, give me 1-2 days if not possible I will update you |
Hey! Are you working on it? coz if not then I would like to overtake it. |
I'm working on Parcel.readSparseArray and there is only one place it occurs, which is com/ichi2/anki/FieldEditLine.kt:249 |
Is anyone working on PackageManager depreciated interfaces? |
I don't think anyone is |
I'm not able to figure out a few things. So sure go ahead. I'll just watch and learn 😂 |
Sure, Thanks! |
yes, you can start working on it. |
Could you please review the last PR so that I can move on to the other one? Like whenever you are good to go. Thanks! |
@criticalAY if you examine the volume of work in flight at any time (https://github.com/ankidroid/Anki-Android/pulse) you'll see you have to have some patience, especially since we are essentially all volunteers. Sometimes things are very very fast, sometimes they sit, it is not predictable. However, if you feel you have that PR under control, you can take on another one - that's fine. I would only caution against having too many PRs in flight at once, but that would be like 5-6 - at that point it is usually a sign that things are not really being answered satisfactorily for some reason or they would be getting merged. In this case I think we're close, go ahead on something new if you like, while reviewers catch up. Cheers! |
Yes, I do understand but if I make another PR that would make a conflict I guess. One thing that I am learning from open source contributions is how to be patient and I would love to wait as I am enjoying working with you all <3 |
I believe the various SDK33 deprecations will not conflict with each other, each of them should be in different chunks of text which git should ideally be able to handle just fine on merge. Even if not, handling conflicts via git rebase / fixing conflicts / force push to your branch is one of the most powerful things you can learn as a modern software developer (where "modern" is defined as "we are all using git now"). Once you've got git rebase-merge/de-conflict/force-push down, there is almost nothing out of reach with regards to managing a source code repository and that's a powerful professional skill. So don't fear conflicts, in my opinion |
API 33 serializable bundle deprecation update #12463 for Bundle.getSerializable |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Additional info on
|
Hey! I'm new here but would like to contribute. Can I try to work on onBackPressed() ? |
@niryline that sounds great! Good luck |
Hey @mikehardy, I migrated the deprecated code, But I'm getting some errors when I'm going to push the code and make a PR. Here is the error code FAILURE: Build failed with an exception.
Error occurred during initialization of VM
|
@MudssirAhmed we use JDK11 normally for development. I would make sure that's the JDK in use. Looks like you attempted to use 8. |
@mikehardy thanks for the comment, I created a PR for onBackPress depreciation handle. PR |
Oh @MudssirAhmed I was working on this... I guess I was too slow. |
Deprecated in API 33 https://developer.android.com/reference/android/content/pm/PackageManager#getPackageInfo(java.lang.String,%20int) `PackageManagerCompat` was created because: * PackageInfoFlags is introduced in API 33 and is the API replacement * Unusable before API 33 * parameters: `flags: Integer` is replaced with `flags: PackageInfoFlags` * `PackageInfoFlags` is given `PackageInfoFlagsBits` which handles invalid values * PackageInfoFlagsBits depends on constants which are not defined in API 21 Closes ankidroid#12548 (superseded) Related ankidroid#12364
Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
@david-allison there's a pending PR for the last remaining issue - should we ask them to update it? |
onBackPressed is the only remaining one, and we're going to track it in #14558 |
Hi there! Thanks for picking up a deprecation task - we think these are good first issues because:
1- typically you can just search the codebase for a relevant string and find where the work is quickly
2- typically there is documentation upstream in the Google Android Developer docs that explain how the old API worked, why it is deprecated, and then there is documentation for the new API
3- the functionality is already working, switching to a new implementation has a clear standard to meet, it should be obvious the change was good (because the feature was working, and should just still be working
These are the collection of interfaces deprecated as we switched compileSdkVersion from 32 to 33:
The task is to:
@Suppress("deprecation")
near it signaling that you found the spot!./gradlew jacocoTestReport ktlintCheck
passes on your work locally, and that the feature still worksAsk if you have any questions!
Originally posted by @david-allison in #12359 (comment)
The text was updated successfully, but these errors were encountered: