I have this simple problem, we want to use the FACEBOOK NOTE landing page and link it with a NEARBY NOTIFICATION.
The strange thing is that even if the URI is OK for physical web on the NEARBY is not showing up the notification.
When we change it to another standard page it works.
Of course I used a SHORTNER link to do that.
LINK OF THE PAGE ON FACEBOOK:
https://www.facebook.com/notes/il-mago-del-fornello/zuppa-di-roveja-e-cumino/1734572063523531/
THIS LINK is confirmed to be compatible with PHYSICAL WEB on: https://beaufortfrancois.github.io/sandbox/physical-web/url-validator/
But is not working.
See if the message shows in the Nearby list view in Google Settings. If you find the message there, the message was configured correctly and may not being raised as a notification for other reasons (ex: poor feedback from users, or a backoff on the specific device). If the message does not show in the Nearby list view either, it may have been flagged as a policy violation. Check the text in the message and the destination page for appropriateness (ex: profane text won't be shown). A copy of the policies can be found here: https://developers.google.com/nearby/notifications/policies
If you turn on debug mode, you can find more information about why the message was not shown in the Nearby service portion of the bug report.
https://developers.google.com/nearby/notifications/debug_mode
Related
I have created a flutter application in both iOS and Android that uses OAuth2. In order to authenticate the the app. While I can sign in successfully on iOS, Android provides error the following error:
E/flutter ( 6309): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null)
This is almost certainly because of a configuration issue in my OAuth verification request. Their rejection (see below) describes a homepage they require:
Dear Developer,
Thank you for submitting an OAuth App Verification request.
Unfortunately, we cannot proceed further with the verification process
until the requested things are provided.
As we discussed in our previous communication, to proceed with the
verification process for your project what-happend-here you will need
to provide a homepage that accurately represents your app’s identity
to Google users.
Every OAuth2 project requires a homepage. To ensure users’
understanding of your app’s purpose, your homepage should:
Be a verified domain under your ownership
Be accurate, inclusive, and easily accessible to all users
Link to an externally accessible domain that describes the necessary content, context, or connection to the app you are submitting
Explain with transparency the purpose for which your application requests user data
etc.
However, despite the description, I've no feel of what it should be like. Is there an example of such a page that I can use as a model?
Thanks for any help.
I've been back and forth with google over this issue. I can't give a simple answer, but I can summarize the items I've changed in order to meet compliance.
For context, I'm just using oauth on my personal webpage to identify users. I'm not selling an app. I'm not using restricted scopes. I'm not touching any user data.
This should be the simplest case, yet it was difficult to get approval. Each rejection reply is in the style of a form letter. I conclude that an AI has be trained against a set of compliant pages, and it "feels" mine isn't compliant, i.e. it's not able to point to a specific violation like a human or a rule's based system would. For this reason, I advise against spending time in your email replies. It doesn't seem that anyone reads them, just change your content and reply to get the AI to look again.
In the google console you must provide:
a homepage url
a privacy policy url
an uploaded icon image file
If you're using oauth for a website, don't confuse the oauth console "homepage url" with the base url of your website. Google wants a "homepage" that says "what your app is".
The content served at the homepage must have a [link rel="shortcut icon"] whose href points to the identical bytes of the icon you uploaded in the oauth console. If the bytes differ because you're using a scaled or differently styled image, you'll be rejected.
The content served at the homepage must have a privacy policy link where the href is identical to the characters entered at the console. If they're the same page, but differ by an anchor for example, you'll be rejected.
Also watch for caching. I changed the contents of my [link rel="shortcut icon"/] and got a reply that seemed to accept the icon but complain about another issue. Then when I fixed the other issue they rejected me for the icon again. I think since I changed the uploaded icon but didn't change it's name that they later saw a cached icon. I changed just the url (thus invalidating their cache) and the next reply didn't complain about the icon.
If you're not using restricted scopes you shouldn't need the limited use disclosure, but I got a complaint about that so I added it.
Here's what I'm using for both the homepage and the privacy policy:
https://holtstrom.com/michael/about/
Here's how that looked at the time of this posting when it was finally approved.
You'll see that I have all of the google requirements rendered in underline followed by the text that satisfies the requirement.
In case it helps, here's the replies I received from Google:
Google OAuth Consent Screen Verification:
#Michael Holtstrom's answer works perfectly, And I got my app approved in just the 2nd attempt.
But, since there is no information available anywhere on internet regarding this, that's why
I am posting my answer with all the screenshots, only to support #Michael Holtstrom's answer, so that you can move ahead with more confidence.
Because, I was really worried for 3-4 days whether my app will get approved or not. Because this was the last part left in my project.
I was also using Google OAuth only to get email, name and profile picture.
My app could have got approved in the first attempt only, but the first time I submited homepage had text selection disabled(Because I built it using Flutter Web, on which text selection is disbaled by default).
So, I think the Google's AI was unable to read the text on homepage, and thus asked me to update the homepage.
Next time, I built using wordpress, and then my app got approved.
(And by the way, I'm using chrome extension dark reader, that's why all the screenshot has dark mode enabled.)
Youtube Video Url:
https://youtu.be/lzq9WjCXT6c
Consent screen form on GCP Console
Google OAuth Homepage
https://www.madhavkumar.in/about/
Privacy Policy
https://www.madhavkumar.in/privacy-policy/
Email thread with Google Trust Team
We publish advertisement on facebook and we have a new domain. The problem is that advertisement click rate on facebook panel is 6193 but only 1682 person enter website accordşng to google analytic.
There are about 4500 hit which is lost. AS you know, users are redirected to our website after click on facebook advertisement but they cannot access to our website. we are waiting your kindly response.
our website: testmastersatinal.com
Try using Google's URL builder to properly code the landing page URL in such a way that GA will recognize the traffic as having come from your FB advertising campaign. Here's a blog describing how it is done.
For reasons that I do not yet completely understand - but apparently have to do with the internal FB redirect process for ads, much of my traffic from Facebook shows up in Google Analytics as (direct)/(none). I've found that setting the GA UTM codes on the landing page URL will help by using Google's URL builder helps with this issue.
More generally, in my experience, advertiser reported clicks are often different from what you see in GA. In fact, I'm working on trying to resolve this issue now with another advertising platform (not FB) who is billing us for 2.5x the number of clicks we are seeing in Google Analytics.
There are many possible causes for this, and you can find relevant discussions on
webmasters, moz.
One thing you should try is segmenting the referrals by device (mobile, tablet, desktop) or operating system, etc. See if the percentage of traffic is much lower from your ad on one particular device or operating system. This may indicate that the GA tracking is not working correctly on that device or OS.
I've noticed that some Facebook apps, like BranchOut, have customized notifications messages. When an app request is sent and appears in the top left notification center the text on the notification is something they seem to control on their own, instead of the default "Name sent you a request".
From what I find the the documentation this isn't possible. Custom messages are only shown for users already using the app, otherwise you get Facebooks default invite message.
Does anyone know how they are doing this? Do they simply have a deal with Facebook, or are they sending something other than an App Request?
Just in case someone else finds this question, it appears you can no longer control this message. There are some stuff floating around on other questions but none of them work anymore.
According to the docs, only whitelisted apps are allowed to edit the app request message that shows in the notification itself.
You can send custom notifications with the Notifications API:
https://developers.facebook.com/docs/concepts/notifications/
These can only be sent to users who already have the app installed.
If you wish to invite someone to the app then you must use apprequest which doesn't allow you to customise the message.
We've just developed a Facebook application which has a piece of functionality that allows you to post to a friends' wall. Fairly simple piece of functionality, and it's been working so far on the main www.facebook.com website. If I receive a notification that someone has posted on my timeline, and can click the link, and see the post. This is fine.
However, move to the iPhone app, or the mobile website, and it's not the same. I see the notification, click the link, and then see the following Facebook error message:
Privacy Check Failed
You can not see that.
Interestingly, in the mobile website, if I simply change the subdomain part of the URL in the address bar from
https://m.facebook.com/permalink.php?story_fbid=XXX&id=XXX
to
https://www.facebook.com/permalink.php?story_fbid=XXX&id=XXX
To access the full site, it works fine, and I can see the post (I've blanked the IDs for privacy).
After some research on the web, I can't anyone who has recently seen this message. Has anyone else seen it before? My instinct is telling me it's a bug with Facebook, but I want to check I'm not missing anything.
I am having a strange problem while making app requests. I understand that when an app request is made through my app, it also puts a notification in the top saying so and so has sent a request from this app. Now, while I can successfully make the request, the bookmark count goes up but I do no get a notification at all. Is there something i could be missing? I'm following instructions from this blog post on Facebook developer site - http://developers.facebook.com/blog/post/464/. I am new to Facebook development so if it's something simple, please point me in the right direction.
Thank You.
I've had issues with this in the past but it looks like Facebook have very recently acknowledged this and brought about correcting the issue.
http://developers.facebook.com/blog/post/540/
App to User Requests now display messages
Previously, when apps sent notifications to users (available by posting a request to the apprequests connection of the User Graph object, as documented in Social Channels), the bookmark counters were incremented, but the message included with the notification was not shown. As of this week, if you send an app to user notification, we will also display the notification message in the apps or games dashboards. This provides app developers a more effective way to communicate application-level updates to users. Note that the ticker count is now shown in bookmarks, hovercards and, for games, in the games ticker. As a result of this change, your users may see an increased number of notification messages from your application.