Token wizard crowdsale creation does not call metamask

[Febrero]

If you are reporting a problem with Token Wizard, please include the following information:

Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)

Kovan, Rinkeby, Sokol

If you were able to create it, what is the URL of your crowdsale?

not able to create. After i click to create crowdsale it keeps on the same window and doesnt do anything.

Do you have screenshots showing the problem?

Many. Metamask is working fine (prove from mew)

Also there is an error on the dev mode:

Logfile
wizard.poa.network-1519755306821.log

Do you see errors in the dev console? If yes, please include a screenshot

see above

To open the dev console in Google Chrome, press F12, or go to View -> Developer -> Developer Tools, and open the Console tab

If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.

Your answer

Also i have been able to create crowdsales in the past. Please see below a list of crowdsale contracts i have created on the test network /kovan

[vbaranov]

@Febrero What is your crowdsale parameters?

[Febrero]

ok i know what the problem is.

so when i create the crowdsale like this it works:

if i add the contract creator address to the reserved tokens it breaks.

The problem is with the contract creator address being add to the reserved tokens.

[Febrero]

how can this be fixed?

[dennis00010011b]

@Febrero
Looks like decimals field is empty . It may be reason why deployment failed. See #634

[Febrero]

Nope it's just a bad screenshot. the fields decimal was not empty when i run it <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> 2018-02-27 20:44 GMT+00:00 dennis00010011b <notifications@github.com>:

…

@Febrero <https://github.com/febrero> Looks like decimals field is empty . It may be reason why deployment failed. See #634 <#634> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AX5Qlwqg59eMppYj7gSTumEMgKph9mgTks5tZGkrgaJpZM4SVadk> .

-- *Pedro Febrero* *Founder* +447874977692 (UK) +351936882364 (PT)

[Febrero]

The problem is if you try to add the contract creator address to reserve tokens.

Can you try? With the address your creating the contract also add it to the reserved tokens and assign it a token number, for example, 1000000

Then put the rest of the parameters as you please and see if it works.

In my case it did not work.

[dennis00010011b]

@Febrero I can't reproduce it

[Febrero]

i did input 18 decimals:

then click continue (notice how the contract owner has reserved 10000000

amounts

if i go back the decimals disappeared

[Febrero]

if i click continue it takes me to the last screen but nothing happens

[Febrero]

im testing in kovan

[Febrero]

@dennis00010011b were you able to reproduce now?

It's not working at all for me now. Something has definitely changed as this was working weeks ago.

[vbaranov]

I reproduced the problem.
It happens to me with 10000000 rate. oneTokenInETH is incorrectly calculated:
https://github.com/poanetwork/token-wizard/blob/master/src/stores/utils.js#L100.
@fernandomg @fvictorio please take a look

[Febrero]

@vbaranov thanks Victor.

Do you know when will it get fixed, more or less? I'm not entirely sure about the seriousness, hence my question.

Thanks again

[vbaranov]

There is no ETA for this issue. We will resolve it ASAP. Follow this issue for resolution. Btw, there will be no error, if you'll use less rate.

[Febrero]

Absolutely.

I have tested with a less rate and i confirm it's working. Thanks again Victor.

[fernandomg]

@Febrero @vbaranov I'm working on this issue.

I'm taking the chance to replace the rate input type from number to text, so we are able properly handle big (or really small: 1e-18) numbers, I'm working with BigNumber library (https://github.com/MikeMcl/bignumber.js) to do so.

I've managed to properly work with numbers up to 1e18, and deploy properly.

Tomorrow will be pushing the PR for this issue, after fixing rate validation and crowdsale/invest pages handling of rate value.

[Febrero]

@fernandomg muchas gracias Fernado.

Awesome, thank you so much for the explanation and for swift resolution. Will wait for your
--commit.