NEM Wallet Beta 2.4.4 - Bug bounty paid in XEM

Releases
#69

I found a new bug that only happens when using the latest Google Chrome (V.56).

At the Apostille notarization creation menu, the fee will be remitted but the Zip file can not be downloaded.

Looking at the console log, it seems that I am trying to access the cettificate.png file and it is a CORS policy violation.
Here is the screen at that time.

2017-02-07 18.01.31.png1235×1096 148 KB

#70

Hi,

Indeed, this issue was also in Safari. It has been fixed a couple days ago by fetching the certificate from Github repository if using those browsers.

1 Like
#71

Thanks for the report. As QM said, the next release will have this fixed.

1 Like
#72

Hi,
I’m using the english language.
If I go from

Services

Delegated Harvesting
clic on "Manage delegated account"
In the harvesting panel on the bottom,
there is a combo box,
"Select a node to harvest on"
on the right of this combobox, there are three buttons from left to right:

1 - "use custom node"
2 - "use node from list"
3 - “start delegated harvesting”

well, the description of 1 should go to button 2
and the description of button 2 should go to button 1

#73

I have logged two issues on GitHub:
#13 - In Microsoft Edge after upgrade of NCC wallet you are not prompted to download the upgraded wallet and manually trying to download the wallet from Account does work either.
#15 - Microsoft IE 11 rendering on pages is broken. Probably down to IE 11 but might want to include supported / recommended browsers on the initial splash screen

KC

#74

@quasarblue, Will be fixed in upcoming 1.3.0

@KingCole, I’ll probably lock the app and show a splash screen with recommended browsers if an unsupported one is used.

#75

Version 1.3.0

  • New design
  • Address book
  • Fix Apostille on Chrome and Safari
  • No need to provide an account address to create a private key wallet, address will be shown automatically
  • Same as above point but for creating multisig accounts
  • Importance transaction module show the corresponding remote account address when a custom public key is provided
  • Fix handling of decimal amount in normal transfer transaction, comma and dot decimal mark can be used
  • Fix message fee
  • Fix ‘unknown mosaic divisibility’ error when receiving a new mosaic
  • Limit individual apostille file to 100MB
  • Fix display of importance score
  • Fix “FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE” using NIS time-sync API
  • Lock app and show message if browser not supported
  • New market data provider
  • Minor fixes & improvements
2 Likes
#76

Since the start and stop marks of the harvest are the same color, it may be a bit confusing.
When I am not harvesting and not connected, I think that the red mark is better like before.

#77

should be in a different color and different shape. hopefully we will have messages that come up when you hover your mouse over it too.

#78

I 'am try to send XEM with encrypt message option it seem Encrypt message button is disable.

Encrypt.jpg1477×1108 186 KB

#79

I confirmed that the ALT message appears on mouse over.

#80

I just tested it. Encrypted messaging works fine. The problem is you can’t send an encrypted message to an account that has no outgoing transaction.

For encryption to work there needs to be a private/public key pairing and accounts that have not ever made a transaction out don’t have a published public key.

We really need a better error message to help people with that.

1 Like
#81

As a result of various tests, I found an event that Encrypt can not be checked if the destination address is incorrect.
Would you please check the destination address once?

#82

Speaking of which, if the other party has never issued outbound transactions, it was a specification that does not generate a public key. If the destination is the initial account, the public key has not been released yet, so we can not encrypt it.

#83

Yes i try to send outgoing before send encrypt message to this account it work, Thank you for your support.

1 Like
#84

bug1

  1. add new contact in address book
  2. click Refresh in browser
  3. login in the wallet
  4. address book is empty (no commit data)

bug2

  1. add new contact in address book (Label “x”)
  2. click Edit button
  3. modify label to “x1” and insert password
  4. click close Icon
  5. click Efit button again
  6. Label is “x” but password field is not empty

No cleanup for password field

#85

bug3

Incorrect format of message field.

Long msg - it’s 1 row and i can’t see whole msg only end part.

#86

Well, there is no problem with NanoWallet’s logout & login, but if I reload or close the browser and reopen it, the entire address book will disappear.
I am concerned that the value of ngStorage-contacts is fixed by the value when using the address book for the first time.

Additional notes
The first time I used the address book was the version (Jeff PM Ver.) that was released in part on the day before the official release.
Perhaps, I thought whether the specification is different from the official release version, and deleted ngStorage-contacts, it started to work normally. Even if I reload, the address book will now remain.

#88

Bug Found when trying to Import to Mobile app.
In account there is an option to click QR ( Android and iOS)
Clickingg button asks for wallet password.
Successful password then displays a QR Code.

If a user leaves this flow either from closing it/ Clicking outside the modal and then reopening it they see a blank area where a QR should be. No Request for a password

Here is a link to an actual github issues with screenshots.

#89

Once delegated harvesting is ACTIVE,
the button “stop delegated harvesting” shows disabled.
Password is required to enable.
The message is somewhat difficult to understand.