Skip to content
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

Add request address command #9741

Merged
merged 1 commit into from
Jan 10, 2020
Merged

Add request address command #9741

merged 1 commit into from
Jan 10, 2020

Conversation

cammellos
Copy link
Contributor

@cammellos cammellos commented Jan 2, 2020

This PR adds the request-address command as described in the specs.
The flow is:

  1. User A prepares a transaction to send to user B, requesting user B their address
  2. User B should see a message with the transaction details, and they can either accept or decline the request. If they accept they will select an account.
  3. User A will receive the response and send back a transaction, which will need to be signed
  4. User B will then validate the transaction, and only once validated it will be shown to the user.

Currently the validation is done on Ropsten for testing purposes, so make sure both accounts are using the ropsten network before testing.

Known issues:

  1. Select account sheet animates once the account is selected, after clicking on accept request address
  2. Token transfer have not been tested (It would be handy if someone could test those on ropsten)
  3. Declining a transaction does not hide the previous message

Likely there are other issues here and there, if testing, please let me know.

status: ready

@cammellos cammellos requested a review from a team as a code owner January 2, 2020 14:58
@ghost
Copy link

ghost commented Jan 2, 2020

Pull Request Checklist

  • Docs: Updated the documentation, if affected
  • Docs: Added or updated inline comments explaining intention of the code
  • Tests: Ensured that all new UI elements have been assigned accessibility IDs
  • Tests: Signaled need for E2E tests with label, if applicable
  • Tests: Briefly described what was tested and what platforms were used
  • UI: In case of UI changes, ensured that UI matches Figma
  • UI: In case of UI changes, requested review from a Core UI designer
  • UI: In case of UI changes, included screenshots of implementation

@status-im-auto
Copy link
Member

status-im-auto commented Jan 2, 2020

Jenkins Builds

Click to see older builds (64)
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ e8ccee7 #1 2020-01-02 15:11:39 ~12 min ios 📦ipa 📲
✔️ e8ccee7 #1 2020-01-02 15:16:25 ~17 min android-e2e 📦apk 📲
✔️ e8ccee7 #1 2020-01-02 15:17:57 ~19 min android 📦apk 📲
✔️ 60a4698 #2 2020-01-03 12:19:48 ~12 min ios 📦ipa 📲
✔️ 60a4698 #2 2020-01-03 12:24:36 ~17 min android-e2e 📦apk 📲
✔️ 60a4698 #2 2020-01-03 12:25:27 ~18 min android 📦apk 📲
✔️ 392c291 #3 2020-01-07 09:05:08 ~9 min ios 📦ipa 📲
✔️ 052f7c4 #4 2020-01-07 09:14:13 ~9 min ios 📦ipa 📲
✔️ 052f7c4 #4 2020-01-07 09:16:38 ~11 min android 📦apk 📲
✔️ 052f7c4 #4 2020-01-07 09:17:12 ~12 min android-e2e 📦apk 📲
✔️ 21a98c6 #5 2020-01-07 12:33:47 ~13 min ios 📦ipa 📲
✔️ 21a98c6 #5 2020-01-07 12:38:36 ~18 min android 📦apk 📲
✔️ 21a98c6 #5 2020-01-07 12:39:34 ~19 min android-e2e 📦apk 📲
✔️ 9adce9e #6 2020-01-07 13:56:54 ~18 min android-e2e 📦apk 📲
✔️ 9adce9e #6 2020-01-07 13:56:59 ~18 min android 📦apk 📲
✔️ 4cc252a #7 2020-01-07 14:52:39 ~11 min android-e2e 📦apk 📲
✔️ 4cc252a #7 2020-01-07 14:59:49 ~18 min android 📦apk 📲
✔️ d22cb08 #8 2020-01-07 21:03:19 ~9 min ios 📦ipa 📲
✔️ d22cb08 #8 2020-01-07 21:06:31 ~12 min android 📦apk 📲
✔️ d22cb08 #8 2020-01-07 21:07:39 ~13 min android-e2e 📦apk 📲
✔️ ff880d6 #9 2020-01-08 09:47:00 ~12 min ios 📦ipa 📲
✔️ ff880d6 #9 2020-01-08 09:53:38 ~19 min android 📦apk 📲
✔️ ff880d6 #9 2020-01-08 09:53:39 ~19 min android-e2e 📦apk 📲
✔️ 64e3949 #10 2020-01-08 10:04:35 ~9 min ios 📦ipa 📲
✔️ 64e3949 #10 2020-01-08 10:06:52 ~11 min android 📦apk 📲
✔️ 64e3949 #10 2020-01-08 10:14:35 ~19 min android-e2e 📦apk 📲
✔️ 800cfac #11 2020-01-08 15:01:00 ~13 min ios 📦ipa 📲
✔️ 800cfac #11 2020-01-08 15:06:27 ~19 min android 📦apk 📲
✔️ 800cfac #11 2020-01-08 15:06:32 ~19 min android-e2e 📦apk 📲
✔️ 477b386 #12 2020-01-08 15:51:55 ~9 min ios 📦ipa 📲
✔️ 477b386 #12 2020-01-08 15:54:13 ~11 min android 📦apk 📲
✔️ 477b386 #12 2020-01-08 16:00:56 ~18 min android-e2e 📦apk 📲
✔️ cb571e9 #13 2020-01-08 16:12:55 ~8 min ios 📦ipa 📲
✔️ cb571e9 #13 2020-01-08 16:17:15 ~12 min android 📦apk 📲
✔️ cb571e9 #13 2020-01-08 16:17:34 ~13 min android-e2e 📦apk 📲
✔️ bc3b235 #14 2020-01-08 21:00:56 ~8 min ios 📦ipa 📲
✔️ bc3b235 #14 2020-01-08 21:04:11 ~12 min android 📦apk 📲
✔️ bc3b235 #14 2020-01-08 21:04:16 ~12 min android-e2e 📦apk 📲
✔️ 9ce47ff #15 2020-01-09 10:42:45 ~8 min ios 📦ipa 📲
✔️ 9ce47ff #15 2020-01-09 10:45:45 ~11 min android-e2e 📦apk 📲
✔️ 9ce47ff #15 2020-01-09 10:46:01 ~12 min android 📦apk 📲
✔️ 30d40dc #17 2020-01-09 11:30:27 ~8 min ios 📦ipa 📲
✔️ 30d40dc #17 2020-01-09 11:32:01 ~10 min android-e2e 📦apk 📲
✔️ 30d40dc #17 2020-01-09 11:32:49 ~11 min android 📦apk 📲
✔️ 090e810 #19 2020-01-09 12:23:52 ~10 min android-e2e 📦apk 📲
✔️ 090e810 #19 2020-01-09 12:24:41 ~11 min android 📦apk 📲
✔️ 6fa8a0b #20 2020-01-09 14:34:29 ~9 min ios 📦ipa 📲
✔️ 6fa8a0b #20 2020-01-09 14:36:09 ~10 min android 📦apk 📲
✔️ 6fa8a0b #20 2020-01-09 14:37:18 ~12 min android-e2e 📦apk 📲
✔️ 316ab1a #21 2020-01-09 16:59:40 ~9 min ios 📦ipa 📲
✔️ 316ab1a #21 2020-01-09 17:02:13 ~11 min android 📦apk 📲
✔️ 316ab1a #21 2020-01-09 17:02:49 ~12 min android-e2e 📦apk 📲
✔️ 7be25d5 #22 2020-01-10 07:29:30 ~12 min ios 📦ipa 📲
✔️ 7be25d5 #22 2020-01-10 07:34:15 ~17 min android-e2e 📦apk 📲
✔️ 7be25d5 #22 2020-01-10 07:35:03 ~18 min android 📦apk 📲
✔️ ebc7051 #24 2020-01-10 08:54:54 ~8 min ios 📦ipa 📲
✔️ ebc7051 #24 2020-01-10 08:57:37 ~11 min android 📦apk 📲
✔️ ebc7051 #24 2020-01-10 08:57:56 ~11 min android-e2e 📦apk 📲
✔️ c4e8012 #25 2020-01-10 15:53:44 ~8 min ios 📦ipa 📲
✔️ c4e8012 #25 2020-01-10 15:55:55 ~11 min android 📦apk 📲
✔️ c4e8012 #25 2020-01-10 15:59:32 ~14 min android-e2e 📦apk 📲
fddd865 #26 2020-01-10 16:42:52 ~19 sec android 📄log
fddd865 #26 2020-01-10 16:42:53 ~18 sec ios 📄log
✔️ fddd865 #26 2020-01-10 16:54:52 ~12 min android-e2e 📦apk 📲
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ 50981ce #27 2020-01-10 19:25:00 ~12 min ios 📦ipa 📲
✔️ 50981ce #27 2020-01-10 19:31:37 ~19 min android 📦apk 📲
✔️ 8482889 #28 2020-01-10 19:31:44 ~18 min android-e2e 📦apk 📲

@cammellos cammellos self-assigned this Jan 3, 2020
@cammellos
Copy link
Contributor Author

@rachelhamlin requesting a transaction has also been implemented if you'd like to give it a go

@status-im-auto
Copy link
Member

✔️ status-react/prs/ios/PR-9741#6 🔹 ~12 min 🔹 9adce9e 🔹 📦 ios package

@status-im-auto
Copy link
Member

✔️ status-react/prs/ios/PR-9741#7 🔹 ~9 min 10 sec 🔹 4cc252a 🔹 📦 ios package

@yenda
Copy link
Contributor

yenda commented Jan 8, 2020

UX bug turned out to be quite a rabbit hole, while implementing link to transaction I realize that the lack of pending transaction in history was actually due to a bug, which I fixed, then while testing it it turned out that there was also a bug in send transaction drawer when trying to select one of your own account as recipient.

@yenda
Copy link
Contributor

yenda commented Jan 8, 2020

@churik @Serhy this is ready for testing

@statustestbot
Copy link

96% of end-end tests have passed

Total executed tests: 100
Failed tests: 4
Passed tests: 96

Failed tests (4)

Click to expand
1. test_request_public_key_status_test_daap

Device 1: Type 'status-im.github.io/dapp' to EnterUrlEditbox
Device 1: Tap 'Confirm' on native keyboard

Device 1: 'AllowButton' is not found on the screen

Device sessions

2. test_offline_messaging_1_1_chat

Device 1: Tap on AirplaneModeButton
Device 1: Looking for an element by text part: 'MmsService'

Device 1: 'ChatElement' is not found on the screen

Device sessions

3. test_pass_phrase_validation

Device 1: Wait for ReencryptYourKeyButton
Device 1: Looking for full text: 'Invalid seed phrase'

Device 1: 'BaseElement' is not found on the screen

Device sessions

4. test_pair_devices_sync_one_to_one_contacts

Device 2: Looking for a message by text: 'sent after sync'
Device 2: Wait for ChatElementByText

"Royal Defensive Solenodon" is not found in Contacts after initial sync

Device sessions

Passed tests (96)

Click to expand
1. test_search_chat_on_home
Device sessions

2. test_can_see_all_transactions_in_history
Device sessions

3. test_install_pack_and_send_sticker
Device sessions

4. test_send_message_in_group_chat
Device sessions

5. test_login_with_new_account
Device sessions

6. test_clear_history_of_group_chat_via_group_view
Device sessions

7. test_timestamp_in_chats
Device sessions

8. test_password_in_logcat_sign_in
Device sessions

9. test_logcat_recovering_account
Device sessions

10. test_modify_transaction_fee_values
Device sessions

11. test_public_chat_clear_history
Device sessions

12. test_need_help_section
Device sessions

13. test_send_and_open_links
Device sessions

14. test_mobile_data_usage_popup_stop_syncing
Device sessions

15. test_mobile_data_usage_settings
Device sessions

16. test_create_new_group_chat
Device sessions

17. test_sign_typed_message
Device sessions

18. test_user_can_switch_network
Device sessions

19. test_mobile_data_usage_popup_continue_syncing
Device sessions

20. test_set_profile_picture
Device sessions

21. test_home_view
Device sessions

22. test_open_google_com_via_open_dapp
Device sessions

23. test_send_message_to_newly_added_contact
Device sessions

24. test_share_contact_code_and_wallet_address
Device sessions

25. test_make_admin_member_of_group_chat
Device sessions

26. test_connection_is_secure
Device sessions

27. test_add_to_contacts
Device sessions

28. test_add_account_to_multiaccount_instance
Device sessions

29. test_can_open_dapp_from_dapp_store
Device sessions

30. test_user_can_remove_profile_picture
Device sessions

31. test_refresh_button_browsing_app_webview
Device sessions

32. test_long_press_to_delete_1_1_chat
Device sessions

33. test_can_add_existing_ens
Device sessions

34. test_transaction_wrong_password_wallet
Device sessions

35. test_public_chat_messaging
Device sessions

36. test_unread_messages_counter_public_chat
Device sessions

37. test_delete_one_to_one_chat_via_delete_button
Device sessions

38. test_long_press_to_delete_public_chat
Device sessions

39. test_text_message_1_1_chat
Device sessions

40. test_delete_public_chat_via_delete_button
Device sessions

41. test_can_use_purchased_stickers_on_recovered_account
Device sessions

42. test_open_transaction_on_etherscan
Device sessions

43. test_onboarding_screen_when_requesting_tokens_for_recovered_account
Device sessions

44. test_unread_messages_counter_1_1_chat
Device sessions

45. test_contact_profile_view
Device sessions

46. test_logcat_backup_recovery_phrase
Device sessions

47. test_delete_group_chat_via_delete_button
Device sessions

48. test_start_chat_with_ens
Device sessions

49. test_add_and_remove_contact_from_public_chat
Device sessions

50. test_open_blocked_site
Device sessions

51. test_open_chat_by_pasting_public_key
Device sessions

52. test_ens_username_recipient
Device sessions

53. test_fetch_more_history_in_empty_chat
Device sessions

54. test_open_public_chat_using_deep_link
Device sessions

55. test_switch_users_and_add_new_account
Device sessions

56. test_copy_contact_code_and_wallet_address
Device sessions

57. test_send_transaction_from_daap
Device sessions

58. test_send_two_transactions_one_after_another_in_dapp
Device sessions

59. test_message_marked_as_sent_in_1_1_chat
Device sessions

60. test_long_press_delete_clear_all_dapps
Device sessions

61. test_copy_and_paste_messages
Device sessions

62. test_deploy_contract_from_daap
Device sessions

63. test_back_forward_buttons_browsing_website
Device sessions

64. test_password_in_logcat_creating_account
Device sessions

65. test_add_custom_token
Device sessions

66. test_sign_message_from_daap
Device sessions

67. test_group_chat_system_messages
Device sessions

68. test_dapps_permissions
Device sessions

69. test_logcat_send_transaction_from_wallet
Device sessions

70. test_pair_devices_sync_name_photo_public_group_chats
Device sessions

71. test_log_level_and_fleet
Device sessions

72. test_add_and_delete_watch_only_account_to_multiaccount_instance
Device sessions

73. test_recover_account_from_new_user_seedphrase
Device sessions

74. test_user_can_complete_tx_to_dapp_when_onboarding_via_dapp_completed
Device sessions

75. test_send_two_transactions_in_batch_in_dapp
Device sessions

76. test_ens_in_public_and_1_1_chats
Device sessions

77. test_block_user_from_public_chat
Device sessions

78. test_fetching_balance_after_offline
Device sessions

79. test_logcat_sign_message_from_daap
Device sessions

80. test_offline_status
Device sessions

81. test_wallet_set_up
Device sessions

82. test_manage_assets
Device sessions

83. test_add_new_group_chat_member
Device sessions

84. test_decline_invitation_to_group_chat
Device sessions

85. test_account_recovery_with_uppercase_recovery_phrase
Device sessions

86. test_send_token_with_7_decimals
Device sessions

87. test_user_can_see_all_own_assets_after_account_recovering
Device sessions

88. test_send_emoji
Device sessions

89. test_filters_from_daap
Device sessions

90. test_redirect_to_public_chat_tapping_tag_message
Device sessions

91. test_logcat_send_transaction_from_daap
Device sessions

92. test_remove_member_from_group_chat
Device sessions

93. test_send_eth_from_wallet_to_address
Device sessions

94. test_send_stt_from_wallet
Device sessions

95. test_messaging_in_different_networks
Device sessions

96. test_collectible_from_wallet_opens_in_browser_view
Device sessions

@Serhy
Copy link
Contributor

Serhy commented Jan 9, 2020

With the 14th builds in jenkins on both iOS and Android for the accounts switched to Ropsten network and created 1-1 chat between each other:

Issue #1

Similar to above Issue1:
Send Send transaction command to user UserB -> UserB taps Accept and share address (Select account bottom sheet appears) -> tap Status account and tap any of Status account / another account in the list.
Actual result: bottom sheet does not collapse giving no ability to select-and-confirm anything apart Status account (I can pull down and proceed with default Status account selected but that's anyway not the case)

Issue #2

Can't Cancel bottom-sheet which appears after Accept and share address tapped by tapping the Cancel button.

@Serhy
Copy link
Contributor

Serhy commented Jan 9, 2020

Issue 3

There are issues with keyboards appearance when user taps Sign and send
Preconditions:

  1. UserA (iOS) and UserB (Android) create/recover and account with positive ETH/token balance and switch to Ropsten
  2. UserA and UserB join the same 1-1 chat
  3. Both UserA and UserB send Send transaction (ETH or token) to each other
  4. Both UserA and UserB confirm address
  5. Both UserA and UserB navigate back to Chats view

Scenario #1 (When dialpad on Android appears)

  1. UserB (Android) opens 1-1 chat
  2. UserB taps Sign and send
    Actual result:

Screenshot 2020-01-09 at 12 39 47

Scenario #2 (When keyboard on Android appears)

  1. UserB (Android) opens 1-1 chat
  2. UserB taps inside message input, so the keyboard appears
  3. UserB taps Sign and Send
    Actual result:

Screenshot 2020-01-09 at 12 42 17

Scenario #3 (When keyboard on iOS keep staying overlapping Send tranasaction bottom-sheet)

  1. UserA (iOS) opens 1-1 chat
  2. UserA taps inside message input, so the keyboard appears
  3. UserA taps Sign and Send
    Actual result:

Screenshot 2020-01-09 at 12 45 27

9) However, after I put Status on iOS on background and return back it to foreground it becomes like in Scenario2 above with Android (so Send transaction with keyboard below)

Expected results:

I think expect results for above would be: when Sign and send button is pressed we a) hide/close any keyboard/dialpad and then call for Send transaction bottom sheet. So Send transaction always appears without keyboard/dialpad

@yenda
Copy link
Contributor

yenda commented Jan 9, 2020

@Serhy build 17 should contain fixes for all your issues, also I switched to ropsten instead of mainnet so you can do all the tests you want. build 16 is the same but mainnet only

@@ -134,6 +134,8 @@
:InstallationID installation-id
:MaxMessageDeliveryAttempts config/max-message-delivery-attempts
:MailServerConfirmations config/mailserver-confirmations-enabled?
:VerifyTransactionURL "https://ropsten.infura.io/v3/f315575765b14720b32382a61a89341a" #_"https://mainnet.infura.io/v3/f315575765b14720b32382a61a89341a"
:VerifyTransactionChainID 3 #_1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whats this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use that to validate transaction, it should always point to mainnet as we don't validate ropsten transactions, so it's not the same as the network the user is in

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

though once we support multiple networks it can probably go away

[cofx chat-id transaction-hash signature]
{::json-rpc/call [{:method "shhext_sendTransaction"
:params [chat-id transaction-hash (:result (types/json->clj signature))]
:on-success #(re-frame/dispatch [:transport/message-sent % 1])}]})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does 1 mean ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 means that only 1 confirmation is needed (as opposed to n for group chats), it's an artifact of when sending was mostly in status-react, we will remove it at some point but still some work to do

src/status_im/subs.cljs Outdated Show resolved Hide resolved
@@ -37,7 +37,7 @@
:height panel-height
:transform [{:translateY bottom-anim-value}]
:opacity alpha-value}}
[react/view
[react/view {:style {:flex-direction :row}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why row ? @errorists

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@errorists can tell if that's a good idea or not, basically I kept finding it super weird to have only 2 commands that are aligned vertically instead of horizontally, in the designs they are on top of each other but there is also more commands. So I thought we should align them like this until there is more


(defn- command-pending-status
[command-state direction to transaction-type]
[react/view {:style {:flex-direction :row
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could be moved to styles ns

@status-im-auto
Copy link
Member

✔️ status-react/prs/ios/PR-9741#19 🔹 ~9 min 9 sec 🔹 090e810 🔹 📦 ios package

@Serhy
Copy link
Contributor

Serhy commented Jan 9, 2020

Issue #4

Status crashes when navigating to 1-1 chat with sent or received Send transaction/Receive transaction command message with STT. Apparently it happens with tokens having no custom icon. Well not all tokens with default icon behaves like that, but it's the only pattern I see when sending request command with ~10 different tokens. Appears for STT and all fine for all other tokens in Ropsten. Also if I'm on Mainnet then tokens with default icon sent in Request command (ADX and TGT) does not crash app but VRS does (and several other tokens with non-default icons behave fine)

To reproduce:

  1. Create a new account and enable STT token on Ropsten (or recover account having STT already)
  2. In 1-1 chat send the Send transaction / Request transaction with STT token selected.
    Actual result: App crashes

Screenshot 2020-01-09 at 15 09 44

Logcat with exception stacktrace:
Status.log

@churik
Copy link
Member

churik commented Jan 9, 2020

ISSUE 5: Messages from device with custom time are not sent immediately

I think it may be important because issue is not reproducible on current nightly.
So messages from devices with custom time will be sent later (if time is behind).
So if you have device time -5 mins and send message from PR to PR build - it will be received only after 5 minutes.

Steps:

  • Device A: install status
  • Device A: set custom time
  • Device A: create new multiaccount
  • Device A: join public chat
  • Device B (with automatic time): create multiaccount, join the same public chat
  • Device A: send message and check it on other device

Expected result: message is received on Device B
Actual result: message is not received on Device B (it will appear on Device B after 5 mins)
cc @cammellos

@cammellos
Copy link
Contributor Author

@churik can you replicate consistently? are messages on device A marked as "Sent"?
thanks

@churik
Copy link
Member

churik commented Jan 9, 2020

@cammellos, yes, consistently from PR build.
Yes, they are marked as "Sent"

@yenda
Copy link
Contributor

yenda commented Jan 9, 2020

@Serhy @churik 4 should be fixed

@cammellos cammellos force-pushed the wip/commands branch 2 times, most recently from 25d2fa0 to ebc7051 Compare January 10, 2020 08:46
@cammellos
Copy link
Contributor Author

@churik @Serhy issue 5 should also be fixed, I haven't had time to test the build, but if you manage to test it let me know, thanks!

@Serhy
Copy link
Contributor

Serhy commented Jan 10, 2020

All above issues are fixed but Issue 3: Scenario1 and Scenario2 on Android 8.1 (Samsung J7) (can't reproduce with Android 9 though)

Issue 6

Custom token displayed as ERC20 in Send/Request if I just added it to the list of tokens for the first time. However if I relogin, then I see token recognised in the command message. Can't Sign the transaction though, because of 'Insufficient funds' error (even my address has enough funds) - that's might be due to #9792 which might be the root cause of this 'Issue6'

Update: in latest build here difference between develop for #9792 issue is that here custom token kept on Wallet -> Manage Assets -> Assets list

To reproduce:

  1. Open Status and create new account
  2. Add custom token (for Ropsten it may be 0x101848D5C5bBca18E6b4431eEdF6B95E9ADF82FA - WEENUS token)
  3. Send Send transaction or Request transaction with custom token
    Actual result: ERC20 is displayed in command message

Screenshot 2020-01-10 at 15 42 14

Issue 7

We need to reflect testnet ETH as we do in Wallet: i.e. ETHro/ETHri. It's now displayed as ETH which may have consequences which is described in next Issue8

Issue 8

Commands view in different network. Not sure if it's part of this PR but what happens is that commands I sent from Ropsten looks on Mainnet as ERC20 for all tokens and ETH recognised as mainnet ETH (fiat conversion applied to it)

Screenshot 2020-01-10 at 15 45 32

@yenda yenda force-pushed the wip/commands branch 2 times, most recently from c4e8012 to fddd865 Compare January 10, 2020 16:42
@Serhy
Copy link
Contributor

Serhy commented Jan 10, 2020

Tested https://i.diawi.com/3KL5uB,
and http://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-200110-154443-c4e801-pr-universal.apk
Agreed to skip Issue8 for now.
Issue9 and Issue 3: Scenario1 and Scenario2 to have a separate GHI.

  1. Can send tx with ETH (0 , 1e-18 ETH, max I have)
  2. Can send tx with tokens including custom token
  3. Can request with token and reply to it
  4. Can request with ETH and reply to it
  5. Sign phrase appears when no wallet onboarding set up done
  6. Fiat values calculated accordingly to amount
  7. Check status (Shared -> Pending -> Confirmed) on both recipient and sender
  8. Changed name of shared account reflected in previous messages - like for that!
  9. Messaging in different networks and with different custom time works

Lets merge, @cammellos @yenda (just to fix conflict). Kudos to you!
Rest minor issues and known issues we may fix separately.

Signed-off-by: yenda <eric@status.im>
@yenda yenda merged commit 8482889 into develop Jan 10, 2020
@delete-merged-branch delete-merged-branch bot deleted the wip/commands branch January 10, 2020 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

7 participants