Update deprecated Parcel functions#18068
Update deprecated Parcel functions#18068irfano merged 10 commits intofeature/update-compile-sdk-33from
Conversation
Generated by 🚫 dangerJS |
|
|||||||||||
| 💡 Scan this QR code with your Android phone to download and install the APK directly on it. | ||
| App | WordPress | |
| Build Flavor | Jalapeno | |
| Build Type | Debug | |
| Commit | b5bc515 | |
|
|||||||||||
| 💡 Scan this QR code with your Android phone to download and install the APK directly on it. | ||
| App | Jetpack | |
| Build Flavor | Jalapeno | |
| Build Type | Debug | |
| Commit | b5bc515 | |
ParaskP7
left a comment
There was a problem hiding this comment.
👋 @irfano !
I have reviewed and tested this PR as per the instructions, everything works as expected, good job! 🌟 🌟 🌟
FYI: In addition to the basic smoke test, I did some target testing, see below:
MediaScreen: Because of theMediaItem.ktchange.StatsScreen: Because of theSeelctedDateProvider.ktchange.NotificationsScreen & Functionality: Because of theAndroidManifest.xmlchange.
I can verify that everything works as expected! 🚀
Added
android.permission.POST_NOTIFICATIONSto fix the build error.
Question (❓): How did the build failed, I tried removing this permission and running assembleJetpackWasabiDebug in order to notice this build error but couldn't identify one (nor a warning). 🤔
Can you guide me here please? 🙏
...but notifications still works on Android 13 and lower versions.
This is true, I tested this by creating a new post and then seeing the notification showing right after, that is, even though I clicked the Don't Allow button when the Notification Permission dialog appeared after a clean install of the app.
|
FYI: The only thing that doesn't make me feel comfortable with this change is the fact that the 1.9.0 transitively updates Kotlin from PS: I was hoping to avoid such a transitive update and do such an update via #17563 . But, I guess we are now reaching a deadlock where #17563 needs #17790 and #17790 can't be completed with the the 1.9.0 update. 🤷 Or maybe, we could skip the 1.9.0 update in this PR, just to be on the safe side and add create our own compat extension functions, just like you did with #18061. 🤔 Wdyt @irfano ? |
Thank you for the additional testing, @ParaskP7. ❤️
It was showing a warning when running
I reverted all changes and created new functions in |
…-for-android13 # Conflicts: # WordPress/src/main/java/org/wordpress/android/ui/stats/refresh/lists/sections/granular/SelectedDateProvider.kt # WordPress/src/main/java/org/wordpress/android/util/extensions/CompatExtensions.kt
You saw the notification on the Notifications tab in the app, right? |
|
👋 @irfano and thank you for the update! ❤️ 🙇 🚀
I see, I see, so it was a warning then not an error, it just this warnings was failing the build due to Btw, thanks for reverting this change, I agree with that too, as it might be better to add this commit when we re-enabled
This is great, thanks for doing that, I agree, staying on the safe side might be wise atm! 💯 FYI: I went on another round of reviewing and testing, everything looks LGTM and works as expected! 🌟 🌟 🌟 It is a ✅ from my side, let's merge! 🚀
Done! 🎯 FYI: I added an UPDATE section on this comment of mine. |
I actually saw the notification alerts being displayed even on the device, not only on the That is with me clicking Can you give me an example of a specific notification that during your testing, when you click |
I have tested the case and here are the instructions:
After tapping the "Don't allow" button, the notification permission should be off in the app settings. |
|
👋 @irfano !
Ah, you are right, it was my bad, I am having all 3 variations of the Jetpack app on my testing phone, production ( I tested it again just now, just to be on the safe side, with both, clicking Thank you for making me realize this silly testing mistake of mine! 🙇 😅 💤 |
It's good to test all cases. 😄 |




This PR is part of a parent PR to update compileSdk to 33.
androidx.corewas updated to1.9.0to be able to useParcelCompat.readParcelableandParcelCompat.readListfunctions.To test:
Being able to build and basic smoke test should be enough.
Regression Notes
Potential unintended areas of impact
Notifications might be affected.
What I did to test those areas of impact (or what existing automated tests I relied on)
I tested notifications manually on devices with Android 13 and lower version.
What automated tests I added (or what prevented me from doing so)
N/A
PR submission checklist:
RELEASE-NOTES.txtif necessary.