I’m developing a chrome extension and would like to make it a paid extension with a free trial. I uploaded my item onto the Developer dashboard and saved it as a draft, not submitting it yet. But on my Developer dashboard I don’t see an option to set the type of payment (free trial) or to set a price. Under Pricing & Distribution it says ‘Pricing and payment information can only be added in the old dashboard’ but there’s no option there either. My goal is to set a price and check if a user has paid when the trial has expired.
Steps I have taken:
I have paid $5 in Google payments center and under Account in my
Developer dashboard it says fee has been paid
I added at the long key in my manifest.json, taken from the .pem I
created by packing the extension (not using the crx in any way,
just to get a key). I can upload a new item without any errors so
the key seems to be working.
On Google Cloud Platform I created a project with the exact same name
and enabled the Chrome Web Store API. I generated a OAuth 2.0
Client id - using my app name and 32 digit id generated by the
developer dashboard - which I’ve added in my manifest.json
My manifest key and oauth2 now looks like:
"key": "MIIBIjANB…...",
"oauth2": {
"client_id": "19…...apps.googleusercontent.com",
"scopes": [
"https://www.googleapis.com/auth/chromewebstore.readonly"
]
}
I added this in my background.ts:
chrome.identity.getAuthToken({ 'interactive': true }, (token) => {
console.log('token: ', token);
});
It already seems to be working showing me a Google window prompting to ‘Choose an account to continue to ’ and that my extension ‘wants to access your Google Account’ and can ‘View your Chrome Web Store apps and extensions’, and returning a token.
My questions are:
Why don’t I see an option to select Free trial and set a price?
In Google payments center I have two id’s, should my id here be the same as the first 12 digits of my client id by any chance (cos it isn’t)?
Do I need to go through the process of creating an OAuth consent screen? In my project in Google Cloud Platform I now have that client id but it also says ‘To protect you and your users, your consent screen and application need to be verified by Google’ and creating the screen it requires ‘Authorized domains’, ‘Application Homepage link’ and ‘Application Privacy Policy link’. Is this really necessary for an extension, which doesn’t have a homepage?
Turns out this feature has been disabled due to Covid-19.
"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."
https://groups.google.com/a/chromium.org/g/chromium-extensions/c/r5EKL-McE3A/m/epeWeh-wAQAJ
Related
I've moved recently from country A to B. Unfortunately I cannot login anymore to my Azure account. I have a personal account not an organizational account.
I've followed all steps here Common problems with two-step verification for a work or school account but still did not succeed. I've logged in to my outlook account and added a new QR code for the authenticator app, but this works only for my outlook account.
I always get the screen which only shows my old mobile number
I cannot open an Azure support ticket as I cannot login anymore.
How can I add my new mobile number so that I can get a code to login to Azure in such a case?
In this case the only way is to contact support via
https://azure.microsoft.com/de-de/overview/contact-azure-sales/#phone-numbers
I would like to test (sandbox) responsive signing from the docusignapi to provide a mobile-friendly document version to our customers.
Unfortunately, I am being denied to test it since it was not part of my account plan.
I enabled Allow recipients to view mobile-friendly documents with responsive signing in the tab Signing Settings of the Admin section.
It still did not accept the request. To request responsive signing, I added a DocumentHtmlDefinition to the Document:
DocumentHtmlDefinition def = new DocumentHtmlDefinition();
def.setDocumentId(documentId);
def.setSource(html);
document.setHtmlDefinition(def);
"errorCode":"PLAN_ITEM_NOT_ENABLED","message":"A requested plan item is not enabled for this account. This account is not enabled for Smart Sections."
I thought the sandbox allowed the full testing of the api regardless of any account plan. Is it possible that testing responsive signing is not possible with a sandbox account?
Mel, This should be enabled in the sandbox account. If you have not created it recently, it's possible this older account doesn't have it yet. Could you try to create a new sandbox account by going to https://developers.docusign.com/ and creating a new one? This should resolve your issue.
I'm working with actions on google and dialogflow, and recently they proposed google signin to make account linking fast without writing own oauth server.
Today I implemented their google signin in my dialogflow app it is working quite fine but unfortunately I am unable to delete that account to check all development aspects, I tried my other google accounts and my friends account but soon ended up out of accounts
Un other methods when i enable and disable testing it forget about linking but in google signin it is tightly stick with the account, and i have tried almost everything i can try like restarting my phone and clearing cache of chrome browser but it looks like it is saving account somewhere in cloud.
What i need to do is, when i sign in first time it ask for name permission, i need that screen again and again for testing something
Google calls this Removing a Website or App that has access to your account. It is done using the myaccount.google.com console.
If you want to do this using Android, the easiest way is to:
Open your device's Settings app Settings app and then Google and then Google Account.
At the top, tap Security.
Under "Signing in to other sites," tap Signing in with Google.
Tap the name of your project.
Choose Remove access.
Through the web, you can go to Apps With Access to your Accounts:
Scroll down to the "Signing in with Google" section
Locate your project.
Select it, and choose "Remove access"
The name that is shown should be the name you've given to your project as part of the OAuth screen. If you haven't set that up (and if you're just playing around, you probably haven't), it will use the Project ID for your project. You can find this on the Cloud Console home screen attached to the same project name that you used in Dialogflow and the Action Console.
While you're in there, you will probably want to configure the OAuth screen to have a name for the app as it will be visible to users on the OAuth screen. From the menu, select "APIs & Services" and then "Credentials"
Select the "OAuth consent screen" tab, and fill in the "Application name".
This name should then be in the list of applications you have installed, and can remove.
I'm trying to use Video Indexer API (v2). But when I try to sign in to it using the the Azure Active Directory, I get this message:
Selected user account does not exist in tenant 'Microsoft' and cannot access the application 'da0eb6e2-d2bd-4cbd-ad65-81ddc43546e2' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.
I'm not sure what the issue is?
Sign-in to the VideoIndexer developer portal has been revised.
We unified the developer portal sign-in with that of the VideoIndexer site.
The screenshot in #Mohit_Garg comment in no longer relevant. This is our new sign-in experience.
The first option should be used in case of Active Directory accounts. This is also the only option that will allow you to use Video Indexer paid.
In many cases users selected the Microsoft option in the old authentication method when they actually wanted AAD option.
After the new experience they select the first option "Sign in with a corporate account" and get a message saying that an account with that E-Mail already exit.
An Email is unique in Video Indexer developer portal. So if you want to use your AAD but previously opened an account in the developer portal using a different authentication method you will need to sign-in using the original authentication method and close the account in your developer profile page. After the account removal you will be able to sign in with different authentication method.
More info can be found in the official video indexer documentation
Clarification: I'm a developer in the Video Indexer team.
Follow below steps to Subscribe to the API -
Sign in.
To start developing with Video Indexer, you must first Sign In to the Video Indexer portal.
If signing in with an AAD account (for example, alice#contoso.onmicrosoft.com) you must go through two preliminary steps:
A. Contact us at visupport#microsoft.com to register your AAD organization’s domain (contoso.onmicrosoft.com).
B. Your AAD organization’s admin must first sign in to grant the portal permissions to your org. To do this, the organization's admin must navigate to https://videobreakdown.portal.azure-api.net/signin-callback?provider=Aad, sign in and give consent.
Subscribe.
Select the Products tab. Then, select Production and subscribe.
Once you subscribe, you will be able to see your subscription and your primary and secondary keys. The keys should be protected. The keys should only be used by your server code. They should not be available on the client side (.js, .html, etc.).
Start developing.
You are ready to start integrating with the API. Find the detailed description of each Video Indexer REST API.
The docs say (step 4):
In the App Review for Instagram section, click Add to Submission for each permission your App will need from its Users. instagram_basic is required. instagram_manage_comments, instagram_manage_insights, and instagram_content_publish are optional.
Scroll to the bottom of the page, and in the Current Submission sub-section, for each submission, click its View Notes link.
In the View Notes dialogue for each permission submission, provide a description for how you will use the data returned by any endpoints that require the permission, and a screencast showing how your app will use the data.
Once you've completed your notes for all of your permission submissions, click the Submit For Review button at the bottom of the page. Note that this is separate from your App Review, which you will do after testing.
After you've added both Facebook Login and Instagram API products to your app configuration, add Facebook Login to your app and record a screencast showing how you will use data returned by the Instagram API. This is similar to the Facebook Login screencast but with Instagram data, so the same guidelines apply.
Step 5:
Once you've been notified that your Instagram API product submission has been approved, you can use the Graph API Explorer to test your app.
With Facebook Login I can create an app that works in sandbox mode. Which lets me create a screencast. To be able to use Instagram Graph API (on a site) I need (from what I can gather):
Facebook Page linked to Instagram Business Account
an app icon
a privacy policy page
a site with working Facebook Login
description of how each permission is going to be used
screencast of... what exactly? of a site that is basically ready, but instead of fetching data from Instagram, it has them hardcoded in the code?
Or there is a sandbox mode after all?
UPD I've highlighted the important parts in the quotes above. Then:
5. Test Your App
Once you've been notified that your Instagram API product submission has been approved, you can use the Graph API Explorer to test your app.
Go to the Graph API Explorer...
The first call you will make is to the Graph API's /user/accounts edge...
Locate the Page that you connected to the Instagram Business Account and click its ID...
Next, [make /page?fields=instagram_business_account request].
This is where I get empty response in Graph API Explorer (only id field is returned), or:
200:- OAuthException:(#200) Access to this data is temporarily disabled for non-active apps or apps that have not recently accessed this data due to changes we are making to the Facebook Platform. https://developers.facebook.com/status/issues/205942813488872/
GET /...?fields=instagram_business_account HTTP/1.1
on my site. Which requests to Instagram Graph API can I make before passing reviews (Instagram App Review, and Facebook App Review)?
It looks like the documentation that Facebook provides is somewhat misleading. You can actually use Instagram Graph API via Graph API Explorer (or by sending GET requests from your code) in a very limited way accessing only your instagram business account BEFORE you get initial approval described in Step 4.
Steps:
Open Graph API Explorer.
First, you need to add extra permissions in the "Access Token" section. There is a "Add a Permission" drop down on the bottom of that section. Open that drop down and select: instagram_basic, manage_pages, business_management permissions. Depending on what you are trying to do, you may need other permissions as well (e.g. instagram_manage_comments, ads_management, manage_pages).
Once you selected the extra permissions, click on the "Get Access Token" button.
Now, you have access token with correct permissions and you should be able to execute instagram_business_account request. This will return the instagram id of your business account, which you can then use for other requests.
After going through these steps, I'm able to get media for my business account via Instagram Graph API, although I'm still trying to figure out why tags request returns empty list.
Go to your app dashboard from your developer account:
https://developers.facebook.com/apps/APP_ID/dashboad
Go to: Roles -> Test Users.
Edit one of the test users to change its password to what you want in order to know him.
Once done, logout from your personal account and connect with the "test user" account in https://facebook.com
Go to your app and click the facebook login with the scope "instagram_basic".
With the access_token that you get you are able to ask Graph API about the user's instagram business account.
Et voilà.
PS: You will not be able to use the Open Graph API tool from your test user. My advice is to test your app from Incognito mode so it will not interpose with your personal account.
UPDATE
Currently, access the instagram data from this way is disabled but this is the right way to access the data.
FB error message says:
(#200) Access to this data is temporarily disabled for non-active apps or apps that have not recently accessed this data due to changes we are making to the Facebook Platform. https://developers.facebook.com/status/issues/205942813488872/
You can get full functionality of Graph API if you login with the developer account, use that to create a video screencast of app functionality and submit
You will have to create a test application out of your real application, these applications are in sand box mode by default (developer mode) https://developers.facebook.com/docs/apps/test-apps/ You will be able to access any fb permission / feature with it, and develop a product with it. Once you are ready to review, in your submission of your real application link your test app in the process