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...
Related
I tried to do this:
But I always get this:
"Sorry, unable to open the file at this time. Please check the address and try again
Do I have to enable it somewhere secret somehow.
It seems to be a bug, I am having the same issue and it seems that other users also do.
There is already an issue about it on Public Issue Tracker - give it a "star" to increase visibility.
In the meantime use the workaround as suggested by TheMaster and create your scripts from script.google.com instead of drive.google.com.
On Google's Docs Editors Help Nathan Alvesinho suggested that multiple accounts may have something to do with it. I also have multiple accounts. I used the Sign out of all accounts button on my google profile. I signed back in to only one account, and it worked. Not ideal, but it helped me.
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
I'm trying to deploy a script ad add-on but I get the following error: "Chrome Web Store system error, please try again later."
I've already waited 12+ hours but unfortunately this didn't help.
I get the error after I fill in the first screen (description, url, instructions,...).
This was very unclear from the documentation but you have to pay $5 to register as a developer in the Google Developer Console
I found this information from this Google form about this same topic.
To me problem was that I hadn't accepted the term of services in Developer Dashboard
You do not have to pay for the $5 fee to overcome this if you are developing for your own domain (google app)!
I got my account whitelisted, and now I should be able to publish my add-on.
I went through the this list: https://developers.google.com/apps-script/add-ons/publish#development_checklist.
But now, when I try to publish it as decribed here: https://developers.google.com/apps-script/add-ons/publish#publish_your_add-on, I get this error message on the developer dashboard:
Please fix the following errors: The manifest has an invalid install
container.
It does not provide much information to me, so i don't know what to do with it.
Can someone tell me how to start?
The same question was published recently on "google-apps-script-issues" bugtracker.
Google aknowledged it as a "whitelist" problem:
https://code.google.com/p/google-apps-script-issues/issues/detail?id=4000
The best I can do now is wait.. As suggested on the issue page, if somebody will have the same problem they should star the issue.
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.