My client has reached their friends limit and so I cannot become a friend.
In the developer section under roles:
https://developers.facebook.com/apps/[longId]/roles
I want to add myself as a developer.
It appears that the field is checking against existing friends as I type.
When I finish adding my email it says I am not a facebook user. Not True.
Has any one run into this?
It appears that I need to be a friend to test on the app.
Related
I recently released my quiz app in the german Play Store and I get some impressions/downloads from the US which is odd since it should not be visible to the Play Store there. I am using Firebase authentication and I also see that some users authenticate but in my database they don't have an account (username, avatar etc.) which also can't be because after you login with Google you get to a page where you can choose your username and in the second you reach to this site, a user document will be automatically created, but in some cases it does not get created.
I noticed this behavior since my app was in beta testing.
Is it a normal behavior that there are some users who can see and are able to download an app that is usually only available in one country?
It can happen because google play console generates pre-launch reports for your app, so I think they use dummy accounts to login into your application. It can also happen when you submit an update to your app and it goes through a review process.
I created an App with the GSuite administrator account. But now when I go back I am my work user(rob) and have no access to the App I created.
If I then go to Google and switch accounts there is no issue for all other Google apps(drive, gmail etc) but Appmaker still shows me as rob.
How can I convince App Maker to work like all other Google apps and let me select the logged in user?
Most likely it happens because at this time App Maker doesn't provide users with account chooser widget like most other Google products. Here are some things to try to bypass this limitation:
use different chrome instances for better accounts separation (https://support.google.com/chrome/answer/2364824) - I would highly recommend this approach. I have about 10 different accounts and this feature saves me tons of time and gives peace of mind
use incognito window
log out from other accounts (in theory, when you open AM it will ask you to choose an account and re-login)
With Google One-Tap sign in it explains you need to add googleyolo.retrieve() on the pages that require sign in for pages that need the user signed in and googleyolo.hint() for when you want to pop-up a sign-up dialogue to first-time users.
Question: Is it possible to auto-select the user even though he has multiple credentials wherever the googleyolo.retrieve() is executed?
My app saves the last user id in the cache, so the next time he opens the app, I want the app to auto choose his last used account.
From the documentation:
If the user has only one credential saved, the credential can be retrieved without user interaction, which makes completely automatic sign-in possible.
When multiple credentials are saved, the user can choose the one to use with a single tap.
I'd like to change this behaviour (the bold text) to auto choose the last user.
I'm the product manager at Google for this library. This is something we've thought about but unfortunately currently don't have plans to support. The current experience is optimized for switching between accounts, which we've found equally common as using a previously selected account. So for now, this behavior can't be changed. I'll update this answer if there is a future revision.
I need to work on Microsoft Cognitive Services (Face API). I downloaded the code from https://github.com/Microsoft/Cognitive-face-android. Now I am unable to generate the Subscription Key for it.
No matter whatever I do I get stuck in this page
From where else I can find the Subscription Key.
Thanks
The interface you are using is for testing-purposes. Consequently, it is not meant to be used for more than a month.
Here's how you can generate an API key the proper way:
Newer Edit: The Azure interface has changed since this guide was written. It hasn't changed that much, so leave me a comment if this guide is broken.
The largest change I have seen is that Bing Search API can now be located directly using the "+ New" form shown in Part A/Step 3. (aka, don't search for "cognitive services")
Edit: There is now another piece of documentation half-way down entitled "Part B: Adding a Credit Card for Pay-As-You-Go via the Azure Portal." If you have not already set up your payment method on portal.azure.com, you will get stuck at Part A/step 5.
process.
Part A:
Go to https://portal.azure.com and sign in with your credentials.
(Optional) Check to make sure you have an active Pay-As-You-Go(PAYG) subscription. Click the "More services" arrow and type subscriptions into the form that appears. Click into Subscriptions and make sure you see an entry here.**
If you're sure you have an active PAYG acct, make sure you're on the dashboard and press the green "+ New" button and start to type Cognitive Services. As you finish typing it should be your only option.
Once you've clicked the "Cognitive Services APIs" suggestion you will be brought to the following page. Click the green brain.
You'll be given a description of Cognitive services and you'll see a create button at the bottom. Press that.
The "Create" pane will pop up. Fill this out. CHECK THE PIN TO DASHBOARD BOX FIRST SO YOU DON'T FORGET (Note: If you do not have an active PAYG subscription you will see an error instead of the "Create" pane on the right-side of the image below.)
When you press the green-explosion from the picture above you will see the following icon:
This is what you want. When you've completed the form from the previous picture, press "Create" below the "pin to dashboard" box.
When you've created the subscription successfully, you'll get a little message that things are validated and your service is deploying. You should be on the dashboard now and should see a little tessellating box if you pressed pin to dashboard. Soon it will be complete and vuala!You'll see something similar to the following image. Press the "keys" button on your new service.
** If you're told that "You don't have any active subscriptions," you'll need to click the white "Add+" button and create a PAYG subscription. You will need a credit-card and non-VoIP phone for this step.
Part B:
Adding a Credit Card for Pay-As-You-Go via the Azure Portal
This portion of the process is necessary if you have never used portal.azure.com before and/or don't have an active payment-subscription on it.
For this process you will need: A valid credit-card**, a non-voip telephone for human-verification, >= $3 USD for the lowest API tier.
TO AVOID POTENTIAL HEADACHES; DO NOT USE GOOGLE CHROME FOR THESE STEPS. If you are on a Windows 10 Machine use Edge in InPrivate mode as your browser. Otherwise, firefox private-browsing is a decent alternative.
Follow steps 1 & 2 from the guide above to navigate to the Subscriptions pane. Underneath the circled "+ Add" button, you should see a message telling you there are "No subscriptions in xxxxx(Default Diretory) directory." Click the "+ Add" button.
You will be taken to the URL https://account.windowsazure.com/signup?showCatalog=True, and you should see the following screen:
As the picture above indicates. Select Pay-as-you-go (PAYG) unless you want to go off-guide. You'll be brought here & will need to fill out the 3 sections. Your card won't be charged during this process.
Once you complete the 3 steps denoted in the image above, you'll be taken to a page which asks you to wait for ~4 mins while your subscription is getting ready & you'll see that fun little animation of spinning half-circles. Eventually you'll be presented with a button which is labeled "Start Managing my Services. Which will take you back to the dashboard at portal.azure.com.
From the dashboard, Find the "Subscriptions" pane again, and this time you should see something similar to the following.
You now have a payment method with which to purchase your API subscription. From here you can resume at Step 3 of Creating an API Endpoint & Accessing Your Keys aka the first half of this guide.
** Your credit-card must have a billing address located in the country which your Microsoft username/password combo was created in.
For the subscription key, you have to create the cognitive service account in azure portal. Follow the following steps:
If you have not done so already, you will need to sign up for the Face API (preview) service.
Go to the Azure Portal at http://portal.azure.com/ and sign in with your Azure account.
Click on + New.
Select the Intelligence option.
Select the Cognitive Services APIs product. This product will allow you to start a subscription for any of the cognitive services APIs (Face, Text Analytics, Computer Vision, etc.). Today we will focus on the Face API (preview) API.
Enter a Resource name for your Face API subscription. (For instance: "MyFaceAPI"). This name should not have any spaces in it.
On API type, select .
On Pricing tier, you can select a plan. You may select the Free tier for 10,000 transactions/month. This is a free plan, so it is a good way to start trying the system. Once you go to production, we recommend you consider your request volume and change the plan type accordingly.
Select a Resource Group, or create a new one if you don't have one already.
You may change other elements in the Create dialog. We should point out that the resource provider today is only supported from United States data centers. Once you are done with any selections, click Create.
Wait a few minutes for the resource to be deployed. Once it is deployed, you can go to the Keys section in the Settings blade where you will be provided a primary and secondary key to use the API. Copy the primary key, as you'll need it when creating your first model.
Hope this help.
REF:
See this image for the azure portal registration
Have anyone heard Facebook say anything about adding the possibility to specify the privacy when publishing an action? I wonder if it's something they plan for the near future or if it will take longer time for them to implement.
Background
The "App activity privacy" let's the user set who should be able to see actions published by the app. I would like my app to set the privacy for each and every action the app publishes, just as an app can do for wall posts by specifying the "privacy" field.
Edit 2012-05-24
I attended Facebook Developer Garage in Stockholm yesterday and had the opportunity to ask what Facebook's plan is. The answer was that Facebook did think a lot about adding flexible privacy settings, but decided that they want it as simple as possible for the user. They want to let the user decide the privacy settings for everything the app publishes once and the users can currently do this when they add the app. You never know when Facebook change their minds but currently they don't have a plan for decent privacy settings.
Facebook have now added the "privacy" parameter when publishing actions.
See https://developers.facebook.com/docs/opengraph/actions/
Case closed.
Edit: As Angel García Olloqui pointed out, the privacy field can only have the values ALL_FRIENDS or SELF. Pretty useless for now.
Edit: I added a more complete answer to the question.
Access token generates corresponding to your all permissions which appear on the first startup of the application. Then by using that access token app enables to get some information from user