feat(deps): bump androidxFragment from 1.5.7 to 1.6.2

[dependabot[bot]]

Bumps androidxFragment from 1.5.7 to 1.6.2. Updates androidx.fragment:fragment-ktx from 1.5.7 to 1.6.2

Updates androidx.fragment:fragment-testing from 1.5.7 to 1.6.2

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[JuancaG05]

@dependabot rebase

[dependabot[bot]]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[Aitorbp]

We are having problems with Bitrise because it does not pass the tests due to flakies. Therefore we have made a list of the flakies that are being played to ignore them from Bitrise. We have looked at the last 10 worksflows that have failed in bitrise and we have put the tests that have been played the most in order from most to least. In any case all these tests except badge_available_offline_in_image_is_not_viewed_when_file_does_not_change_state will be ignored because they are already known from previous worksflows:

privacyPolicyOpensPrivacyPolicyActivity (7) test_sort_by_name_click (5) test_sort_by_date_click (2) verifyTests (2) initialViewStatus_brandedOptions_serverInfoInSetup_connectionFails (2) badge_available_offline_in_image_is_not_viewed_when_file_does_not_change_state (1) login_isLoading (1)

[jesmrec]

In any case all these tests except badge_available_offline_in_image_is_not_viewed_when_file_does_not_change_state will be ignored because they are already known from previous worksflows:

that one failed 1 out of 10, same as login_isLoading. Why is this one ignored with the same flaky rate as the one you mentioned?

Just as my opinion, i'd ignore only the two on the top.

[Aitorbp]

In any case all these tests except badge_available_offline_in_image_is_not_viewed_when_file_does_not_change_state will be ignored because they are already known from previous worksflows:

that one failed 1 out of 10, same as login_isLoading. Why is this one ignored with the same flaky rate as the one you mentioned?

Just as my opinion, i'd ignore only the two on the top.

Because that one in particular I've never seen it in other past worksflows (maybe appear too more often). For example, the login_isLoading one I've seen many times, although in these last 10 workflows it only appears once.

[Aitorbp]

This bump is not going to be merged because the bitrise UI Tests are giving a lot of problems.