There's no recent posts or activity, the documentation is ancient, and my efforts to add subscription payments just outputs this for a subscription purchase:
The query calls all seem to work, the payment box opens, but I'm thinking that maybe I'm chasing a deprecated API? I'm not sure what's still active and what's not. :( I've tried in both debug mode and with a published (unlisted) app.
You may check on this link. Maybe your Google Account had Google Payments disabled for all users. Try enabling it and see if it works. You can also try deleting your card from your account and add it back again or try different browsers and delete caches.
This issue was also reported in this thread and suggested action is to contact the support team to fix the issue.
Related
In the Web Store Developer Dashboard, I see no way to set the price for an extension I am uploading. Am I missing something? Or is it no longer possible to create a paid extension? I saw an article saying they were removing paid extensions in January but there are still paid extensions on the store.
I got an email yesterday from chromewebstore-dev-support#google.com that included this info:
Chrome Web Store payments - We are disabling the ability to create new paid items or add payments to existing items. This includes extensions, themes, apps, and in-app purchases.
Here is the full text of the email:
Dear Developer,
We want to tell you about impending changes to the Chrome Web Store as
a result of the COVID-19 situation.
Given adjusted work schedules due to these unprecedented times, there
may be some temporary limitations and delays in support in some cases:
Delay in publishing - New versions submitted to the Store will take longer to be reviewed and published.
Delay in responses to appeals - If you appeal an item rejection or removal, or appeal an account suspension, expect the response to be
delayed. However, we will respond to every appeal request and we will
get back to you as soon as we can.
Delay in developer account transfers - If you are transferring your extension to a different account, expect a significant increase
in the time taken to complete the transfer.
Delay in general support - If you are trying to reach out to our support team for issues related to your account(s) or extension(s),
expect a delayed response from our team. We will get back to you as
soon as we can.
Chrome Web Store payments - We are disabling the ability to create new paid items or add payments to existing items. This includes
extensions, themes, apps, and in-app purchases.
You can help by making sure that your extensions comply with the
Developer program policies before you submit them. Refer to these
resources for more information:
Help center articles
chromium-extensions Google Group
StackOverflow
Chrome support forum
We understand that these changes may cause inconvenience, and we
apologize for any interruption of service. Thank you for your support
during this challenging time and for your participation in the Chrome
extension ecosystem.
The Google Chrome Web Store team
Sorry about the formatting.
During a bug investigation on Instagram app, we tried to associate a Facebook page to an existing Instagram Business creator account. For some reason we had only a "Something went wrong error, please try again later" for days.
We also tried to do it from a new account when we just switched to business account and it worked! So later we tried on our existing account because it's this one that we need to test (but it's a real account from one of our coworker) to switch back to a personal account in order to start the process over.
Unfortunately we did it without being really careful about the grey message that says it will lose content from promotions (we were not even aware about what this is).
Then we switched again to business account and tried to link our Facebook page and it worked. So it clearly fixed the bug that we had to connect our Facebook page.
Nevertheless, a couple hours later, our coworker came to us very scared and told us that she lost all the insights from her previous posts and she really needs it for her other work..
Is there any chance that we can get back this data, and if so how?
This website is for all developers - but I doubt the developers you need to see this are not going to see this. We really don't know how to help you in this case because we (as a community - not as individuals) do not manage any of the instagram or facebook code. These problems will have to be solved using the help provided on their platforms.
THIS site: https://help.instagram.com/381579045265733
THIS site: https://www.facebook.com/help/326603310765065/
I have searched high and low, but I can't find anything telling me how to enable GitHub Vulnerability alerts through their API. I conversely can't find anything saying it's not supported.
Does anyone know where I can find the API documentation if it is supported, or can someone tell me it's not? I have just completed a migration to GitHub for my origination and we have ~750 repositories so enabling them all manually is... less than ideal.
we released an API for this scenario a while back, so you can now enable or disable security alerts in bulk using that. We also published a sample which calls that API for all the repositories in an organization.
API: https://developer.github.com/v3/previews/#enable-or-disable-vulnerability-alerts-for-a-repository
Sample: https://github.com/github/enable-security-alerts-sample
#Russ looks like it's only available according to the UI. I am in the same position in needing to enable this for a very large number of repos.
Take a look at: https://github.community/t5/GitHub-API-Development-and/Security-vulnerability-alerts/td-p/15846
I got this from my companies GitHub service rep:
Enable security vulnerability via API (v3 or v4)
I've raised this and currently in conversations with the team that is responsible for
this feature to see when this could be addressed. I have to say this
is an exception to the GitHub rule of API/Platform first. I apologise
for that.
Is it possible to receive email notification for new comments on the Support page of a Chrome extension in the webstore?
On the support page of a Chrome extension I can add a new question, suggestion or bug report but I don't receive any notification about responses.
I had the same problem. I have several apps in the Chrome Web Store and I found it tedious to be constantly checking. I found an extension that claimed to have this functionality, though I found it periodically lost my list of extensions and wasn't able to actually fetch reviews consistently. You can try the extension here: https://chrome.google.com/webstore/detail/my-extensions/igejgfmbjjjjplnnlgnbejpkpdajkblm?hl=en. It is also open source, so it could be improved.
I ended up writing some of my own scripts to periodically check and send me an email when there is a new review or support request. I made it available to use as a hosted service (currently free, though I plan on asking for a little money to defray the hosting costs as well as some coffee money). Check out the hosted service at https://www.chromebeat.com. It has a full list of the Chrome webstore apps and extensions and can send you notifications on a new support issue or review. Right now it only checks hourly and sends on the hour.
Also, when you respond to a support request, the user who reported it doesn't get any kind of notification. The best way around that I've found is to actually message that person's Google+ profile, either by adding them to a circle (e.g. App users) posting publicly and mentioning them in the post, or for some users it's possible to message directly with hangouts.
[update: Oct 2015. It's now possible to "Reply" to reviews in the web store, so that's probably the best way to respond to user reviews directly]
As far as I know, there is no such option. You will have to periodically check it.
Which makes using the built-in Feedback quite useless - you're better off using something like a public bug tracker as your "Support" link and disabling Feedback.
Existing feature request: https://code.google.com/p/chromium/issues/detail?id=295837
As of 2015-03-23, it is untriaged.
No, that has not been implemented, even approaching a decade later.
New Solution:
The two options in the current answer are no longer working, so I made a small utility app to solve this problem.
You can submit your extension's id and your email address and Webstore Watch will notify you within 1 minute of a new support request.
https://gmanicus.github.io/WebstoreWatch/
Let me know if this goes down or if you experience problems. I can't guarantee 100% reliability, but I will do my best to maintain it.
I saw the commercial library for iAd's from Monte but he isn't developping it anylonger due to the coming of InnerActive Ads in Livecode, right? So, I have created an InnerActive account and tried the only lesson I found on Livecode Lessons. That didn't work. So I posted a comment there which is awaiting moderation for quite some time now. I also mailed Inneractive, got a ticket replied, but no answer from them either.
If anyone has Ads with Inneractive running please tell/show us how you did it. I am calling mobileAdRegister with my appID and that seems okay. Then I try mobileAdCreate and mobileAdSetTopVisible and 'the result' tells me 'could not create ad'.
Dictionairy then tells me the app does not have Internet permissions or the registered app key is not valid. But I do check for internet connection and I'm sure I'm using my valid appID..
Regards, Amsterfrank
I have tested ads in the current release of LiveCode and they do indeed seem to be broken.
The LiveCode quality control team is aware of this and are currently investigating what could be the cause of this. A report on this issue can be viewed here-
http://quality.runrev.com/show_bug.cgi?id=11224
A workaround for now is to use an older version of LiveCode. After running a few tests, the last version of LiveCode that does not exhibit the mobile ad bug is LiveCode 6.0.0. This is available to download from here-
http://downloads.livecode.com/livecode/
With that being said, I would recommend holding off until the issue is resolved in a more current releases as there have been many bug/enhancements to LiveCode since 6.0.0