status-mobile
status-mobile copied to clipboard
fixed overlapping last message by the composer when there is a pinned…
fixes https://github.com/status-im/status-mobile/issues/20513
Summary
This pr adds margin-bottom when the user is not allowed to post a message in a community channel because they are not a member. The margin-bottom is the height of the permission bottom sheet that is shown when the user is no longer a community member
A note to @status-im/mobile-qa, this pr also fixes a bug explained in this comment https://github.com/status-im/status-mobile/pull/20606#issuecomment-2245086356. Its a small simple fix I bundled up in this pr
Before and after screenshots comparison
status: ready
Jenkins Builds
Click to see older builds (76)
| :grey_question: | Commit | :hash: | Finished (UTC) | Duration | Platform | Result |
|---|---|---|---|---|---|---|
| :x: | 79f3b31542669e3d492b891b3d1236bf68e16377 | #1 | 2024-07-01 11:04:01 | ~5 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 79f3b31542669e3d492b891b3d1236bf68e16377 | #1 | 2024-07-01 11:07:32 | ~8 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 79f3b31542669e3d492b891b3d1236bf68e16377 | #1 | 2024-07-01 11:10:07 | ~11 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 79f3b31542669e3d492b891b3d1236bf68e16377 | #1 | 2024-07-01 11:10:57 | ~12 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | e37afa0a559af3e44195d35c5872dc9ec28f1333 | #2 | 2024-07-01 11:51:02 | ~7 min | tests |
:page_facing_up:log |
| :x: | e37afa0a559af3e44195d35c5872dc9ec28f1333 | #2 | 2024-07-01 11:51:43 | ~8 min | ios |
:page_facing_up:log |
| :heavy_check_mark: | e37afa0a559af3e44195d35c5872dc9ec28f1333 | #2 | 2024-07-01 11:53:43 | ~10 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | e37afa0a559af3e44195d35c5872dc9ec28f1333 | #2 | 2024-07-01 11:55:13 | ~11 min | android-e2e |
:robot:apk :calling: |
| :x: | ea97a4f6 | #3 | 2024-07-16 10:38:43 | ~2 min | ios |
:page_facing_up:log |
| :heavy_check_mark: | ea97a4f6 | #3 | 2024-07-16 10:41:00 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | ea97a4f6 | #3 | 2024-07-16 10:42:15 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | ea97a4f6 | #3 | 2024-07-16 10:43:59 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 605355a1 | #4 | 2024-07-18 10:43:01 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 605355a1 | #4 | 2024-07-18 10:44:32 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 605355a1 | #4 | 2024-07-18 10:46:17 | ~8 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 605355a1 | #4 | 2024-07-18 10:47:47 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | d5e25971 | #5 | 2024-07-18 22:14:49 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | d5e25971 | #5 | 2024-07-18 22:16:55 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | d5e25971 | #5 | 2024-07-18 22:17:51 | ~7 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | d5e25971 | #5 | 2024-07-18 22:19:30 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | d9feecc0 | #7 | 2024-07-18 23:01:39 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | d9feecc0 | #7 | 2024-07-18 23:04:53 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | d9feecc0 | #7 | 2024-07-18 23:05:07 | ~7 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | d9feecc0 | #7 | 2024-07-18 23:06:44 | ~9 min | ios |
:iphone:ipa :calling: |
| :x: | d5258da6 | #8 | 2024-07-19 15:19:41 | ~3 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | d5258da6 | #8 | 2024-07-19 15:23:00 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | d5258da6 | #8 | 2024-07-19 15:24:35 | ~8 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | d5258da6 | #8 | 2024-07-19 15:25:44 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | d6096ec6 | #9 | 2024-07-19 16:16:57 | ~5 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | d6096ec6 | #9 | 2024-07-19 16:17:49 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | d6096ec6 | #9 | 2024-07-19 16:19:34 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | d6096ec6 | #9 | 2024-07-19 16:20:49 | ~9 min | ios |
:iphone:ipa :calling: |
| :x: | ca53173d | #10 | 2024-07-23 22:56:20 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | ca53173d | #10 | 2024-07-23 22:58:18 | ~6 min | android-e2e |
:robot:apk :calling: |
| :x: | 42c72d16 | #12 | 2024-07-23 23:04:25 | ~3 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 42c72d16 | #12 | 2024-07-23 23:07:58 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 42c72d16 | #12 | 2024-07-23 23:08:49 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 42c72d16 | #12 | 2024-07-23 23:10:04 | ~8 min | ios |
:iphone:ipa :calling: |
| :x: | c920bac7 | #13 | 2024-07-24 11:59:46 | ~2 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | c920bac7 | #13 | 2024-07-24 12:03:27 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | c920bac7 | #13 | 2024-07-24 12:03:38 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | c920bac7 | #13 | 2024-07-24 12:07:06 | ~10 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 3b3d9c91 | #14 | 2024-07-24 12:46:56 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 3b3d9c91 | #14 | 2024-07-24 12:49:08 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | b753ce9f | #15 | 2024-07-24 12:53:35 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | b753ce9f | #15 | 2024-07-24 12:55:45 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | b753ce9f | #15 | 2024-07-24 12:55:58 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | b753ce9f | #15 | 2024-07-24 12:58:28 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | d46a9bb8 | #16 | 2024-07-24 19:27:56 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | d46a9bb8 | #16 | 2024-07-24 19:29:45 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | d46a9bb8 | #16 | 2024-07-24 19:30:14 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | d46a9bb8 | #16 | 2024-07-24 19:32:45 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 34555e4c | #17 | 2024-07-26 09:55:17 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 34555e4c | #17 | 2024-07-26 09:56:57 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 34555e4c | #17 | 2024-07-26 09:59:09 | ~8 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 34555e4c | #17 | 2024-07-26 10:01:41 | ~11 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 79fcb12d | #18 | 2024-07-26 18:29:59 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 79fcb12d | #18 | 2024-07-26 18:32:56 | ~7 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 79fcb12d | #18 | 2024-07-26 18:32:58 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 79fcb12d | #18 | 2024-07-26 18:34:28 | ~8 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 3261ac05 | #19 | 2024-07-26 19:19:29 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 3261ac05 | #19 | 2024-07-26 19:21:51 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 3261ac05 | #19 | 2024-07-26 19:22:47 | ~7 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 3261ac05 | #19 | 2024-07-26 19:24:06 | ~8 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | ced05069 | #20 | 2024-07-29 08:36:20 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | ced05069 | #20 | 2024-07-29 08:38:28 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | ced05069 | #20 | 2024-07-29 08:39:07 | ~7 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | ced05069 | #20 | 2024-07-29 08:40:38 | ~8 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | df32b171 | #21 | 2024-08-19 09:08:05 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | df32b171 | #21 | 2024-08-19 09:10:01 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | df32b171 | #21 | 2024-08-19 09:10:56 | ~7 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | df32b171 | #21 | 2024-08-19 09:12:56 | ~9 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 92c38762 | #22 | 2024-09-05 08:24:25 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 92c38762 | #22 | 2024-09-05 08:25:55 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 92c38762 | #22 | 2024-09-05 08:27:36 | ~8 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 92c38762 | #22 | 2024-09-05 08:33:01 | ~13 min | ios |
:iphone:ipa :calling: |
| :grey_question: | Commit | :hash: | Finished (UTC) | Duration | Platform | Result |
|---|---|---|---|---|---|---|
| :heavy_check_mark: | 9f9a5aff | #23 | 2024-09-09 22:52:40 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 9f9a5aff | #23 | 2024-09-09 22:54:39 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 9f9a5aff | #23 | 2024-09-09 22:55:16 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 9f9a5aff | #23 | 2024-09-09 22:59:02 | ~10 min | ios |
:iphone:ipa :calling: |
| :heavy_check_mark: | 6c4900ed | #24 | 2024-09-09 23:06:48 | ~4 min | tests |
:page_facing_up:log |
| :heavy_check_mark: | 6c4900ed | #24 | 2024-09-09 23:08:46 | ~6 min | android-e2e |
:robot:apk :calling: |
| :heavy_check_mark: | 6c4900ed | #24 | 2024-09-09 23:09:13 | ~6 min | android |
:robot:apk :calling: |
| :heavy_check_mark: | 6c4900ed | #24 | 2024-09-09 23:12:33 | ~10 min | ios |
:iphone:ipa :calling: |
@ilmotta I have made some updates on this, so instead of checking on pinned messages, we instead check on if the user can post to community and if its a community chat.
https://github.com/user-attachments/assets/5d985618-6ba2-4f29-843d-3f65d403cca5
@ilmotta something else I am noticing, if there is a pinned message and the message is unpinned, the app is killed and restarted and navigate to the current chat the message is still pinned.
this behavior is inconsistent maybe its because i was using an old account or something. I am not reproducing it any more
I have made some updates on this, so instead of checking on pinned messages, we instead check on if the user can post to community and if its a community chat.
Thanks @jo-mut. I'll check the PR again later today.
something else I am noticing, if there is a pinned message and the message is unpinned, the app is killed and restarted and navigate to the current chat the message is still pinned.
There's a delay for messages to propagate in the network. Maybe because of that, when you unpin and immediately close the app, when reopening, the deletion may not have fully propagated yet?
Or do you mean you reopen and the message is never unpinned?
I am also closing the following issue https://github.com/status-im/status-mobile/issues/20779, I think its because was using an old account.
I have made some updates on this, so instead of checking on pinned messages, we instead check on if the user can post to community and if its a community chat.
Thanks @jo-mut. I'll check the PR again later today.
something else I am noticing, if there is a pinned message and the message is unpinned, the app is killed and restarted and navigate to the current chat the message is still pinned.
There's a delay for messages to propagate in the network. Maybe because of that, when you unpin and immediately close the app, when reopening, the deletion may not have fully propagated yet?
Or do you mean you reopen and the message is never unpinned?
yeah, when I pin and unpin a message and restart the app, the message is still pinned but not its not reproducible, so maybe its because of message reliablity issues or could because i was using an old account in testing
@ilmotta this is what I meant before, when there is a pinned message and its unpinned, on-reopening the community channel the message is still pinned and when the message is not pinned and I pin the message on-reopening the channel the message in not pinned. The behaviour is the opposite when the channel is closed and reopened. It could be message reliability
https://github.com/user-attachments/assets/4c890944-648f-49d8-ae98-d67b11f279cb
https://github.com/user-attachments/assets/8983523f-0e9f-4e68-b97e-c96082e637e3
The referenced issue does not seem to happen because of a pinned message. It still happens in the case where there is not a pinned message and the user is not a community member and therefore cannot post.
As tested on develop user is member v user has left community
this is what I meant before, when there is a pinned message and its unpinned, on-reopening the community channel the message is still pinned and when the message is not pinned and I pin the message on-reopening the channel the message in not pinned. The behaviour is the opposite when the channel is closed and reopened. It could be message reliability
@jo-mut, in this example, I think the user can't unpin a message if they are not a member, that's why you see the message is still unpinned. If they could, anybody would be able to alter the list of pinned messages.
The actual bug is that the user shouldn't be able to pin/unpin messages if they are not a member. This we should fix if possible.
@ilmotta got you, I think that can be handled in a separate issues, it falls out of scope for this issue. As for this pr, the overlapping of the last-message is fixed
The actual bug is that the user shouldn't be able to pin/unpin messages if they are not a member. This we should fix if possible.
shall I create an issue or have you already done so? I think we can do this one in this release
this is what I meant before, when there is a pinned message and its unpinned, on-reopening the community channel the message is still pinned and when the message is not pinned and I pin the message on-reopening the channel the message in not pinned. The behaviour is the opposite when the channel is closed and reopened. It could be message reliability
@jo-mut, in this example, I think the user can't unpin a message if they are not a member, that's why you see the message is still unpinned. If they could, anybody would be able to alter the list of pinned messages.
The actual bug is that the user shouldn't be able to pin/unpin messages if they are not a member. This we should fix if possible.
@ilmotta I added a commit to prevent a user who is not a member from pinning and un-pinning channel messages, I thinks its a small issue that can be bundled up in this pr. Once approved I will let the QA know so they can take this into account when testing.
Thank you @jo-mut, for sure the fix could have been implemented in a separate PR, but thanks for helping with that already. And sorry today I was on many calls and couldn't check the PR again.
@ilmotta I made last minute changes to check if user is a community member instead of using able-to-send-message?
57% of end-end tests have passed
Total executed tests: 7
Failed tests: 2
Expected to fail tests: 1
Passed tests: 4
IDs of failed tests: 702745,727229
IDs of expected to fail tests: 727232
Failed tests (2)
Click to expand
Class TestWalletMultipleDevice:
| 1. test_wallet_send_eth, id: 727229 |
|
Class TestOneToOneChatMultipleSharedDevicesNewUi:
| 1. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745 |
Device 1: Device 2: |
Expected to fail tests (1)
Click to expand
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_watch_only_account, id: 727232 |
[[Missing networks in account address, https://github.com/status-im/status-mobile/issues/20166]] Device 1: |
Passed tests (4)
Click to expand
Class TestWalletMultipleDevice:
| 1. test_wallet_send_asset_from_drawer, id: 727230 |
Class TestCommunityOneDeviceMerged:
| 1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133 |
| Device sessions Device 1: |
| 2. test_community_copy_and_paste_message_in_chat_input, id: 702742 |
| Device sessions Device 1: |
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_regular_account, id: 727231 |
| Device sessions Device 1: |
@ilmotta I made last minute changes to check if user is a community member instead of using
able-to-send-message?
Thanks @jo-mut. Let's also see the feedback from a QA about this point. I don't know the granularity at which pinning messages are controllable. Double-checking how the desktop app behaves is another sure way to verify how it should be or pinging a desktop dev. Being a community member may be correct, but might be too permissive too and still not the precise check we should do because the user is doing an operation at the channel level, not community level.
53% of end-end tests have passed
Total executed tests: 51
Failed tests: 23
Expected to fail tests: 1
Passed tests: 27
IDs of failed tests: 702845,702840,702894,703086,702947,702958,702775,702786,702844,704613,702841,702839,702809,702838,704615,702948,702859,703629,702957,702843,727229,702777,703194
IDs of expected to fail tests: 727232
Failed tests (23)
Click to expand
Class TestActivityMultipleDevicePR:
| 1. test_activity_center_reply_read_unread_delete_filter_swipe, id: 702947 |
Device 1: Device 2: |
Class TestWalletMultipleDevice:
| 1. test_wallet_send_eth, id: 727229 |
|
Class TestDeepLinksOneDevice:
| 1. test_links_deep_links, id: 702775 |
Device 1: |
| 2. test_links_open_universal_links_from_chat, id: 704613 |
Device 1: |
Class TestActivityMultipleDevicePRTwo:
| 1. test_activity_center_admin_notification_accept_swipe, id: 702958 |
|
| 2. test_activity_center_mentions, id: 702957 |
Device 1: Device 2: |
Class TestCommunityMultipleDeviceMerged:
| 1. test_community_emoji_send_copy_paste_reply, id: 702840 |
|
| 2. test_community_contact_block_unblock_offline, id: 702894 |
|
| 3. test_community_mark_all_messages_as_read, id: 703086 |
|
| 4. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844 |
|
| 5. test_community_unread_messages_badge, id: 702841 |
|
| 6. test_community_message_delete, id: 702839 |
|
| 7. test_community_message_send_check_timestamps_sender_username, id: 702838 |
Device 1: Device 2: |
| 8. test_community_edit_delete_message_when_offline, id: 704615 |
|
| 9. test_community_one_image_send_reply, id: 702859 |
|
| 10. test_community_message_edit, id: 702843 |
|
| 11. test_community_several_images_send_reply, id: 703194 |
|
Class TestCommunityMultipleDeviceMergedTwo:
| 1. test_community_leave, id: 702845 |
|
| 2. test_community_mentions_push_notification, id: 702786 |
Device 1: Device 2: |
| 3. test_community_markdown_support, id: 702809 |
|
| 4. test_community_hashtag_links_to_community_channels, id: 702948 |
|
| 5. test_community_join_when_node_owner_offline, id: 703629 |
|
Class TestActivityCenterContactRequestMultipleDevicePR:
| 1. test_add_contact_field_validation, id: 702777 |
Device 1: Device 2: |
Expected to fail tests (1)
Click to expand
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_watch_only_account, id: 727232 |
[[Missing networks in account address, https://github.com/status-im/status-mobile/issues/20166]] Device 1: |
Passed tests (27)
Click to expand
Class TestOneToOneChatMultipleSharedDevicesNewUi:
| 1. test_1_1_chat_edit_message, id: 702855 |
| Device sessions Device 1: Device 2: |
| 2. test_1_1_chat_message_reaction, id: 702730 |
| Device sessions Device 1: Device 2: |
| 3. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745 |
| Device sessions Device 1: Device 2: |
| 4. test_1_1_chat_pin_messages, id: 702731 |
| Device sessions Device 1: Device 2: |
| 5. test_1_1_chat_text_message_delete_push_disappear, id: 702733 |
| Device sessions Device 1: Device 2: |
| 6. test_1_1_chat_push_emoji, id: 702813 |
| Device sessions Device 1: Device 2: |
| 7. test_1_1_chat_emoji_send_reply_and_open_link, id: 702782 |
| Device sessions Device 1: Device 2: |
| 8. test_1_1_chat_send_image_save_and_share, id: 703391 |
| Device sessions Device 1: Device 2: |
Class TestWalletMultipleDevice:
| 1. test_wallet_send_asset_from_drawer, id: 727230 |
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
| 1. test_1_1_chat_mute_chat, id: 703496 |
| Device sessions Device 1: Device 2: |
| 2. test_1_1_chat_is_shown_message_sent_delivered_from_offline, id: 702783 |
| Device sessions Device 1: Device 2: |
| 3. test_1_1_chat_delete_via_long_press_relogin, id: 702784 |
| Device sessions Device 1: Device 2: |
Class TestCommunityOneDeviceMerged:
| 1. test_community_copy_and_paste_message_in_chat_input, id: 702742 |
| Device sessions Device 1: |
| 2. test_community_navigate_to_channel_when_relaunch, id: 702846 |
| Device sessions Device 1: |
| 3. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133 |
| Device sessions Device 1: |
| 4. test_community_undo_delete_message, id: 702869 |
| Device sessions Device 1: |
| 5. test_community_mute_community_and_channel, id: 703382 |
| Device sessions Device 1: |
| 6. test_community_discovery, id: 703503 |
| Device sessions Device 1: |
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_regular_account, id: 727231 |
| Device sessions Device 1: |
Class TestGroupChatMultipleDeviceMergedNewUI:
| 1. test_group_chat_reactions, id: 703202 |
| Device sessions Device 1: Device 2: Device 3: |
| 2. test_group_chat_join_send_text_messages_push, id: 702807 |
| Device sessions Device 1: Device 2: Device 3: |
| 3. test_group_chat_offline_pn, id: 702808 |
| Device sessions Device 1: Device 2: Device 3: |
| 4. test_group_chat_pin_messages, id: 702732 |
| Device sessions Device 1: Device 2: Device 3: |
| 5. test_group_chat_send_image_save_and_share, id: 703297 |
| Device sessions Device 1: Device 2: Device 3: |
| 6. test_group_chat_mute_chat, id: 703495 |
| Device sessions Device 1: Device 2: Device 3: |
Class TestActivityCenterContactRequestMultipleDevicePR:
| 1. test_activity_center_contact_request_accept_swipe_mark_all_as_read, id: 702851 |
| Device sessions Device 1: Device 2: |
| 2. test_activity_center_contact_request_decline, id: 702850 |
| Device sessions Device 1: Device 2: |
Hi @ilmotta !
This PR touches some areas needed to be retested. Sorry for the delay.
-
want to report that @jo-mut fix of overlapping is good and I see no issue on my iOS
-
pin logic that exist on mobile and desktop:
-
no one can NOT pin/un-pin if he is NOT a community member
-
no one can NOT pin/un-pin if he IS a member but NO such desktop setting is turned on during community creation on desktop:
- also desktop has such
permissionsthat could be added tochannels:
View
View and post
and it is the way for user to be a member but NOT to have ability to post (so NOT being able to send a message)
But this functionality should be retested as there are issues in token gated functionality and I can not clearly say will this View only member can pin/unpin in such case.
@ilmotta will leave this PR in Testing status until 2.31 if you do not mind as we are not planning to include it in 2.30
100% of end-end tests have passed
Total executed tests: 7
Failed tests: 0
Expected to fail tests: 0
Passed tests: 7
Passed tests (7)
Click to expand
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_regular_account, id: 727231 |
| Device sessions Device 1: |
Class TestCommunityOneDeviceMerged:
| 1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133 |
| Device sessions Device 1: |
| 2. test_community_copy_and_paste_message_in_chat_input, id: 702742 |
| Device sessions Device 1: |
Class TestCommunityMultipleDeviceMerged:
| 1. test_community_message_edit, id: 702843 |
| Device sessions Device 1: Device 2: |
Class TestOneToOneChatMultipleSharedDevicesNewUi:
| 1. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745 |
| Device sessions Device 1: Device 2: |
Class TestWalletMultipleDevice:
| 1. test_wallet_send_asset_from_drawer, id: 727230 |
| 2. test_wallet_send_eth, id: 727229 |
@ilmotta will leave this PR in Testing status until 2.31 if you do not mind as we are not planning to include it in 2.30
Agreed @mariia-skrypnyk. Better that way 👍🏼
also better to mind composer simlification, might be also affected https://github.com/status-im/status-mobile/pull/20125
So should we just close this PR for now?
@ilmotta @churik
So should we just close this PR for now?
It depends if the work in this PR is mostly done, if it is, we can just update/rebase and QA it. @mariia-skrypnyk You mentioned before I see no issue on my iOS, so if it works on Android we could merge the PR. The issues around token-gating functionality I think are outside the scope of this PR, which is supposed to be just UI polish.
I agree that in general pin logic is outside of scope of the PR; we can merge if initial bug is fixed and move pin logic issues to separate , cc @mariia-skrypnyk
86% of end-end tests have passed
Total executed tests: 7
Failed tests: 1
Expected to fail tests: 0
Passed tests: 6
IDs of failed tests: 727230
Failed tests (1)
Click to expand
Class TestWalletMultipleDevice:
| 1. test_wallet_send_asset_from_drawer, id: 727230 |
|
Passed tests (6)
Click to expand
Class TestCommunityMultipleDeviceMerged:
| 1. test_community_message_edit, id: 702843 |
| Device sessions Device 1: Device 2: |
Class TestCommunityOneDeviceMerged:
| 1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133 |
| Device sessions Device 1: |
| 2. test_community_copy_and_paste_message_in_chat_input, id: 702742 |
| Device sessions Device 1: |
Class TestWalletOneDevice:
| 1. test_wallet_add_remove_regular_account, id: 727231 |
| Device sessions Device 1: |
Class TestOneToOneChatMultipleSharedDevicesNewUi:
| 1. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745 |
| Device sessions Device 1: Device 2: |
Class TestWalletMultipleDevice:
| 1. test_wallet_send_eth, id: 727229 |
Hi @ilmotta @ulisesmac !
Rebased PR and retested on iOS and Android. Issue with overlapping is fixed and PR can be merged. Failed e2e is not related.