-
Notifications
You must be signed in to change notification settings - Fork 215
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Token wizard crowdsale creation does not call metamask #632
Comments
@Febrero What is your crowdsale parameters? |
how can this be fixed? |
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 <[email protected]>:
… @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)
|
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. |
@Febrero I can't reproduce it |
if i click continue it takes me to the last screen but nothing happens |
im testing in kovan |
@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. |
I reproduced the problem. |
@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 |
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. |
Absolutely. I have tested with a less rate and i confirm it's working. Thanks again Victor. |
@Febrero @vbaranov I'm working on this issue. I'm taking the chance to replace the rate input type from I've managed to properly work with numbers up to Tomorrow will be pushing the PR for this issue, after fixing |
@fernandomg muchas gracias Fernado. Awesome, thank you so much for the explanation and for swift resolution. Will wait for your |
# Conflicts: # src/stores/TierStore.js
…into metamask-not-being-called-#632
…into metamask-not-being-called-#632
…into metamask-not-being-called-#632
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 tabIf 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
The text was updated successfully, but these errors were encountered: