Since November the 4th - In order for MetaMask to interact with your webpage dapps, you need to implement the windows.ethereum.enable as part of your scripts
I have run through the pet shop tutorial - https://truffleframework.com/tutorials/pet-shop - everything works as expected
but metamask is no longer working - can anyone assist as to how i would implement the code change above into the existing script for the pet shop tutorial
PS: I downloaded the pet shop dapp a while ago and was looking into getting it to work again.
The short answer is to download the latest version of the pet shop app, but more information can be found on the ethereum stack exchange
https://ethereum.stackexchange.com/questions/61794/metamask-now-longer-interacts-with-petshop-dapp/61803#61803
I tried it yesterday actually and it worked for me. Just go to the page, they upgraded the code. https://truffleframework.com/tutorials/pet-shop
Related
The validation report says that there are login issues with the app but nobody has been able to reproduce. This app is currently live with our customers and has been for many months and they are not reporting issues either. The only changes in this app submission were store front content (test descriptions and screenshots). We have tried on desktop and o365 versions. I can send screenshots of the o365 version working if there is a place I can send it. Please help.
Thanks
Jeff
Chrome Version: Version 54.0.2840.99 m (64-bit)
OS: Windows 10
Extensions: None enabled
I want to upload an extension to the web store developer dashboard. Since it will be my first one I have to pay 5 dollars as an entry fee. When I tried the first time I was able to see a button to press that loaded the form in which I put my CC info.
But I had trouble with my cc and I had to try it again later. But now the button is missing from the page and there is nothing I can do to bring it back.
This is a picture that shows a screen shot with the button enabled and what I'm seeing right now.
Link here.
Does anyone here had a similar problem and knows how to deal with it?
It is known bug and being tracked at crbug.com/652178
I doubt whether Google Webstore team have fixed it yet, but as a workaround you can try updating your payment details at https://wallet.google.com , then retry. I got it solved earlier in same steps.
Hope it helps!
I'm getting the following error when I try to publish:
This hosted web app has one or more app urls not owned by the developer.
The web_url of this hosted web app is not owned by the developer.
I am getting the green warning box as described in:
https://code.google.com/p/google-apps-script-issues/issues/detail?id=1520
However, I'm hitting the refresh button and no joy in the solving the problem. I've published a lot of apps scripts in the past and never had this issue.
You have to register your url with the Google webmaster tools program and they will give you code to fix this. In case you have already done that, just go and verify again. It happened to me as well and I had to verify the site again. It works!
I've created a packaged app for chrome web store. For test reasons I've tried to buy my own app using another google account with another credit card and recieved an error:
Uh oh. There was a problem.
We couldn't start your purchase because of a technical issue. Details
of the problem below: There is an error in the setup for your
purchase. Please contact the merchant about this issue.
What might be a reason of this error?
Thanks!
Thanks all for helping. Problem dissapeared some how... didn't do anything to fix it...
Has anybody found that the Obout Calendar control has stopped working in the latest Google Chrome update (17.0.963.56 m)?
We have an active licence with Obout, but following two emails and two telephone calls we have yet to receive a response or even an acknowledgement that an issue exists. Anyone using the latest version of Chrome can replicate the issue on the published examples:
http://www.obout.com/calendar/calendar_live_styles.aspx?style=default
Try paging through the months a few times and you should eventually see the following error:
Uncaught TypeError: this is not a Date object.
If anybody has a workaround or can shed light on the matter I would love to hear from you. At the moment it has crippled our live site and we are frantically looking for a solution.
The new version of the Obout Calendar has been released today:
http://www.obout.com/calendar/changelog.aspx
It contains the fix for the latest Google Chrome.
I have seen the problem and am also waiting to hear back from Obout. Have sent 3 emails and as yet nothing. I have only just bought the suite this week! and am hoping that this difficulty in getting a response is just my lack of using the correct channels.
OK Problem Solved!...Obout have just emailed me a revised DLL. Happy to forward this if anybody requires.