Closed AdamGrzybkowski closed 2 weeks ago
The following changes in project dependencies were detected (configuration wordpressVanillaReleaseRuntimeClasspath
):
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21311-1ee70bb | |
Commit | 1ee70bb7a8dda3956a576ad3e8a5bfd37d6b8f48 | |
Direct Download | wordpress-prototype-build-pr21311-1ee70bb.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21311-1ee70bb | |
Commit | 1ee70bb7a8dda3956a576ad3e8a5bfd37d6b8f48 | |
Direct Download | jetpack-prototype-build-pr21311-1ee70bb.apk |
Attention: Patch coverage is 0%
with 6 lines
in your changes missing coverage. Please review.
Project coverage is 39.50%. Comparing base (
ae41f3f
) to head (1ee70bb
).
Files with missing lines | Patch % | Lines |
---|---|---|
...java/org/wordpress/android/util/WPAvatarUtils.java | 0.00% | 3 Missing :warning: |
...a/org/wordpress/android/login/util/AvatarHelper.kt | 0.00% | 3 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@AdamGrzybkowski I tested the flow with the Me fragment and it all worked as expected, but I can't seem to get SignupEpilogueFragment
to appear regardless of the build variant. What do I need to do to get that to show?
@AdamGrzybkowski I tested the flow with the Me fragment and it all worked as expected, but I can't seem to get SignupEpilogueFragment to appear regardless of the build variant. What do I need to do to get that to show?
@nbradbury I was actually hoping you would help me with this screen as I also struggle with it.
I mentioned it in the description:
Note: I have an issue with one screen during sign-up flow SignupEpilogueFragment. When I run wasabi flavor this screen automatically finishes and moves to the next one. Testing the jalapeno build seems to work fine.
Here's how it looks for me:
https://github.com/user-attachments/assets/63294887-a883-4e5c-b160-f6005d4ce2ce
There's this Dialog with Updating account
copy that's triggered by something and then the screen is closed.
@hamorillo Given that the Signup screen works for you, would you mind testing this as well?
🤔 I wonder why the behavior is different for me:
https://github.com/user-attachments/assets/d9aed627-ae72-4ef1-808a-a351e956c26e
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
This PR bumps the Gravatar SDK to the latest 2.0.0 version.
On the outside, we made some updates to our public API but under the hood, the avatar upload endpoint was also updated to a v3 version.
Note: I have an issue with one screen during sign-up flow
SignupEpilogueFragment
. When I runwasabi
flavor this screen automatically finishes and moves to the next one. Testing thejalapeno
build seems to work fine. I've also asked @hamorillo to test this and it worked okay for him on both variants. Any idea what's happening? I can see the thewasabi
build is getting someAccountAction.PUSH_SETTINGS
updates.To Test:
Avatar change flow from the
MeFragment
andSignupEpilogueFragment
.SignupEpilogueFragment
screen.Regression Notes
Potential unintended areas of impact
PR Submission Checklist:
~- [ ] I have completed the Regression Notes.~
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):
~- [ ] WordPress.com sites and self-hosted Jetpack sites.~ ~- [ ] Portrait and landscape orientations.~ ~- [ ] Light and dark modes.~ ~- [ ] Fonts: Larger, smaller and bold text.~ ~- [ ] High contrast.~ ~- [ ] Talkback.~ ~- [ ] Languages with large words or with letters/accents not frequently used in English.~ ~- [ ] Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)~ ~- [ ] Large and small screen sizes. (Tablet and smaller phones)~ ~- [ ] Multi-tasking: Split screen and Pop-up view. (Android 10 or higher)~
The update shouldn't affect the UI so the above scenarios are not valid.