I am trying to associate a new domain with my chrome app. I've tried uploading the new manifest file, but the Web Store dashboard says:
This hosted web app specifies one or more URLs that are not matched by sites you own. If this app will be published for anyone to access, you must verify ownership of or association to sites to match all of the URLs listed below.
Unmatched app urls:
https://www.mydomain.com/
To verify your ownership of these websites, add the necessary websites using Google Webmaster Tools and return here to complete this step.
If the site already has an owner, you may request they grant you an association which allows you to publish apps and extensions to the Chrome Web Store on behalf of the site. You may request an association in the verified website section below.
In Google Webmaster Tools, I see the following message:
https://www.mydomain.com/: Chrome Web Store associate request received
March 21, 2014
You requested permissions to publish apps and extensions to the Chrome
Web Store on behalf of https://www.mydomain.com/. You will receive a
message telling you when your request has been approved.
In the verified website section, I see:
https://www.mydomain.com/: The association request placed 3/21/14 11:51 AM is pending action by the site's owner. If you know who the owner is, you should contact them and ask them to approve it for you. If you don't, there is nothing else you can do to make this happen more quickly.
What do I need to do in order to get this association approved? The Web Store makes it sound like I need to do something in Google Webmaster Tools, but Google Webmaster Tools makes it sound like there's nothing to be done.
I was able to resolve this issue by specifying https://mydomain.com rather than https://www.mydomain.com.
Related
Its been three weeks my app (GSuite spreadsheet add-on) is in "Pending Review" state after unpublishing it through chrome web store developer dashboard.
I also don't know why it is visible in marketplace as well when I already requested Google for unpublishing this item.
Query: Its already three weeks gone, any idea how much max time Google takes to unpublish an GSuite marketplace app from Chrome web store developer dashboard?
Here is a related SO post about the unpublished apps in web store.
See this full answer from the post:
if app is unpublished then is will not be available for download, will
not appear in in-store search results, and simply cannot be installed
from store. No details information from Google Play can be received
even with direct URL to the application. Unpublishing however does not
affect existing installations (so apps will not be automatically
removed from any device that got it installed already). Also existing
users still would be able to update if they are on older version.
And you cannot have another application with the same package name, no
matter what.
EDIT
Please note that you unpublish (and this means just what name says,
nothing more) not just APK - you hide all related stuff (app's page in
Google Play etc). To end user it looks like the app is gone. For you -
it is still in your console, you can edit description, images, see
comments, stats or update APKs etc., but unless you publish it again,
nobody will see these changes.
So we've developed a Facebook App (and similar apps on Twitter and Instagram) that allow users to post and read content using an external system. We'll sell this integration directly to our clients, so it's a private application.
Basically the user will see a very simple page with a button "Log in to Facebook" and a disclaimer regarding the authorization (we'll use some query params fixed in the url, depending on the client). The client authorize us and we capture the access tokens.
To submit the app review, though, we have to explicitly give a test user to the reviewers, but that's not really possible because the real "action" happens within the integrated systems, NOT within the app itself. And those systems are not public (they shouldn't be).
So just to be clear: our app is basically a very simple "Facebook login" that we use to get tokens, generated by specific clients authorization. It's not going to be published anywhere.
Until we have around 5 to 10 clients we can add the specific users in our app as Testers/Admins/etc, but what if we scale up? Say we have 20 clients. How are we supposed to get our app to be "live"?
To follow the app review steps we would have to create some users in our local systems (we have some dev environments), open them to the internet so the reviewers can log in and see how it actually works? Is that it?
(btw I'm asking this because our app review was rejected twice and I want to make sure I'm submitting everything they ask this time).
Thanks :)
I think the Login Review FAQ answers most of your questions. The key point:
Our review team will actually test how your app uses each permission on every platform you have listed in the settings section of your app.... You'll need to explain exactly how to test each permission or feature in your app so that we can make sure it works and follows our policies. We can't approve your app if we can't fully test how it integrates with Facebook.
In other words, it's not enough to just allow them to log in to your app, you have to expose all Facebook-related features to the reviewer.
To follow the app review steps we would have to create some users in our local systems (we have some dev environments), open them to the internet so the reviewers can log in and see how it actually works? Is that it?
Yes, though I'm not sure what you mean by "open them to the internet". You should be able to create a test user on your local system and link that account to a test Facebook user. Then you can have the Facebook reviewer use that test account for their review. (From the FAQ: "In the Items in Review section, you'll see a Test User (optional) section that allows you to type the name of the user you wish to be used in your review.")
I used to manage a website but am no longer associated with it. One of the features I implemented was a basic facebook comments application. I created the app under my personal facebook account and managed it through developers.facebook.com.
I grew tired of receiving alerts whenever site visitors used the app to comment on an article so I deleted the application from my developers.facebook.com account.
The application still exists and operates as normal on the site. I expected to see an error on the website.
I do not have administrative access to the site in order to remove the reference to application. How can I completely "destroy" that application so that no site can reference it?
We have a browser based game which uses Facebook Connect through an AppID that we used to run the same game in a canvas until Fb Credits were introduced and we were forced to shut it down. Now, we only use the App the same way as a product page with the FbConnect integration on our own site.
Today's mail states for our case:
If your Connect app is accessing user connections or asking for additional permissions beyond age, email, and our Publishing Permissions, please remove these requests.
(This refers to this policy change: https://developers.facebook.com/blog/post/2012/09/05/platform-updates--operation-developer-love/)
We are using oauth FbConnect with scope=email,user_birthday. This is exactly what was specified in an earlier mail so it should be ok.
Once the user is authenticated, we simply call
https://graph.facebook.com/me?access_token=...
and read what comes there.
Is it possible, that we are not allowed to call the GraphAPI's me anymore? It contains info like gender, location and locale...
The Oauth data contains the fbuid, first/lastname and the email, but it does not contain the age, what we are supposed to be allowed to ask?
Do I have to call https://graph.facebook.com/me?fields=birthday explicitly?
Did anyone actually succeed in getting an "desktop web game hosted primarily off Facebook" to comply with their new policy without creating a new AppID?
Note: There have been a couple of questions about the "Sep 5th policy change" like Facebook: Notice of Violation this one and many previous closed as duplicates, but none I found so far contains questions or answers on a technical level.
Maybe you could skip the "Website with Facebook Login" part in developer settings and only provide your game directly via canvas. (eg. apps.facebook.com/logogame). that's what "on facebook.com" is all about, I guess.
This question already has an answer here:
Closed 10 years ago.
Possible Duplicate:
Dec 5th beaking changes - facebook says app will be effect
I got an email that my app is impacting some new rules. Unfortunately english isn't my native language and I found no possibility to ask the facebook support - I'm not sure if I understood the email correctly. I hope you can help me:
Your desktop web game hosted primarily off Facebook currently
accesses user connections when authenticating and/or requests
additional permissions beyond age, email, and publishing permissions.
This is no longer allowed per Facebook Platform Policy I.13a:
Desktop web games off of Facebook.com may only use Facebook Login
(Authentication, excluding user connections such as friend list),
Social Plugins and publishing (e.g., Feed Dialog, Stream Publish, or
Open Graph). When authenticating, these games may not request
additional permissions other than age, email, and our Publishing
Permissions.
If your app is accessing user connections
(https://developers.facebook.com/docs/reference/api/user/) or asking
for additional permissions beyond age, email, and our Publishing
Permissions, please remove these requests. After December 5th, we will
place restrictions on your app if your app continues to access user
connections or request additional permissions other than
'user_birthday', 'email' or our publishing permissions such as
'publish_actions' or 'publish_stream'.
Do I understand this right, I can ask for following additional permission like email or publishing stream but nothing else?
I changed my login-url from
"scope=email,publish_stream,read_stream,user_games_activity"
to this:
"scope=email,publish_stream"
Is it now okay?
I also use $facebook->api('/'.$FacebookID.'/friends'); to get the list of friends and build a form where the user can send his friends an invitation. Is this not alowed anymore?
• Your Canvas/mobile game currently shares the same app ID with a
desktop web game off Facebook.com, which is no longer allowed per
Facebook Platform Policy I.13b:
(Games on Facebook.com and mobile must not share the same app ID with
desktop web games off of Facebook.com. You must not use Canvas apps to
promote or link to game sites off of Facebook, and must not use emails
obtained from us to promote or link to desktop web games off of
Facebook.com).
Please create a separate app ID for your Facebook Connect integration.
After December 5th, your Connect app will no longer be accessible if
it continues to share an app ID with its Canvas/mobile counterpart.
You have received this message because your app uses a Connect
integration. If you believe this to be an error, please reference the
developer docs to ensure your app is categorized correctly.
This one I don't understand at all. What and where can I do that? My app has a own URL and a canvas page at facebook. Would it be enough to remove the canvas page and only keep the direct URL?
I changed my login-url from "scope=email,publish_stream,read_stream,user_games_activity" to this: "scope=email,publish_stream" Is it now okay?
Yes, it should be ok now because according to the breaking changes "these games may not request additional permissions other than age, email, and our Publishing Permissions." So you should be fine.
I also use $facebook->api('/'.$FacebookID.'/friends'); to get the list of friends and build a form where the user can send his friends an invitation. Is this not alowed anymore?
/friends doesn't require any additional permissions, so I think it should be ok.
What and where can I do that? My app has a own URL and a canvas page at facebook. Would it be enough to remove the canvas page and only keep the direct URL?
Yes, you need to separate your canvas/mobile game from the desktop web game. Currently, they both have the same app ID, you can choose to either remove the canvas page entirely or create a new app for the canvas/mobile game and use that new app ID. Regardless, the end result is that only one of your games can use your exisiting app ID.